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

lareinepcc.com

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

This reading of lareinepcc.com was taken 5d ago

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

DNS Records

A 1

  • 183.111.183.118

MX 1

  • 10mw-002.cafe24.com

TXT 1

  • v=spf1 ip4:183.111.183.118 ~all

NS 4

  • ns2.cafe24.co.kr
  • ns2.cafe24.com
  • ns1.cafe24.com
  • ns1.cafe24.co.kr

SOA 1

  • lareinepcc.com postmaster.lareinepcc.com

MCP_RECORDS 1

  • v=spf1 ip4:183.111.183.118 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:183.111.183.118 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:183.111.183.118 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:183.111.183.118 ~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_b9479b22e565b39f
Output Hash
df8b241ffe51873bd50bb5d39bfa7e1eb6b955d65a91059a0dd34f2f0cdd6652
Signature
ed25519:f0b039f7afac71e325ef9a2b4cb277455d36d3898b64fd58185c706ee3057840ccc1f4fdeb7ee75ce57272a294576f0f507a89be1ab6a0c81d8249935c205d04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser