Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 430 ms totalREVIEW
https://primevideo.com
54 ms · HTTP/1.1
https://www.primevideo.com/
149 ms · HTTP/1.1
https://www.primevideo.com/offers/nonpri...
226 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://primevideo.com | 301 | 54 ms | HTTP/1.1 | AmazonS3 |
| 2 | https://www.primevideo.com/ | 302 | 149 ms | HTTP/1.1 | Server |
| 3 | https://www.primevideo.com/offers/nonpri... | 200 | 226 ms | HTTP/1.1 | Server |
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
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
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
User-agent: *
Disallow: /hp/video/
Disallow: /-/*/hp/video/
Disallow: /api
Disallow: /gp/video/api
Disallow: /region/*/api
Disallow: /-/*/api
Disallow: /mystuff
Disallow: /gp/video/mystuff
Disallow: /region/*/mystuff
Disallow: /-/*/mystuff
Disallow: /profiles
Disallow: /gp/video/profiles
Disallow: /region/*/profiles
Disallow: /-/*/profiles
Disallow: /optout
Disallow: /gp/video/optout
Disallow: /region/*/optout
Disallow: /-/*/optout
Disallow: /settings
Disallow: /gp/video/settings
Disallow: /region/*/settings
Disallow: /-/*/settings
Disallow: /search
Disallow: /gp/video/search
Disallow: /region/*/search
Disallow: /-/*/search
Disallow: /ap/
Disallow: /gp/video/ap/
Disallow: /region/*/ap/
Disallow: /-/*/ap/
Disallow: /auth
Disallow: /gp/video/auth
Disallow: /region/*/auth
Disallow: /-/*/auth
Disallow: /salp/i
Disallow: /gp/video/salp/i
Disallow: /region/*/salp/i
Disallow: /-/*/salp/i
Disallow: /detail/Login
Disallow: /gp/video/detail/Login
Disallow: /region/*/detail/Login
Disallow: /-/*/detail/Login
Disallow: */src/
Disallow: */node_modules/
Disallow: /review/create-review/
User-agent: EtaoSpider
Disallow: /
User-agent: CCBot
Disallow: /
User-Agent: PerplexityBot
Disallow: /
User-agent: GoogleAgent-Mariner
Disallow: /
User-agent: GoogleAgent-Shopping
Disallow: /
User-agent: meta-externalagent
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Scrapy
Disallow: /
User-agent: PetalBot
Disallow: /
User-agent: Devin
Disallow: /
User-agent: omgili
Disallow: /
User-agent: AI2Bot
Disallow: /
User-agent: Gemini-Deep-Research
Disallow: /
User-agent: PanguBot
Disallow: /
User-agent: MistralAI-User
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: Sidetrade indexer bot
Disallow: /
User-agent: Google-NotebookLM
Disallow: /
User-agent: DuckAssistBot
Disallow: /
User-agent: Copilot
Disallow: /
User-agent: Ai2Bot-Dolma
Disallow: /
User-agent: Google-CloudVertexBot
Disallow: /
User-agent: meta-externalfetcher
Disallow: /
User-agent: iaskspider
Disallow: /
User-agent: wpbot
Disallow: /
User-agent: aiHitBot
Disallow: /
User-agent: cohere-ai
Disallow: /
User-agent: FriendlyCrawler
Disallow: /
User-agent: img2dataset
Disallow: /
User-agent: VelenPublicWebCrawler
Disallow: /
User-agent: YouBot
Disallow: /
User-agent: Brightbot
Disallow: /
User-agent: Claude-User
Disallow: /
User-agent: Perplexity-User
Disallow: /
User-agent: ISSCyberRiskCrawler
Disallow: /
User-agent: CopilotNative
Disallow: /
User-agent: CopilotSapphire
Disallow: /
User-agent: imgproxy
Disallow: /
User-agent: SemrushBot-SWA
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Timpibot
Disallow: /
User-agent: Thinkbot
Disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations163 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, 29 ms lookupPASS
| A | 3.165.113.82, 3.165.113.31, 3.165.113.102, 3.165.113.119 |
| AAAA | — |
| CNAME | — |
| NS | ns-1172.awsdns-18.org, ns-306.awsdns-38.com, ns-532.awsdns-02.net, ns-1933.awsdns-49.co.uk |
| MX | 10 amazon-smtp.amazon.com |
| TXT | SPF v=spf1 include:amazon.com -all google-site-verification=fLLG-R7u0APME_LIafQD3GE3uyiK18Vu4qajGwkX5TQ MS=ms35125271 google-site-verification=T7MCISsmLlHGtFwAm5SP0f_tjN_ygqjpaXbhtJOlKHY google-site-verification=qF9TbJ6oxoeA7tw6EXEpfwomlNLw7-d8i9KyOnwJWR8 spf2.0/pra include:amazon.com -all |
| 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.
A+Domain Intelligenceprimevideo.com — via MarkMonitor Inc., 25 years, 9 months old, hosted on AWSPASS
109 days
October 31, 2026
163 days
Issued by Amazon
25 years, 9 months
Registered October 31, 2000
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
3.165.113.31
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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