CONTINUOUS INTERNET TELEMETRY24H DRIFT29,105 material changesacross 28,144 domains · 24h to ~12h ago · -8,917 vs yesterdayROTATION59 domains moved DNS from kirklanddc.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW556 curated domains not reachable+25 vs yesterdaySITE ERRORS33,755 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,583 sites429 rate-limit / 403 bot-block, a posture signal

roitapis.fr

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

This reading of roitapis.fr was taken 5d ago

roitapis.fr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting roitapis.fr 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 roitapis.fr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byLet's Encrypt
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 13:32 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 roitapis.fr actually stands on - every host below is a signed observation
roitapis.fr
A / AAAA
148.251.10.43
unattributedserves the site
NS
ns1.soy.esns2.soy.es
soy.esanswers its DNS
MX
mail.roitapis.fr
roitapis.frreceives its email
TLS
roitapis.fr
Let's Encryptissued its certificate

DNS Records

A 1

  • 148.251.10.43

MX 1

  • 10mail.roitapis.fr

TXT 1

  • v=spf1 mx mx:roitapis.fr ip4:116.202.192.156 ip4:148.251.10.43 ~all

NS 2

  • ns1.soy.es
  • ns2.soy.es

SOA 1

  • ns1.soy.es hostmaster.audioledcar.soy.es

MCP_RECORDS 1

  • v=spf1 mx mx:roitapis.fr ip4:116.202.192.156 ip4:148.251.10.43 ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • v=spf1 mx mx:roitapis.fr ip4:116.202.192.156 ip4:148.251.10.43 ~all

MTA_STS_RECORDS 1

  • v=spf1 mx mx:roitapis.fr ip4:116.202.192.156 ip4:148.251.10.43 ~all

TLS Certificates (3)

Common NameIssuerExpires
roitapis.fr C=US, O=Let's Encrypt, CN=YR2 Thu, 15 Oct 2026 01:32:55 +0000
YR2 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 (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_092f51e5da90082d
Output Hash
f925f8f452f745a4de3989e751ab2af32e5777c865d3c6592bab96628c0c7e67
Signature
ed25519:00d5146c174071201c925e9cfe4904996633af779e1af532ea3240f76da90422d675291b8a9b96cd16e68f21782b50173f1f200501720e74a604fd912304240e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser