Skip to content
https://youtube.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.youtube.com/
200https://youtube.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://youtube.com/ → https://youtube.com/

Consistent

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

Certificate validity

59
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
1 A records, 23 ms lookup
PASS
1 A records, 23 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 142.251.209.46
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a00:1450:4002:406::200e
Info::
4 nameserver(s) configured
Got: ns1.google.com, ns3.google.com, ns2.google.com, ns4.google.com
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: 23 ms
Got: 23 ms
A142.251.209.46
AAAA2a00:1450:4002:406::200e
CNAME—
NSns1.google.com, ns3.google.com, ns2.google.com, ns4.google.com
MX
0 smtp.google.com
TXT
google-site-verification=QtQWEwHWM8tHiJ4s-jJWzEQrD_fF3luPnpzNDH-Nw-w
facebook-domain-verification=64jdes7le4h7e7lfpi22rijygx58j1
SPF v=spf1 include:google.com mx -all
CAALookup not available with standard resolver
Resolved in 23 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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), 476 ms total
PASS
1 redirect(s), 476 ms total
Info::
Single redirect
Got: https://youtube.com → https://www.youtube.com/ (301)
Info::
WWW normalization redirect

https://youtube.com

177 ms · HTTP/1.1

301

https://www.youtube.com/

299 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://youtube.com301177 msHTTP/1.1ESF
2https://www.youtube.com/200299 msHTTP/1.1ESF

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (33 ms)
PASS
IPv6 reachable (33 ms)
Info::
IPv6 is configured and reachable at 2a00:1450:4002:406::200e
Got: 33 ms connect
IPv6 Ready
AAAA Records 2a00:1450:4002:406::200e Connection Reachable (33 ms)
A+
Crawlability
robots.txt present, sitemap with 20 URLs
PASS
robots.txt present, sitemap with 20 URLs
Info::
robots.txt is present
Got: 766 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 766 B Sitemaps referenced 2 User-agents Mediapartners-Google*, * Blocking No — crawling allowed
# robots.txt file for YouTube
# Created in the distant future (the year 2000) after
# the robotic uprising of the mid 90's which wiped out all humans.

User-agent: Mediapartners-Google*
Disallow:

User-agent: *
Disallow: /api/
Disallow: /comment
Disallow: /feeds/videos.xml
Disallow: /file_download
Disallow: /get_video
Disallow: /get_video_info
Disallow: /get_midroll_info
Disallow: /live_chat
Disallow: /login
Disallow: /qr
Disallow: /results
Disallow: /signup
Disallow: /t/terms
Disallow: /timedtext_video
Disallow: /verify_age
Disallow: /watch_ajax
Disallow: /watch_fragments_ajax
Disallow: /watch_popup
Disallow: /watch_queue_ajax
Disallow: /youtubei/

Sitemap: https://www.youtube.com/sitemaps/sitemap.xml
Sitemap: https://www.youtube.com/product/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 20 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
youtube.com — via MarkMonitor Inc., 21 years, 5 months old
PASS
youtube.com — via MarkMonitor Inc., 21 years, 5 months old
Info::
Domain registered until Feb 15, 2027 (10 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

246 days

February 15, 2027

SSL certificate

59 days

Issued by Google Trust Services

Domain age

21 years, 5 months

Registered February 15, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:1450:4002:406::200e

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 February 15, 2005 (21 years, 5 months ago)
Expires February 15, 2027 (10 months)
Last Updated January 14, 2026
Name Servers ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
DNSSEC Not enabled
Hosting
IP Address 2a00:1450:4002:406::200e
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 23 ms TCP Connect 33 ms TLS Handshake 69 ms Server Processing 77 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