Skip to content
https://www.youtube.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
8 PASS 8 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
DNS Records
16 A records, 254 ms lookup
REVIEW
16 A records, 254 ms lookup
Info::
Resolves to 16 IPv4 address(es)
Got: 172.217.29.142, 172.217.28.46, 172.217.28.174, 172.217.30.110, 172.217.28.78, 142.251.135.238, 172.217.29.110, 172.217.28.206, 142.250.78.110, 172.217.28.142, 172.217.30.78, 142.250.78.142, 172.217.30.14, 172.217.29.238, 142.250.219.238, 142.250.219.206
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2800:3f0:4001:814::200e, 2800:3f0:4001:815::200e, 2800:3f0:4001:80e::200e, 2800:3f0:4001:80d::200e
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: youtube-ui.l.google.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (254 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 254 ms
A172.217.29.142, 172.217.28.46, 172.217.28.174, 172.217.30.110, 172.217.28.78, 142.251.135.238, 172.217.29.110, 172.217.28.206, 142.250.78.110, 172.217.28.142, 172.217.30.78, 142.250.78.142, 172.217.30.14, 172.217.29.238, 142.250.219.238, 142.250.219.206
AAAA2800:3f0:4001:814::200e, 2800:3f0:4001:815::200e, 2800:3f0:4001:80e::200e, 2800:3f0:4001:80d::200e
CNAMEyoutube-ui.l.google.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 254 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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)

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

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/20 IPs match cert SAN
REVIEW
0/20 IPs match cert SAN
Info::
PTR for 172.217.29.142 does not match any cert SAN: gru06s47-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.28.46 does not match any cert SAN: pngrub-ab-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.28.174 does not match any cert SAN: pngrub-ae-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.30.110 does not match any cert SAN: gru06s35-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.28.78 does not match any cert SAN: pngrub-ac-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.135.238 does not match any cert SAN: pngrub-aa-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.29.110 does not match any cert SAN: pngrua-ac-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.28.206 does not match any cert SAN: pngrub-af-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.250.78.110 does not match any cert SAN: bog02s17-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.28.142 does not match any cert SAN: gru09s09-in-f142.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.30.78 does not match any cert SAN: pngrua-aj-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.250.78.142 does not match any cert SAN: pngrua-by-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.30.14 does not match any cert SAN: rio01s23-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 172.217.29.238 does not match any cert SAN: pngrua-ag-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.250.219.238 does not match any cert SAN: pngrua-al-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.250.219.206 does not match any cert SAN: gru06s64-in-f14.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR lookup failed for 2800:3f0:4001:814::200e: lookup 2800:3f0:4001:814::200e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2800:3f0:4001:815::200e: lookup 2800:3f0:4001:815::200e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2800:3f0:4001:80e::200e: lookup 2800:3f0:4001:80e::200e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2800:3f0:4001:80d::200e: lookup 2800:3f0:4001:80d::200e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Multi-Resolver DNS Speed
Mean 39ms across 3 resolvers (spread 115ms)
REVIEW
Mean 39ms across 3 resolvers (spread 115ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 1ms
Got: 1ms via 1.1.1.1:53
Info::
Google: 116ms
Got: 116ms via 8.8.8.8:53
B
TLS Certificate Expiry & Recommendations
63 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.youtube.com

https://www.youtube.com

409 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.youtube.com200409 msHTTP/1.1ESF
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2800:3f0:4001:814::200e, 2800:3f0:4001:815::200e, 2800:3f0:4001:80e::200e, 2800:3f0:4001:80d::200e
Got: 2 ms connect
IPv6 Ready
AAAA Records 2800:3f0:4001:814::200e, 2800:3f0:4001:815::200e, 2800:3f0:4001:80e::200e, 2800:3f0:4001:80d::200e Connection Reachable (2 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+
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
youtube.com — via MarkMonitor Inc., 21 years, 6 months old
PASS
youtube.com — via MarkMonitor Inc., 21 years, 6 months old
Info::
Domain registered until Feb 15, 2027 (9 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

273 days

February 15, 2027

SSL certificate

63 days

Issued by Google Trust Services

Domain age

21 years, 6 months

Registered February 15, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2800:3f0:4001:81a::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, 6 months ago)
Expires February 15, 2027 (9 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 2800:3f0:4001:81a::200e
Data source: rdap (0.5s)

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

Connection waterfall

DNS Lookup 2 ms TCP Connect 2 ms TLS Handshake 201 ms Server Processing 252 ms Content Transfer 294 ms
A+
Health Check Endpoint
Health endpoint at https://www.youtube.com/health (HTTP 200)
PASS
Health endpoint at https://www.youtube.com/health (HTTP 200)
Info::
Public health endpoint at https://www.youtube.com/health
Got: https://www.youtube.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback