root-servers.net
Number 67 of the Top 100 · Tranco rank 75
root-servers.net names the thirteen DNS root servers, a.root-servers.net to m.root-servers.net, run by twelve separate organizations. Every lookup on the internet starts with them, which is why the name is so common.
Can root-servers.net be forged?
Can root-servers.net be forged?
Yes. There is no DMARC record, so each receiver decides alone.
- The exact name
- no DMARC record
- Names that copy
- 21 registered lookalikes can send mail. DMARC never sees them. See them →
What we noticed
- The domain publishes no SPF record.
- The domain has no DMARC record, so a receiver has no instruction for mail that fails.
- The domain has no SPF record.
Senders it names none named
These are the services the records name. A record can name a service no longer used, and a sender can sign without being named.
SPFNo SPF record
DKIM0 keys found
We look under the selectors of the services the records name. A domain can have keys we do not find.
Sending names 1 name, 0 at reject
| Name | Policy | SPF lookups | Reports to |
|---|---|---|---|
| i.root-servers.net | absent (inherited) | — | — |
ReportsNo reports asked for
Aggregate reports (rua) go to nobody. No failure reports are asked for.
Transport MTA-STS none · TLS-RPT none · BIMI none
MTA-STS asks senders to deliver to root-servers.net over encrypted connections only. TLS-RPT asks for reports when they cannot. BIMI shows a logo beside mail that passes DMARC at quarantine or reject.
Read on Oct 28, 2026. Check it again yourself →
Watch your own domain's mail this way: Sender Security · the DMARC Report