gmail.com
domain Monitoring only DMARC p=noneMail by Google Workspace · Mail handled by gmail-smtp-in.l.google.com, alt1.gmail-smtp-in.l.google.com, alt2.gmail-smtp-in.l.google.com, alt3.gmail-smtp-in.l.google.com, alt4.gmail-smtp-in.l.google.com
Findings
-
Caution DKIM selector 20230601 is revoked (empty key) DKIM-REVOKED
-
Caution DKIM selector 20221208 is revoked (empty key) DKIM-REVOKED
-
Caution DKIM selector 20210112 is revoked (empty key) DKIM-REVOKED
-
Caution DKIM selector 20161025 is revoked (empty key) DKIM-REVOKED
-
Caution DMARC policy is p=none (monitor only) DMARC-P-NONE
Failing mail is still delivered. Fine while collecting reports; move to quarantine or reject once legitimate sources align.
How to fix: Set p=quarantine (with pct= to ramp), then p=reject.
-
Caution Spoofing protection: monitoring only SPOOF-PARTIAL
DMARC exists but does not enforce; forged mail is still delivered.
How to fix: Move DMARC to p=quarantine or p=reject.
-
Pass gmail-smtp-in.l.google.com supports STARTTLS (TLSv1.3) SMTP-STARTTLS-OK
TLS_AES_256_GCM_SHA384
-
Pass alt1.gmail-smtp-in.l.google.com supports STARTTLS (TLSv1.3) SMTP-STARTTLS-OK
TLS_AES_256_GCM_SHA384
-
Pass SPF uses 1 of 10 permitted DNS lookups SPF-LOOKUPS-OK
-
Pass SPF delegates to _spf.google.com SPF-REDIRECT
The terminating policy comes from the redirected record.
-
Pass MTA-STS is in enforce mode MTASTS-ENFORCE
-
Pass TLS reporting (TLS-RPT) is enabled TLSRPT-OK
v=TLSRPTv1;rua=mailto:sts-reports@google.com
Mail servers (MX)
| Pref | Host | Address | Reverse DNS | SMTP (port 25) |
|---|---|---|---|---|
| 5 | gmail-smtp-in.l.google.com | 172.217.76.26, 2a00:1450:4009:c0f:0:0:0:1a | yulhrp-in-f26.1e100.net ✓ yulhrs-in-f26.1e100.net ✓ |
220 banner in 0 ms
STARTTLS TLSv1.3 TLS_AES_256_GCM_SHA384 cert: mx.google.com valid · until Dec 21 18:40:12 2026 GMT |
| 10 | alt1.gmail-smtp-in.l.google.com | 142.250.102.26, 2a00:1450:4025:402:0:0:0:1a | rb-in-f26.1e100.net ✓ rb-in-f26.1e100.net ✓ |
220 banner in 0 ms
STARTTLS TLSv1.3 TLS_AES_256_GCM_SHA384 cert: mx.google.com valid · until Dec 21 18:40:12 2026 GMT |
| 20 | alt2.gmail-smtp-in.l.google.com | 192.178.213.26, 2a00:1450:4013:c1e:0:0:0:1a | yugrqzs-in-f26.1e100.net ✓ yugrqzs-in-f26.1e100.net ✓ |
not tested |
| 30 | alt3.gmail-smtp-in.l.google.com | 142.251.127.27, 2a00:1450:4001:c21:0:0:0:1a | lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ |
not tested |
| 40 | alt4.gmail-smtp-in.l.google.com | 192.178.228.27, 2a00:1450:4025:4403:0:0:0:1a | yuskelf-in-f27.1e100.net ✓ yuskelf-in-f26.1e100.net ✓ |
not tested |
SPF
v=spf1 redirect=_spf.google.com
DNS lookups: 1 / 10 · terminates with redirectall
DMARC
v=DMARC1; p=none; sp=quarantine; rua=mailto:mailauth-reports@google.com
- Policy
- none
- Subdomains
- quarantine
- Alignment
- DKIM relaxed, SPF relaxed
- Reports to
- mailauth-reports@google.com
DKIM
20230601._domainkey · RSA revoked
20221208._domainkey · RSA revoked
20210112._domainkey · RSA revoked
20161025._domainkey · RSA revoked
Selectors are chosen by the sending service, so a key can exist under a name not tried here. The s= tag in a real message header names it.
Transport security
- MTA-STS
- enforce · mx: smtp.google.com, gmail-smtp-in.l.google.com, *.gmail-smtp-in.l.google.com · max_age 86400
- TLS-RPT
- v=TLSRPTv1;rua=mailto:sts-reports@google.com
- BIMI
- not published
Open relay test owners only
Checks whether each mail server accepts mail for recipients at other domains, which spammers exploit. Because the test sends SMTP commands to your server, it is only offered to verified owners.
Create an account and verify the domain to run this test.
