Analysis History
View all DNS analysis records
| Domain | Email Security | Date | Actions |
|---|---|---|---|
|
Critical Risk
3 to Fix
media.g-my.com
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:43 UTC
v26.46.24 · 49.0s |
|
|
Critical Risk
3 to Fix
qualysperiscope.com
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:42 UTC
v26.46.24 · 67.6s |
|
|
Critical Risk
3 to Fix
www.cnn.com
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:41 UTC
v26.46.24 · 21.8s |
|
|
Critical Risk
3 to Fix
www.cnn.com
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:37 UTC
v26.46.24 · 60.5s |
|
|
Low Risk
2 to Fix
tuta.io
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:10 UTC
v26.46.24 · 12.9s |
|
|
Low Risk
2 to Fix
tuta.io
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:10 UTC
v26.46.24 · 12.1s |
|
|
Low Risk
g-my.com
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:09 UTC
v26.46.24 · 60.5s |
|
|
Low Risk
2 to Fix
tuta.io
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:09 UTC
v26.46.24 · 60.5s |
|
|
Low Risk
1 to Fix
932.moe
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:08 UTC
v26.46.24 · 2.6s |
|
|
High Risk
2 to Fix
glendun.com.au
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:04 UTC
v26.46.24 · 28.3s |
|
|
Low Risk
1 to Fix
932.moe
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:01 UTC
v26.46.24 · 9.2s |
|
|
Low Risk
1 to Fix
932.moe
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:01 UTC
v26.46.24 · 5.1s |
|
|
Low Risk
1 to Fix
932.moe
|
SPF
DMARC
DKIM
|
20 Apr 2026 00:00 UTC
v26.46.24 · 5.3s |
|
|
Low Risk
1 to Fix
932.moe
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:59 UTC
v26.46.24 · 60.5s |
|
|
Low Risk
leeashley.net
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:53 UTC
v26.46.24 · 9.2s |
|
|
Critical Risk
3 to Fix
example.co.uk
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:51 UTC
v26.46.24 · 62.4s |
|
|
Critical Risk
3 to Fix
hogwarts.steinr.eu
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:51 UTC
v26.46.24 · 62.5s |
|
|
Low Risk
1 to Fix
steinr.eu
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:50 UTC
v26.46.24 · 8.4s |
|
|
Low Risk
1 to Fix
steinr.eu
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:48 UTC
v26.46.24 · 60.5s |
|
|
High Risk
1 to Fix
cirsa.com
|
SPF
DMARC
DKIM
|
19 Apr 2026 23:48 UTC
v26.46.24 · 60.5s |
We use two cookies, both essential:
_csrf— Prevents cross-site request forgery. Required for form submissions. Security-only._dns_session— Only exists if you choose to sign in. No account required to use DNS Tool.
We log your IP address for two reasons: rate limiting (so nobody abuses the service) and security (identifying malicious actors and complying with legal obligations). We check source geography for analysis accuracy — DNS responses vary by region, and knowing which resolver answered from where makes the science better.
No tracking cookies. No analytics cookies. No ad networks. No data brokers. Our code is open-core — the application framework is publicly available under BUSL-1.1 with timed Apache-2.0 conversion. Verify it yourself.
If you create an account and want out, account deletion removes your login and scan history. Public domain analyses remain available because they contain only public DNS records, already hashed. Full details: Privacy Policy.