Skip to content
https://netflix.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
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.

B
Redirect Chain
2 redirect(s), 850 ms total
REVIEW
2 redirect(s), 850 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.netflix.com/
Info::
Redirect overhead: 850 ms total
Got: 850 ms
Info::
Cross-domain redirect detected

https://netflix.net

345 ms · HTTP/1.1

301

https://www.netflix.com/

153 ms · HTTP/1.1

302

https://www.netflix.com/nl-en/

352 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://netflix.net301345 msHTTP/1.1
2https://www.netflix.com/302153 msHTTP/1.1envoy
3https://www.netflix.com/nl-en/200352 msHTTP/1.1envoy

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

C
Crawlability
Action
robots.txt present, sitemap with 23414 URLs
REVIEW
robots.txt present, sitemap with 23414 URLs
Info::
robots.txt is present
Got: 3790 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 23414 entries
Info::
Sitemap index with 23414 child sitemaps
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 3790 B Sitemaps referenced 1 User-agents Baiduspider-video, SeznamBot, Twitterbot, Adidxbot, YandexMobileBot, Facebot, Claude-User, googlebot, Baiduspider-mobile, Baiduspider-image, NaverBot, Yeti, OAI-SearchBot, PerplexityBot, AdsBot-Google, Yahoo Pipes 1.0, YJ-WSC, bingbot, YandexWebmaster, ClaudeBot, Applebot, YandexSitelinks, ChatGPT-User, facebookexternalhit, GPTBot, Claude-SearchBot, Y!J-WSC, *, Baiduspider, YandexBot, Googlebot-Video, Yandex, YandexVideo, Google-Extended Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /

User-agent: googlebot
User-agent: Googlebot-Video
User-agent: Applebot
User-agent: bingbot
User-agent: Baiduspider
User-agent: Baiduspider-mobile
User-agent: Baiduspider-video
User-agent: Baiduspider-image
User-agent: NaverBot
User-agent: Y!J-WSC
User-agent: YJ-WSC
User-agent: Yeti
User-agent: Yandex
User-agent: YandexBot
User-agent: YandexMobileBot
User-agent: YandexVideo
User-agent: YandexWebmaster
User-agent: YandexSitelinks
User-agent: SeznamBot
User-agent: facebookexternalhit
User-agent: GPTBot
User-agent: ChatGPT-User
User-agent: OAI-SearchBot
User-agent: Google-Extended
User-agent: ClaudeBot
User-agent: Claude-User
User-agent: Claude-SearchBot
User-agent: PerplexityBot
Allow: /

Disallow: /accountstatus
Disallow: /AccountStatus
Disallow: /aui/inbound
Disallow: /authenticate
Disallow: /autologin
Disallow: /clearcookies
Disallow: /companies
Disallow: /editpayment
Disallow: /emailunsubscribe
Disallow: /error
Disallow: /eula
Disallow: /geooverride
Disallow: /help
Disallow: /imagelibrary
Disallow: /learnmorelayer
Disallow: /learnmorelayertv
Disallow: /login
Disallow: /loginhelp
Disallow: /loginhelp/lookup
Disallow: /loginhelpsucess
Disallow: /LoginHelp
Disallow: /password
Disallow: /logout
Disallow: /Logout
Disallow: /mcd
Disallow: /modernizr
Disallow: /n/
Disallow: /notamember
Disallow: /notfound
Disallow: /notices
Disallow: /nrdapp
Disallow: /optout
Disallow: /overviewblockseeother
Disallow: /popup/codewhatisthis
Disallow: /popupdetails
Disallow: /PopupDetails
Disallow: /popupprivacypolicy
Disallow: /privacypolicychanges
Disallow: /registration
Disallow: /rememberme
Disallow: /signout
Disallow: /signurl
Disallow: /subscriptioncancel
Disallow: /tastesurvey
Disallow: /termsofusechanges
Disallow: /tvsignup
Disallow: /upcomingevents
Disallow: /verifyidentity
Disallow: /whysecure

Disallow: /arabic
Disallow: /Arabic
Disallow: /chinese
Disallow: /Chinese
Disallow: /korean
Disallow: /Korean

Disallow: /airtel
Disallow: /anan
Disallow: /bouyguestelecom
Disallow: /britishairways
Disallow: /brutus
Disallow: /comhem
Disallow: /courts
Disallow: /csl
Disallow: /elisa
Disallow: /entertain
Disallow: /FireTV
Disallow: /firetv
Disallow: /freemonth
Disallow: /kpn
Disallow: /lg
Disallow: /maxis
Disallow: /Maxis
Disallow: /meo
Disallow: /Meo
Disallow: /orangefrance
Disallow: /Panasonic
Disallow: /panasonic
Disallow: /playstation
Disallow: /proximus
Disallow: /qantas
Disallow: /samsung
Disallow: /Sony
Disallow: /sony
Disallow: /talktalk
Disallow: /tdc
Disallow: /telenor
Disallow: /telfort
Disallow: /tim
Disallow: /virginaustralia
Disallow: /vodafone
Disallow: /vodafonedemobilelaunch
Disallow: /xboxone
Disallow: /xfinity
Disallow: /xs4all
Disallow: /ziggo

Disallow: /accountaccess
Disallow: /AccountAccess
Disallow: /BillingActivity
Disallow: /browse
Disallow: /browse/*
Allow: /browse/genre/*
Disallow: /CancelPlan
Disallow: /ChangePlan
Disallow: /changeplan
Disallow: /deviceManagement
Disallow: /DoNotTest
Disallow: /EditProfiles
Disallow: /email
Disallow: /EmailPreferences
Disallow: /entrytrap
Disallow: /HdToggle
Disallow: /LanguagePreferences
Disallow: /ManageDevices
Disallow: /ManageProfiles
Disallow: /MoviesYouveSeen
Disallow: /NewWatchInstantlyRSS
Disallow: /NewWatchInstantlyRSS/*
Disallow: /payment
Disallow: /Payment
Disallow: /phonenumber
Disallow: /pin
Disallow: /profiles
Disallow: /profiles/*
Disallow: /ProfilesGate
Disallow: /search
Disallow: /search/*
Disallow: /viewingactivity
Disallow: /WiViewingActivity
Disallow: /yourAccount
Disallow: /youraccount
Disallow: /YourAccount
Disallow: /YourAccountPayment

User-agent: AdsBot-Google
User-agent: Twitterbot
User-agent: Adidxbot
Allow: /

User-agent: Yahoo Pipes 1.0
User-agent: Facebot
Disallow: /
Allow: /tudum

Sitemap: https://www.netflix.com/sitemap/index
sitemap.xml 200 OK
Type Sitemap Index URLs 23414 entries Valid XML Yes
Child Sitemaps:
B
TLS Certificate Expiry & Recommendations
72 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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 Records
9 A records, 277 ms lookup
PASS
9 A records, 277 ms lookup
Info::
Resolves to 9 IPv4 address(es)
Got: 34.218.19.240, 52.31.48.193, 44.226.113.145, 34.252.74.1, 204.236.236.127, 107.20.175.192, 18.236.7.30, 46.137.171.215, 50.17.247.9
Info::
Has 9 IPv6 (AAAA) record(s)
Got: 2a05:d018:76c:b685::de70, 2a05:d018:76c:b680::de70, 2a05:d018:76c:b684::de70, 2600:1f14:62a:de81::de70, 2600:1f18:631e:2f81::de70, 2600:1f18:631e:2f82::de70, 2600:1f14:62a:de80::de70, 2600:1f14:62a:de82::de70, 2600:1f18:631e:2f80::de70
Info::
4 nameserver(s) configured
Got: ns-1079.awsdns-06.org, ns-1780.awsdns-30.co.uk, ns-293.awsdns-36.com, ns-963.awsdns-56.net
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
Warning::
DNS resolution is slow (277 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 277 ms
A34.218.19.240, 52.31.48.193, 44.226.113.145, 34.252.74.1, 204.236.236.127, 107.20.175.192, 18.236.7.30, 46.137.171.215, 50.17.247.9
AAAA2a05:d018:76c:b685::de70, 2a05:d018:76c:b680::de70, 2a05:d018:76c:b684::de70, 2600:1f14:62a:de81::de70, 2600:1f18:631e:2f81::de70, 2600:1f18:631e:2f82::de70, 2600:1f14:62a:de80::de70, 2600:1f14:62a:de82::de70, 2600:1f18:631e:2f80::de70
CNAME—
NSns-1079.awsdns-06.org, ns-1780.awsdns-30.co.uk, ns-293.awsdns-36.com, ns-963.awsdns-56.net
MX
10 mail.messaging.microsoft.com
TXT
398c25d8b1af44d9956dbc56ab55f2d8
lucid-verification=muk7HWG-zcu*czr5rbh
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 277 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
IPv6 Readiness
IPv6 reachable (26 ms)
PASS
IPv6 reachable (26 ms)
Info::
IPv6 is configured and reachable at 2a05:d018:76c:b685::de70, 2a05:d018:76c:b680::de70, 2a05:d018:76c:b684::de70, 2600:1f14:62a:de81::de70, 2600:1f18:631e:2f81::de70, 2600:1f18:631e:2f82::de70, 2600:1f14:62a:de80::de70, 2600:1f14:62a:de82::de70, 2600:1f18:631e:2f80::de70
Got: 26 ms connect
IPv6 Ready
AAAA Records 2a05:d018:76c:b685::de70, 2a05:d018:76c:b680::de70, 2a05:d018:76c:b684::de70, 2600:1f14:62a:de81::de70, 2600:1f18:631e:2f81::de70, 2600:1f18:631e:2f82::de70, 2600:1f14:62a:de80::de70, 2600:1f14:62a:de82::de70, 2600:1f18:631e:2f80::de70 Connection Reachable (26 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.netflix.net/
200https://netflix.net/

Preferred variant: non-www

HTTP → HTTPS

301http://netflix.net/ → https://www.netflix.com/

Consistent

A+
Domain Intelligence
netflix.net — via MarkMonitor Inc., 28 years, 9 months old
PASS
netflix.net — via MarkMonitor Inc., 28 years, 9 months old
Info::
Domain registered until Dec 7, 2027 (1 years, 7 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.
Domain expiry

511 days

December 7, 2027

SSL certificate

72 days

Issued by Google Trust Services

Domain age

28 years, 9 months

Registered December 8, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a05:d018:76c:b684::de70

Registrar

MarkMonitor Inc.

Unlocked 4 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 December 8, 1997 (28 years, 9 months ago)
Expires December 7, 2027 (1 years, 7 months)
Last Updated November 5, 2025
Name Servers ns-1079.awsdns-06.org, ns-1780.awsdns-30.co.uk, ns-293.awsdns-36.com, ns-963.awsdns-56.net
DNSSEC Not enabled
Hosting
IP Address 2a05:d018:76c:b684::de70
Data source: rdap (0.3s)

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 350 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
276 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
24 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
350 ms
Total Time Total request time from DNS lookup through full response.
350 ms

Connection waterfall

DNS Lookup 276 ms TCP Connect 24 ms TLS Handshake 27 ms Server Processing 24 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