CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~80m ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW540 curated domains not reachablelast probe, steadySITE ERRORS33,827 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 150,322 sites429 rate-limit / 403 bot-block, a posture signal

edgeauditor.com

Observed Jul 26, 2026, 11:25 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of edgeauditor.com was taken 10d ago

edgeauditor.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting edgeauditor.com under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch edgeauditor.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byMicrosoft 365
Secured byLet's Encrypt
7 subdomains · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 04:54 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat edgeauditor.com actually stands on - every host below is a signed observation
edgeauditor.com
A / AAAA
18.188.27.27
unattributedserves the site
NS
ns1-09.azure-dns.comns2-09.azure-dns.netns3-09.azure-dns.orgns4-09.azure-dns.info
azure-dns.com + azure-dns.net + moreanswers its DNS
MX
edgeauditor-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
mail.edgeauditor.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 18.188.27.27

MX 1

  • 0edgeauditor-com.mail.protection.outlook.com

TXT 9

  • v=spf1 include:sendgrid.net include:emsd1.com include:spf.protection.outlook.com include:spf.emailsignatures365.com ~all
  • v=BIMI1; l=https://www.edgeauditor.com/a/img/EA.svg;
  • v=DMARC1; p=reject; rua=mailto:dmarc@edgeauditor.com; ruf=mailto:dmarc@edgeauditor.com; fo=1
  • v=spf1 include:sendgrid.net include:emsd1.com include:spf.protection.outlook.com include:spf.emailsignatures365.com ~all
  • v=BIMI1; l=https://www.edgeauditor.com/a/img/EA.svg;
  • v=spf1 include:sendgrid.net include:emsd1.com include:spf.protection.outlook.com include:spf.emailsignatures365.com ~all
  • v=BIMI1; l=https://www.edgeauditor.com/a/img/EA.svg;
  • v=spf1 include:sendgrid.net include:emsd1.com include:spf.protection.outlook.com include:spf.emailsignatures365.com ~all
  • v=BIMI1; l=https://www.edgeauditor.com/a/img/EA.svg;

NS 4

  • ns1-09.azure-dns.com
  • ns2-09.azure-dns.net
  • ns3-09.azure-dns.org
  • ns4-09.azure-dns.info

SOA 1

  • ns1-09.azure-dns.com support.edgeauditor.com

TLS Certificates (3)

Common NameIssuerExpires
mail.edgeauditor.com C=US, O=Let's Encrypt, CN=YR1 Sun, 20 Sep 2026 01:12:49 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (7)

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_53d197666db68ed6
Output Hash
0f444323ebd6ad4c8b06b2621105af6e456d10b300419ce36b8887b0840ea847
Signature
ed25519:0b7e3444fff96453c16c4b8a5ac22c86b78c42e1c1318f65f8294b08c38478cef1e08d7f7538db85166019d0985c09638c18cf49b1b60238e249137dc4d09009
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser