AI Phone Call Pro

Never miss a customer call — ever

aiphonecall.pro · Added June 10, 2026 · Last analysed June 10, 2026 · via · 57% unique tagline

Own this Launch?

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 10 June 2026; the live site may have changed since.

AI Phone Call Pro is missing several launch fundamentals. Main gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on June 10, 2026. The site is hosted on Google LLC in the United States. Our crawler found 3 technologies on this site, covering web fonts, protocol, and seo. The stack includes Google Fonts, Google Search Console, and HTTP/3.

If you own this site, refresh the snapshot and see the full fix list any time →

0.3

StackScope Score

Poor

11/100 Launch Readiness

Needs work

0/6 Security Headers

Poor

0/3 Legal

Missing

0/2 Web Standards

Missing

100/100 Performance

Fast

Vibe Score 0 · No AI signals

Informational pattern-match signal. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (3)

Infrastructure

Protocol	HTTP/3

Build & Framework

Font	Google Fonts

Analytics & Marketing

SEO	Google Search Console

Infrastructure

Network

GOOGLE-CLOUD-PLATFORM - Google LLC, US

AS396982 · US

DNSSEC

Not enabled

DNS responses unsigned. Cache-poisoning vulnerable.

SSL Certificate

Let's Encrypt

Valid 7 May 2026 to 5 Aug 2026

Certificate as captured in this snapshot, not a live check.

Email Security

✗

SPF Not published. Your domain can be spoofed in phishing emails.

DKIM Not detected at common selectors. Your provider may use a custom one.

✗

DMARC p=none None (p=none). Monitoring only.

MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.

TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (0)

This site uses no client-side storage we could detect on page load.

Readiness Breakdown How?

⚠

Custom title and meta description (partial) missing meta description

- Open Graph tags (title, image, description)

- Responsive viewport meta tag

- Canonical URL declared

- Twitter card meta tags

- Favicon present

- Semantic HTML (nav, main, article)

Performance How?

77 ms Server response

97% Faster than peers

156 ms Largest contentful paint

0.01 Cumulative layout shift

37 KB Page weight

1 Third-party domains

1 Console errors

1 Failed requests

Broken first-party requests (1), worth fixing

404 /

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

AI Stance

No AI stance declared

✗ llms.txt published

✓ No AI bots blocked in robots.txt

Content-Signal

? No directive declared

Link headers

? None advertised

Well-Known Files

✗ robots.txt

✗ sitemap.xml

✗ security.txt

✗ llms.txt

✗ ads.txt

✗ humans.txt

Legal

? Privacy Policy not detected

? Terms of Service not detected

Detection works best on English language sites.

Security Headers (0/6)

✗

Referrer-Policy

✗

X-Frame-Options

✗

Permissions-Policy experimental (check browser support)

✗

X-Content-Type-Options

✗

Content-Security-Policy

✗

Strict-Transport-Security

–

X-XSS-Protection deprecated (use Content-Security-Policy)

Build

✗ HTML minified

✗ CSS minified

✗ JS minified

0 JS files

1 CSS files

1 Third-party domains

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.