CONTINUOUS INTERNET TELEMETRY24H DRIFT48,209 material changesacross 44,537 domains · 24h to ~75m ago · +13,592 vs yesterdaySHIFT65 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,882 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 144,834 sites429 rate-limit / 403 bot-block, a posture signal

varioterm.pl

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

This reading of varioterm.pl was taken 10d ago

varioterm.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting varioterm.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 varioterm.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byhome.pl S.A.
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 00:51 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 varioterm.pl actually stands on - every host below is a signed observation
varioterm.pl
A / AAAA
89.161.189.194
unattributedserves the site
NS
dns.home.pldns2.home.pldns3.home.pl
home.planswers its DNS
MX
varioterm.pl
varioterm.plreceives its email
TLS
varioterm.pl
home.pl S.A.issued its certificate

DNS Records

A 1

  • 89.161.189.194

MX 1

  • 10varioterm.pl

TXT 5

  • v=spf1 a mx ~all
  • v=DMARC1; p=none; rua=mailto:dmarc@varioterm.pl; ruf=mailto:dmarc@varioterm.pl;
  • v=spf1 a mx ~all
  • v=spf1 a mx ~all
  • v=spf1 a mx ~all

NS 3

  • dns.home.pl
  • dns2.home.pl
  • dns3.home.pl

SOA 1

  • dns.home.pl admin.home.pl

TLS Certificates (4)

Common NameIssuerExpires
varioterm.pl C=PL, O=home.pl S.A., CN=home pl DV TLS G2 R35 CA Wed, 03 Feb 2027 23:23:23 +0000
home pl DV TLS G2 R35 CA C=PL, O=Asseco Data Systems S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Root CA Wed, 16 May 2035 07:45:35 +0000
Certum Trusted Root CA C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA Tue, 19 Sep 2028 10:00:00 +0000
Certum Trusted Network CA C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA Mon, 31 Dec 2029 12:07:37 +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_f85cf112fbe380ff
Output Hash
ec9459fcf5a96cf0f92e7202347f7a28ffe6b422458f3177ce4ad7c39489ea19
Signature
ed25519:d23f230fffa4c687e7d4ac5b56d38fe1f120a0865a3fda789ce853f86d3de89d588e29d451707b1773969f66e0bb865b7fc32fc39bf63b7886317e5cb45e7a0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser