Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 483 ms totalREVIEW
https://pca.st
176 ms · HTTP/1.1
https://www.pocketcasts.com
88 ms · HTTP/1.1
https://pocketcasts.com/
219 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://pca.st | 301 | 176 ms | HTTP/1.1 | nginx/1.22.1 |
| 2 | https://www.pocketcasts.com | 301 | 88 ms | HTTP/1.1 | |
| 3 | https://pocketcasts.com/ | 200 | 219 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# To ban all spiders from the entire site uncomment the next two lines:
User-Agent: *
Disallow: /itunes/
Disallow: /private/
Disallow: /polling/
Disallow: /feed/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations267 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
A+DNS Records4 A records, 13 ms lookupPASS
| A | 52.85.31.97, 52.85.31.91, 52.85.31.2, 52.85.31.22 |
| AAAA | 2600:9000:2026:3c00:2:7f27:3800:93a1, 2600:9000:2026:1800:2:7f27:3800:93a1, 2600:9000:2026:2800:2:7f27:3800:93a1, 2600:9000:2026:3000:2:7f27:3800:93a1, 2600:9000:2026:e00:2:7f27:3800:93a1, 2600:9000:2026:ae00:2:7f27:3800:93a1, 2600:9000:2026:c000:2:7f27:3800:93a1, 2600:9000:2026:600:2:7f27:3800:93a1 |
| CNAME | — |
| NS | ns-1058.awsdns-04.org, ns-1554.awsdns-02.co.uk, ns-159.awsdns-19.com, ns-892.awsdns-47.net |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+IPv6 ReadinessIPv6 reachable (58 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
ADomain Intelligencepca.st — via MarkMonitor Inc., 12 years oldPASS
2 days
June 18, 2026
267 days
Issued by Amazon
12 years
Registered June 18, 2014
Status unknown
Protects against DNS spoofing
Unknown
2600:9000:2026:da00:2:7f27:3800:93a1
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice