Infrastructure - https://productshotai.app BeaverCheck Audit

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

C

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 172.67.205.151: lookup 172.67.205.151: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 104.21.85.119: lookup 104.21.85.119: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:3034::6815:5577: lookup 2606:4700:3034::6815:5577: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:3033::ac43:cd97: lookup 2606:4700:3033::ac43:cd97: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

B

Multi-Resolver DNS Speed

Mean 64ms across 3 resolvers (spread 133ms)

REVIEW

Mean 64ms across 3 resolvers (spread 133ms)

Cloudflare: 2ms

Got: 2ms via 1.1.1.1:53

Google: 55ms

Got: 55ms via 8.8.8.8:53

Quad9: 135ms

Got: 135ms via 9.9.9.9:53

C

HTTP Probe Timing

Action

Total 1923 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

111 ms

TCP Connect

2 ms

TLS Handshake

11 ms

Time to First Byte

1.89 s

Total Time

1.92 s

Connection waterfall

DNS Lookup 111 ms TCP Connect 2 ms TLS Handshake 11 ms Server Processing 1.77 s Content Transfer 31 ms

B

TLS Certificate Expiry & Recommendations

81 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

81

days left

0d 30d 60d 90d+

Recommended actions

Enable DNSSEC on your domain for DNS spoofing protection
Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy

B

CDN & Delivery

Cloudflare

REVIEW

Cloudflare

Site is served via Cloudflare CDN (edge: GRU)

Got: cf-ray: a31309fb8afea420-GRU

CDN Detected: Cloudflare

Provider Cloudflare Evidence cf-ray: a31309fb8afea420-GRU

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

B

Health Check Endpoint

No conventional health endpoint found

REVIEW

No conventional health endpoint found

Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

A+

DNS Records

2 A records, 112 ms lookup

PASS

2 A records, 112 ms lookup

Resolves to 2 IPv4 address(es)

Got: 172.67.205.151, 104.21.85.119

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:3034::6815:5577, 2606:4700:3033::ac43:cd97

2 nameserver(s) configured

Got: lee.ns.cloudflare.com, liberty.ns.cloudflare.com

3 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 112 ms

Got: 112 ms

A	172.67.205.151, 104.21.85.119
AAAA	2606:4700:3034::6815:5577, 2606:4700:3033::ac43:cd97
CNAME	—
NS	lee.ns.cloudflare.com, liberty.ns.cloudflare.com
MX	45 route2.mx.cloudflare.net 83 route1.mx.cloudflare.net 99 route3.mx.cloudflare.net
TXT	google-site-verification=gzgmkJoxXg_VKNeyUTGnb8HzVsqaCU399IjmPakarww openai-domain-verification=dv-uQKtX1mHYke7T3q62VSWM0Wq SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAA	Lookup not available with standard resolver

Resolved in 112 ms

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://productshotai.app

https://productshotai.app

725 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://productshotai.app	200	725 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (2 ms)

PASS

IPv6 reachable (2 ms)

IPv6 is configured and reachable at 2606:4700:3034::6815:5577, 2606:4700:3033::ac43:cd97

Got: 2 ms connect

IPv6 Ready

AAAA Records 2606:4700:3034::6815:5577, 2606:4700:3033::ac43:cd97 Connection Reachable (2 ms)

A+

Crawlability

robots.txt present, sitemap with 134 URLs

PASS

robots.txt present, sitemap with 134 URLs

robots.txt is present

Got: 1948 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 134 entries

robots.txt references sitemap

robots.txt 200 OK

Size 1948 B Sitemaps referenced 1 User-agents GPTBot, ChatGPT-User, Bingbot, CCBot, *, ClaudeBot, Claude-User, anthropic-ai, Google-Extended, Bytespider, PerplexityBot, Applebot, OAI-SearchBot, Perplexity-User, Amazonbot Blocking No — crawling allowed

User-Agent: GPTBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: ChatGPT-User
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: OAI-SearchBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: ClaudeBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Claude-User
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: anthropic-ai
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: PerplexityBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Perplexity-User
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Google-Extended
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Bingbot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Applebot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: CCBot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Bytespider
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: Amazonbot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

User-Agent: *
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /checkout/
Disallow: /billing/
Disallow: /prompts

Sitemap: https://productshotai.app/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 134 entries Valid XML Yes

Sample URLs:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 308

www / non-www

308https://www.productshotai.app/

200https://productshotai.app/

HTTP → HTTPS

308http://productshotai.app/ → https://productshotai.app/

Consistent

A+

Domain Intelligence

productshotai.app — via Namecheap Inc., 2 months old

PASS

productshotai.app — via Namecheap Inc., 2 months old

Domain registered until Jun 14, 2027 (9 months remaining)

Domain is only 2 months old

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Got: Registered Jun 14, 2026

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: Namecheap Inc.

Registrar lock is NOT enabled

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Domain expiry

291 days

June 14, 2027

SSL certificate

81 days

Issued by Google Trust Services

Domain age

2 months

Registered June 14, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3033::ac43:cd97

Registrar

Namecheap Inc.

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Namecheap Inc.

Created June 14, 2026 (2 months ago)

Expires June 14, 2027 (9 months)

Last Updated June 19, 2026

Name Servers lee.ns.cloudflare.com, liberty.ns.cloudflare.com

DNSSEC Not enabled

Hosting

IP Address 2606:4700:3033::ac43:cd97

Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice