CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~2h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,518 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,266 sites429 rate-limit / 403 bot-block, a posture signal

lie2me.net

Observed Jul 27, 2026, 19:30 UTC (12d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of lie2me.net was taken 12d ago

lie2me.net is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lie2me.net 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 lie2me.net Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Signed observation on record.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 20:59 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 lie2me.net actually stands on - every host below is a signed observation
lie2me.net
A / AAAA
209.237.151.10
unattributedserves the site
NS
ns58.worldnic.comns57.worldnic.com
worldnic.comanswers its DNS
MX
west.smtp.mx.exch122.serverdata.net
serverdata.netreceives its email

DNS Records

A 1

  • 209.237.151.10

MX 1

  • 10west.smtp.mx.exch122.serverdata.net

TXT 5

  • v=spf1 include:spf.serverdata.net -all
  • v=spf1 include:hostaccount.com ~all
  • v=spf1 include:hostaccount.com ~all
  • v=spf1 include:hostaccount.com ~all
  • v=spf1 include:hostaccount.com ~all

NS 2

  • ns58.worldnic.com
  • ns57.worldnic.com

SOA 1

  • NS57.WORLDNIC.COM namehost.WORLDNIC.COM

TLS Certificates (0)

None.

Subdomains (0)

None observed.

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_cba6f88dab933b66
Output Hash
4f6c3df66764d3e4fb12bc29fc59c4e16bfeaf8f75d85fc96cbe257b49b2f3d8
Signature
ed25519:4dd95ba28efdd23c1a679ccac5a35b7a1ddb0fb551f5b08ecb3407cd7d03783cd1350fc9a476777a5edf6f22f425cccb04451ba5cfb5989f2cd3084267542701
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser