CONTINUOUS INTERNET TELEMETRY24H DRIFT54,366 material changesacross 47,273 domains · last 24h · +19,960 vs yesterdayROTATION53 domains moved DNS from magpiedns.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hNOW608 curated domains not reachablelast probe, steadySITE ERRORS34,089 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,502 sites429 rate-limit / 403 bot-block, a posture signal

dpanel.pl

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

This reading of dpanel.pl was taken 7d ago

dpanel.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dpanel.pl 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 dpanel.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
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-09 06:21 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 dpanel.pl actually stands on - every host below is a signed observation
dpanel.pl
A / AAAA
77.79.196.186
unattributedserves the site
NS
arch.ns.cloudflare.comgeorgia.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mx-1.dpoczta.plwww1.dpanel.pl
dpoczta.pl + dpanel.plreceives its email
TLS
dpanel.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 77.79.196.186

MX 2

  • 10mx-1.dpoczta.pl
  • 10www1.dpanel.pl

TXT 1

  • 46.229.146.116

NS 2

  • arch.ns.cloudflare.com
  • georgia.ns.cloudflare.com

SOA 1

  • arch.ns.cloudflare.com dns.cloudflare.com

SRV 1

  • dpoczta.pl:443 p0

MCP_RECORDS 1

  • 46.229.146.116

DMARC_RECORDS 1

  • 46.229.146.116

BIMI_RECORDS 1

  • 46.229.146.116

MTA_STS_RECORDS 1

  • 46.229.146.116

TLS Certificates (3)

Common NameIssuerExpires
dpanel.pl C=US, O=Let's Encrypt, CN=YR1 Wed, 16 Sep 2026 08:45:27 +0000
YR1 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_47a3313e40b3ad18
Output Hash
b0b2e36ee8f0b65a22732fcd447409cc52a0646419ad5c711574ff5ac2046d17
Signature
ed25519:1d2baa384848d3d1932949f8e203dde501cd012af28496547508a416d66d0d2696598c1795df4d5f0cb6142524d000dd915c5d37da9bf8dabe322ebe06953c0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser