CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 24,136 material changesacross 23,195+ domains · 24h to ~12h ago · a floor, 12h of 24 walkedROTATION48 domains moved DNS from koaladns.com to kirklanddc.com, 46 moved backa rotation loop, not a migration · 24hNOW592 curated domains not reachablelast probe, steadySITE ERRORS33,533 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,513 sites429 rate-limit / 403 bot-block, a posture signal

lawfirmidea.com

Observed Aug 2, 2026, 18:45 UTC (5d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of lawfirmidea.com was taken 5d ago

lawfirmidea.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lawfirmidea.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 lawfirmidea.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 19:19 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 lawfirmidea.com actually stands on - every host below is a signed observation
lawfirmidea.com
A / AAAA
203.245.24.18
unattributedserves the site
NS
ns.lawfirmidea.comns3.lawfirmidea.comns2.lawfirmidea.comns1.lawfirmidea.com
lawfirmidea.comanswers its DNS
MX
rmw-002.fmcity.com
fmcity.comreceives its email

DNS Records

A 1

  • 203.245.24.18

MX 1

  • 10rmw-002.fmcity.com

TXT 1

  • v=spf1 ip4:211.34.104.37 ~all

NS 4

  • ns.lawfirmidea.com
  • ns3.lawfirmidea.com
  • ns2.lawfirmidea.com
  • ns1.lawfirmidea.com

SOA 1

  • lawfirmidea.com postmaster.lawfirmidea.com

MCP_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:211.34.104.37 ~all

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