B75/100

youtube.com

Name: youtube.com email authentication report
Creator: MailAuthWatch
License: https://creativecommons.org/publicdomain/zero/1.0/

1 fix stands between this domain and a clean A. 2 items below, ordered by how much inbox they are costing you. Measured 0s ago from public DNS in 68 ms.

SPF PASSDKIM REVOKED ONLYDMARC REJECTMX OK

Monitor this domain Re-run check

Fix these, in this order, or hand the list to your agent

ranked by impact

The only DKIM selector found (selector1) is revoked.

A selector published with an empty key tells receivers to fail any mail signed with it, and no active key was found under common selectors.

Do this: publish a new key under an active selector, or add your real selector to the check if it is one we did not probe.

No DKIM key found under 79 common selectors.

Either DKIM signing is off, or it uses a selector we did not probe. Without DKIM, forwarded mail and anything that breaks SPF fails DMARC.

Do this: in Google Admin go to Apps → Google Workspace → Gmail → Authenticate email, generate a 2048-bit key with selector "google", publish the TXT record, then click Start authentication.

Records found

SPF · TXT

v=spf1 include:google.com mx -all

DMARC · _dmarc.youtube.com

v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com

DKIM · 0 of 79 selectors

none under common selectors

MX · Google Workspace

0 smtp.google.com

Fix this with your AI agent

AGENT-READY

A prompt built only from what was measured: the records as published, 2 tasks in order, exact record values and Google Cloud DNS commands, guardrails, and how to verify. Paste it into Claude, Cursor, Copilot or ChatGPT.

# Fix email authentication for youtube.com

You are working on the DNS and mail configuration for youtube.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade B (75/100).
Report: https://www.mailauthwatch.com/check/youtube.com

## What is published right now (do not assume anything else)
- SPF (TXT youtube.com): v=spf1 include:google.com mx -all   — valid, 3 of 10 lookups
- DMARC (TXT _dmarc.youtube.com): v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
- DKIM: no key found under 79 common selectors; revoked: selector1
- MX: smtp.google.com  → Google Workspace
- Nameservers: ns2.google.com, ns4.google.com …  → records are managed in Google Cloud DNS

## Tasks, in order of impact
…

# Fix email authentication for youtube.com

You are working on the DNS and mail configuration for youtube.com.
Measured by MailAuthWatch on 17 Oct 2026 from public DNS. Grade B (75/100).
Report: https://www.mailauthwatch.com/check/youtube.com

## What is published right now (do not assume anything else)
- SPF (TXT youtube.com): v=spf1 include:google.com mx -all   — valid, 3 of 10 lookups
- DMARC (TXT _dmarc.youtube.com): v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com
- DKIM: no key found under 79 common selectors; revoked: selector1
- MX: smtp.google.com  → Google Workspace
- Nameservers: ns2.google.com, ns4.google.com …  → records are managed in Google Cloud DNS

## Tasks, in order of impact
### 1. The only DKIM selector found (selector1) is revoked.
Why: A selector published with an empty key tells receivers to fail any mail signed with it, and no active key was found under common selectors.
Add TXT record:
  google._domainkey.youtube.com  TXT  <value from Google Admin>   (value comes from the provider step below)
Publish a new key under an active selector:
Google Admin → Apps → Google Workspace → Gmail → Authenticate email → select the domain → Generate new record (2048-bit, selector "google").
Publish the TXT record it shows, then click "Start authentication".
Where: Cloud DNS → the zone → Add standard.

### 2. No DKIM key found under 79 common selectors.
Why: Either DKIM signing is off, or it uses a selector we did not probe. Without DKIM, forwarded mail and anything that breaks SPF fails DMARC.
Add TXT record:
  google._domainkey.youtube.com  TXT  <value from Google Admin>   (value comes from the provider step below)
Google Admin → Apps → Google Workspace → Gmail → Authenticate email → select the domain → Generate new record (2048-bit, selector "google").
Publish the TXT record it shows, then click "Start authentication".
Where: Cloud DNS → the zone → Add standard.

## Rules
- Publish exactly one SPF record; never add a second v=spf1 TXT.
- Do not remove any include: or ip4: you cannot account for; mail may depend on it.
- Do not set DMARC to p=reject in one step; stage through p=none → quarantine → reject.
- Show the planned DNS changes as a diff (record, old value, new value) before applying them.
- If you cannot access Google Cloud DNS or Google Workspace, stop and say exactly what access you need.

## Verify
  dig +short TXT google._domainkey.youtube.com
  dig +short TXT youtube.com
  dig +short TXT _dmarc.youtube.com
Then open https://www.mailauthwatch.com/check/youtube.com?fresh=1 and confirm:
  DKIM found. Target grade: A.

## Report back
List each record you changed (name, type, old value, new value), what you verified, and anything you could not do.

Open in Claude Open in ChatGPT fix.md

Your agent, your DNS, your review. MailAuthWatch never changes records; it writes the plan and re-checks the result.

Grade history

Free checks keep nothing. Monitoring records every daily measurement and alerts you on change.

History goes back as far as your subscription.

SPF OK

v=spf1 include:google.com mx -all

DNS lookups: 3 of 10 allowed
Final mechanism: -all

OK No problems detected.

Include tree

3 / 10

youtube.com+1 direct

└─ include:google.com+2

└─ _spf.google.com

DKIM Not found

DKIM selectors cannot be listed from DNS, so 79 selectors used by common providers were probed. "Not found" means none of those selectors exist; the domain may still sign with a custom selector.

WarningThe only DKIM selector found (selector1) is revoked. Mail signed with it fails DKIM.

DMARC OK

v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com

Policy: p=reject
Applies to: 100% of failing mail
Aggregate reports: mailto:mailauth-reports@google.com

OK No problems detected.

Mail exchange and extras

OK No problems detected.

MTA-STS: Not published optional: enforces TLS for inbound mail
TLS-RPT: Not published
BIMI: Not published optional: brand logo in inboxes, requires p=quarantine or reject

How the grade is calculated

Score 75/100. SPF present and valid. SPF ends with -all. DMARC present and valid. DMARC policy is reject. DMARC aggregate reporting enabled. SPF contributes up to 35 points, DKIM up to 25, DMARC up to 40 (policy strength and reporting). Any critical issue caps the grade at C. Lookups that failed are shown as "not measured" and never counted as missing.

Check another domain:

Other recently graded domains

Public checks from the last few days. Every report is re-measured from DNS when opened.

live

DomainSPFDKIMDMARCGrade

azure.com2 lookupsnot foundp=rejectB instagram.com6 lookups1024-bitp=rejectA spotify.com6 lookups2048-bitp=rejectA linkedin.com2 lookups1024-bitp=rejectA google.com1 lookupsnot foundp=rejectB live.com5 lookups2048-bitp=noneB amazon.com4 lookups1024-bitp=quarantineA github.com10 lookups2048-bitp=quarantineA gmail.com1 lookupsnot foundp=noneC microsoftonline.com6 lookupsnot foundp=rejectB salesforce.com4 lookups2048-bitp=rejectA mailauthwatch.com1 lookups1024-bitp=rejectA