Scan history
Security checks — sorted by severity
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
Strengths: Mail handled by Google Workspace; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
DNS CAA Records
Strengths: CAA records configured at youtube.com (1 record(s)); Authorised CAs: pki.goog. Issues: No iodef record — CA violations won't be reported to the domain owner.
Strengths: CAA records configured at youtube.com (1 record(s)); Authorised CAs: pki.goog. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Strengths: 4 nameservers configured (ns2.google.com, ns3.google.com, ns4.google.com, ns1.google.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (google.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 4 nameservers configured (ns2.google.com, ns3.google.com, ns4.google.com, ns1.google.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (google.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Security Headers
4/5 security headers present. Missing: Referrer-Policy. Quality issues: CSP: 'unsafe-eval' allows eval() — weakens XSS protection; CSP: no default-src fallback directive.
4/5 security headers present. Missing: Referrer-Policy. Quality issues: CSP: 'unsafe-eval' allows eval() — weakens XSS protection; CSP: no default-src fallback directive.
Cookie Security
Strengths: 7 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/7 cookie(s) missing SameSite attribute (GPS).
Strengths: 7 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/7 cookie(s) missing SameSite attribute (GPS).
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
security.txt (RFC 9116)
Strengths: security.txt found with 4 field(s); Contact: https://g.co/vulnz, mailto:[email protected]; Encryption key provided for secure reporting; Disclosure policy: https://g.co/vrp. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
Strengths: security.txt found with 4 field(s); Contact: https://g.co/vulnz, mailto:[email protected]; Encryption key provided for secure reporting; Disclosure policy: https://g.co/vrp. Issues: Missing 'Expires' field (required by RFC 9116); Not PGP signed (recommended for authenticity).
HSTS Header
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector1).
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector1).
CVE Exposure
Detected technologies: ESF. No version information exposed — CVE matching not possible (this is good practice).
Detected technologies: ESF. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 787 certificates logged in CT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 787 certificates logged in CT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1+ items
Steps to improve youtube.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
DNS Configuration
Without DNSSEC, DNS responses for youtube.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec youtube.com
See all 1 remaining recommendation
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
youtube.com scored 92/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, TLS Protocol Support, security.txt (RFC 9116) all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How youtube.com compares
Grade distribution across 2688 companies we've scanned. youtube.com scores better than 92% of them.
88
A+
27
A
198
A-
202
B+
76
B
376
B-
138
C+
117
C
348
C-
123
D+
96
D
266
D-
633
F
youtube.com — Grade A- (92/100)
2688 companies scanned
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: selector1).
SPF Record
Present
v=spf1 include:google.com mx -all
Security Headers
4/5 present
Missing: Referrer-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 787 certificates logged in CT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns2.google.com, ns3.google.com, ns4.google.com, ns1.google.com); SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: All nameservers are from a single provider (google.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Similar companies
Other domains with comparable security profiles.
