Skip to content
https://imdb.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1585 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1585 B Sitemaps referenced 0 User-agents *, bingbot, GPTBot, Baiduspider, anthropic-ai, Claude-Web, CCbot, FacebookBot, Google-Extended, PiplBot Blocking No — crawling allowed
# robots.txt for https://www.imdb.com properties

# See https://m.imdb.com/robots.txt for the mDot equivalent

 
User-agent: *

Disallow: /OnThisDay

Disallow: /*/OnThisDay

Disallow: /ads/

Disallow: /*/ads/

Disallow: /ap/

Disallow: /*/ap/

Disallow: /register

Disallow: /*/register

Disallow: /registration/

Disallow: /*/registration/

Disallow: /search/name-text

Disallow: /*/search/name-text

Disallow: /search/title-text

Disallow: /*/search/title-text

Disallow: /find

Disallow: /*find

Disallow: /find$

Disallow: /*/find$

Disallow: /find/

Disallow: /*/find/

Disallow: /search/title/*

Disallow: /*/search/title/*

Disallow: /search/name/*

Disallow: /*/search/name/*

Disallow: /user/ur*/ratings

Disallow: /*/user/ur*/ratings

Disallow: /user/ur*/checkins

Disallow: /*/user/ur*/checkins

Disallow: /user/ur*/reviews

Disallow: /*/user/ur*/reviews

Disallow: /_json/*

Disallow: /*/_json/*

Disallow: /api/_ajax/*

Disallow: /*/api/_ajax/*

Disallow: /contribute/*

Disallow: /*/contribute/*

Disallow: /title/*/review/*

Disallow: /*/title/*/review/*

Disallow: /title/*/reviews

Disallow: /*/title/*/reviews

 
User-agent: Baiduspider

Disallow: /list/*

Disallow: /*/list/*

Disallow: /user/*

Disallow: /*/user/*

 
User-agent: bingbot

Disallow: /showtimes/location/*

Disallow: /*/showtimes/location/*


User-agent: anthropic-ai

Disallow: /

User-agent: Claude-Web

Disallow: /

User-agent: CCbot

Disallow: /

User-agent: FacebookBot

Disallow: /

User-agent: Google-Extended

Disallow: /

User-agent: GPTBot

Disallow: /

User-agent: PiplBot

Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
170 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

170
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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 Records
3 A records, 6 ms lookup
PASS
3 A records, 6 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 98.82.158.179, 44.215.137.99, 98.82.155.134
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns1.amzndns.co.uk, ns1.amzndns.com, ns1.amzndns.net, ns1.amzndns.org, ns2.amzndns.co.uk, ns2.amzndns.com, ns2.amzndns.net, ns2.amzndns.org
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 6 ms
Got: 6 ms
A98.82.158.179, 44.215.137.99, 98.82.155.134
AAAA
CNAME
NSns1.amzndns.co.uk, ns1.amzndns.com, ns1.amzndns.net, ns1.amzndns.org, ns2.amzndns.co.uk, ns2.amzndns.com, ns2.amzndns.net, ns2.amzndns.org
MX
10 amazon-smtp.amazon.com
TXT
TS1760027
MS=ms55779356
MS=ms74462343
IPROTA_D66964-XXX
SPF v=spf1 include:amazon.com -all
canva-site-verification=knObS_jT07ww5BsgiACF8g
docker-verification=800fa4c1-614f-4e2c-9ee5-c43ea1dc7831
google-site-verification=f3PqOeHGPuPaaRAkAPJ4bSO-O8bDQOohrmdwxtJAIIM
google-site-verification=uL7Y3ZHRGFE5c6a05OXtn2S2Vq6LfrtqsYlwszK0yl8
apple-domain-verification=0jFtlxygq-YPBzUgTNd2qDiTxb6TpG8Hf1qJcLlFb_w
box-domain-verification=ffea95cd0e0d61c302198367155b07e74fd534fa1d867662dc9bf996...
adobe-idp-site-verification=b6bcd3e5aaffc63607c8bf75744d9a0d1febc50dd7f389428e2a...
cisco-ci-domain-verification=5b0cade9b99903b93ec19495d546a72dbb24ecf17c3670b02bb...
atlassian-domain-verification=ZT4AapXgobCpXIWoNcd7gtMjZyOUdr4EDFMnFUWrqqqgdaQVbD...
CAALookup not available with standard resolver
Resolved in 6 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 56 ms total
PASS
1 redirect(s), 56 ms total
Info::
Single redirect
Got: https://imdb.com → https://www.imdb.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://imdb.com

https://imdb.com

27 ms · HTTP/1.1

302

https://www.imdb.com/

29 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://imdb.com30227 msHTTP/1.1Server
2https://www.imdb.com/20229 msHTTP/1.1Server

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

202https://www.imdb.com/
200https://imdb.com/

HTTP → HTTPS

301http://imdb.com/ https://imdb.com/

Consistent

A+
Domain Intelligence
imdb.com — via MarkMonitor Inc., 30 years, 8 months old, hosted on AWS
PASS
imdb.com — via MarkMonitor Inc., 30 years, 8 months old, hosted on AWS
Info::
Domain registered until Jan 4, 2027 (8 months remaining)
Info::
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.
Info::
Registrar: MarkMonitor Inc.
Warning::
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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

175 days

January 4, 2027

SSL certificate

170 days

Issued by Amazon

Domain age

30 years, 8 months

Registered January 5, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

98.82.158.179

Registrar

MarkMonitor Inc.

Unlocked 8 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 5, 1996 (30 years, 8 months ago)
Expires January 4, 2027 (8 months)
Last Updated October 31, 2025
Name Servers ns1.amzndns.co.uk, ns1.amzndns.com, ns1.amzndns.net, ns1.amzndns.org, ns2.amzndns.co.uk, ns2.amzndns.com, ns2.amzndns.net, ns2.amzndns.org
DNSSEC Not enabled
Hosting
IP Address 98.82.158.179
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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

A+
HTTP Probe Timing
Total 29 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
9 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
29 ms
Total Time Total request time from DNS lookup through full response.
30 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 7 ms TLS Handshake 9 ms Server Processing 9 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback