All data displayed is public and provided by the DNS system. Use of this website is subject to our Terms of Service.
Last checked about 9 hours ago
Your domain has strong email authentication. A few improvements can get you to a perfect score.
Upgrade DMARC policy to reject for stronger protection
DMARC improvement
42 / 50 points
DMARC record is valid and configured correctly.
v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected];
Policy (p)
quarantine
DKIM Alignment (adkim)
Relaxed (default)
SPF Alignment (aspf)
Relaxed (default)
Verification successful
Verification successful
You can add our monitoring system alongside your existing setup. DMARC supports multiple mailto: addresses, giving you additional visibility and backup reporting.
15 / 20 points
BIMI Record Found and Looks Good
v=BIMI1; l=https://assets.tumblr.com/images/favicons/favicon-bimi.svg; a=;
https://assets.tumblr.com/images/favicons/favicon-bimi.svg
image/svg+xml
Note: We do not parse SVG content for safety.
No certificate URL provided (a=). Optional when using self-asserted logos.
30 / 30 points
SPF record is valid.
v=spf1 include:_spf.google.com include:_spf.automattic.com include:sendgrid.net include:mail.zendesk.com include:21055259.spf05.hubspotemail.net -all
Syntax Check
OK
DNS Lookup Count
6 / 10 max
Root-level mechanisms requiring DNS queries: 5.
Void Lookups
0 / 2 max
Fail: Reject emails from unauthorized servers (recommended for production)
Grouped by DNS record source (includes and sub-includes)
This record also contains:
SPF record found
tumblr.com
TXT Record
v=spf1 ip4:74.125.0.0/16 ip4:209.85.128.0/17 ip6:2001:4860:4000::/36 ip6:2404:6800:4000::/36 ip6:2607:f8b0:4000::/36 ip6:2800:3f0:4000::/36 ip6:2a00:1450:4000::/36 ip6:2c0f:fb50:4000::/36 ~all
Processed recursively per RFC 7208
SPF record found
tumblr.com
TXT Record
v=spf1 ip4:192.0.64.0/18 ip4:195.234.109.226/32 ~all
Processed recursively per RFC 7208
SPF record found
tumblr.com
TXT Record
v=spf1 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:134.128.64.0/19 ip4:134.128.96.0/19 include:ab.sendgrid.net ~all
Processed recursively per RFC 7208
SPF record found
sendgrid.net
TXT Record
v=spf1 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ~all
Processed recursively per RFC 7208
SPF record found
tumblr.com
TXT Record
v=spf1 ip4:103.151.192.0/23 ip4:185.12.80.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:216.198.0.0/18 ~all
Processed recursively per RFC 7208
SPF record found
tumblr.com
TXT Record
v=spf1 ip4:3.93.157.0/24 ip4:3.210.190.0/24 ip4:18.208.124.128/25 ip4:54.174.52.0/24 ip4:54.174.57.0/24 ip4:54.174.59.0/24 ip4:54.174.60.0/23 ip4:54.174.63.0/24 ip4:108.179.144.0/20 ip4:139.180.17.0/24 ip4:141.193.184.32/27 ip4:141.193.184.64/26 ip4:141.193.184.128/25 ip4:141.193.185.32/27 ip4:141.193.185.64/26 ip4:141.193.185.128/25 ip4:143.244.80.0/20 ip4:158.247.16.0/20 ip4:216.139.64.0/19 -all
Processed recursively per RFC 7208
How tumblr.com configures email authentication
v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected];
v=spf1 include:_spf.google.com include:_spf.automattic.com include:sendgrid.net include:mail.zendesk.com include:21055259.spf05.hubspotemail.net -all
v=BIMI1; l=https://assets.tumblr.com/images/favicons/favicon-bimi.svg; a=;
Configuration changes will appear here when detected
Run a free email authentication check (DMARC, SPF, BIMI).
We will generate a shareable URL for your domain.
Try popular examples: google.com, amazon.com, booking.com
Discover how other organizations configure their email authentication
Frequently checked
Reject policy + valid SPF
Also using quarantine
Showing domains checked by our users. All data is from public DNS records.
We analyze your domain's email authentication: DMARC policy and alignment, SPF record and includes, and BIMI logo/CV when present.
Healthy authentication improves delivery and blocks spoofing. Major inbox providers increasingly require DMARC and robust SPF/DKIM practices for senders.
Don't rely on snapshots. Get the most accurate, real-time insights into your email delivery and reputation with DMARCTrust.