CONTINUOUS INTERNET TELEMETRY24H DRIFT51,574 material changesacross 48,279 domains · 24h to ~3h ago · -10,502 vs yesterdayROTATION52 domains moved DNS from magpiedns.com to koaladns.com, 52 moved backa rotation loop, not a migration · 24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,864 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 120,840 sites429 rate-limit / 403 bot-block, a posture signal

ductus.fr

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

This reading of ductus.fr was taken 4d ago

ductus.fr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting ductus.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 ductus.fr Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Secured byDigiCert
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 19:15 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 ductus.fr actually stands on - every host below is a signed observation
ductus.fr
A / AAAA
91.195.241.232
Cloudflareserves the site
TLS
ductus.fr
DigiCert Incissued its certificate

DNS Records

A 1

  • 91.195.241.232

TLS Certificates (2)

Common NameIssuerExpires
ductus.fr C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G2 Mon, 26 Oct 2026 23:59:59 +0000
Encryption Everywhere DV TLS CA - G2 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Sat, 27 Nov 2027 12:46:40 +0000

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_cb706dc54ba2f820
Output Hash
3fd343f080ef1a299bb93a1b28733df05767153a910a16e1faf7f2584b7ffb4e
Signature
ed25519:08f5e34d2e0e83371af9d25bf369b819c94b8623183e868ea4fba4297b6ef9eaf204a80351ba59159046bd069422eb3cfe8066449a9de3f77f1034f64625be03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser