rz089status.de

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

This reading of rz089status.de was taken 6d ago

rz089status.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting rz089status.de 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 rz089status.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for rz089status.de in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

INFRASTRUCTURE MAPwhat rz089status.de actually stands on - every host below is a signed observation
rz089status.de
A / AAAA
185.115.26.28
unattributedserves the site
NS
ns69.domaincontrol.comns70.domaincontrol.com
domaincontrol.comanswers its DNS
TLS
rz089status.de
Let's Encryptissued its certificate

DNS Records

A 1

  • 185.115.26.28

TXT 1

  • v=spf1 -all

NS 2

  • ns69.domaincontrol.com
  • ns70.domaincontrol.com

SOA 1

  • ns69.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:postmaster@h-m.net

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
rz089status.de C=US, O=Let's Encrypt, CN=YE2 Tue, 06 Oct 2026 12:08:49 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-17 00:13 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works

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_89646350046e56e5
Output Hash
8edbbc51b9f5529205d3bbf89a4917ea23171fa6b8ee4194409fd310fb6d12a4
Signature
ed25519:4c1657e3affc53c33401fc2c8d7d7293f0d26a4765c9f0f5c50e9f84f86a781e73cd79d53920297ac186e35006ae780cb9aa82fb928d764f74587c557250840a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT43,310 material changesacross 41,332 domains · 24h to ~75m ago · +4,070 vs yesterdayDNS DRIFT92 domains changed DNS providertop destination magpiedns.com · +5 vs yesterdayEMAIL DRIFT7 domains switched email provider24hNOW506 curated domains not reachable-85 vs yesterdaySITE ERRORS33,753 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,797 sites429 rate-limit / 403 bot-block, a posture signal