CONTINUOUS INTERNET TELEMETRY24H DRIFT24,136 material changesacross 23,195 domains · 24h to ~4h ago · -13,886 vs yesterdayROTATION54 domains moved DNS from kirklanddc.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hNOW669 curated domains not reachable+138 vs yesterdaySITE ERRORS33,571 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,494 sites429 rate-limit / 403 bot-block, a posture signal

limbuscompany.com

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

This reading of limbuscompany.com was taken 5d ago

limbuscompany.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting limbuscompany.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 limbuscompany.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoogle Trust Services
1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 21:53 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 limbuscompany.com actually stands on - every host below is a signed observation
limbuscompany.com
A / AAAA
192.0.78.232192.0.78.165
unattributedserves the site
NS
ns3.wordpress.comns1.wordpress.comns2.wordpress.com
wordpress.comanswers its DNS
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.232
  • 192.0.78.165

TXT 1

  • v=spf1 include:_spf.wpcloud.com ~all

NS 3

  • ns3.wordpress.com
  • ns1.wordpress.com
  • ns2.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Wed, 21 Oct 2026 03:48:00 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (1)

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_bf1e71a3e6082788
Output Hash
283f02b735bfc60e6ee9ca0d224a335c5e4f781006903092569bf56d4d39b0f8
Signature
ed25519:e037f9e378362284335915d9c10772b744ce1e2f710877bc61ef13374b4aa6f3bac2fd10d1651749e61d08efd8e35db0f00978e859a16515fae25116d57d1f0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser