Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNS Records11 A records, 37 ms lookupREVIEW
| A | 142.251.218.206, 142.251.218.142, 142.251.214.46, 142.251.218.238, 142.251.219.14, 142.251.219.46, 172.217.12.110, 142.251.218.78, 142.251.218.174, 142.251.218.110, 142.251.46.238 |
| AAAA | 2607:f8b0:4002:c09::5b, 2607:f8b0:4002:c09::88, 2607:f8b0:4002:c09::be, 2607:f8b0:4002:c09::5d |
| CNAME | youtube-ui.l.google.com |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
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
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
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)
BTLS Certificate Expiry & Recommendations61 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
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
A+Redirect ChainNo redirects — direct accessPASS
https://www.youtube.com
172 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://www.youtube.com | 200 | 172 ms | HTTP/1.1 | ESF |
A+Crawlabilityrobots.txt present, sitemap with 20 URLsPASS
# 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
- https://www.youtube.com/sitemaps/misc.xm...
- https://www.youtube.com/kids/sitemap.xml
- https://www.youtube.com/trends/sitemap.x...
- https://about.youtube/sitemap.xml
- https://www.youtube.com/jobs/sitemap.xml
- https://www.youtube.com/creators/sitemap...
- https://www.youtube.com/csai-match/sitem...
- https://www.youtube.com/originals/guidel...
- https://contributors.youtube.com/sitemap...
- https://socialimpact.youtube.com/sitemap...
- https://vr.youtube.com/sitemap.xml
- https://artists.youtube/sitemap.xml
- https://www.youtube.com/measurementprogr...
- https://www.youtube.com/go/family/sitema...
- https://www.youtube.com/yt/terms/sitemap...
- https://www.youtube.com/howyoutubeworks/...
- https://www.youtube.com/myfamily/sitemap...
- https://health.youtube/sitemap.xml
- https://news.youtube/sitemap.xml
- https://research.youtube/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: www
HTTP → HTTPS
Consistent
A+Domain Intelligenceyoutube.com — via MarkMonitor Inc., 21 years, 5 months old, hosted on Google CloudPASS
244 days
February 15, 2027
61 days
Issued by Google Trust Services
21 years, 5 months
Registered February 15, 2005
Not enabled
Protects against DNS spoofing
Google Cloud
ASN AS15169
142.251.214.110
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
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