kalender-365.de
Observed Aug 16, 2026, 14:09 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.
kalender-365.de is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting kalender-365.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 kalender-365.de Watching a domain needs a DRM3 account. The reading above stays free and public either way.Steady. No change on record for kalender-365.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.
DNS Records
A 1
92.205.208.77
AAAA 1
2a00:1169:103:1530::
MX 1
100mxlb.ispgateway.de
TXT 1
v=spf1 mx a include:ispgateway.de ~all
NS 2
ns81.domaincontrol.comns82.domaincontrol.com
SOA 1
ns81.domaincontrol.com dns.jomax.net
MCP_RECORDS 1
v=spf1 mx a include:ispgateway.de ~all
DMARC_RECORDS 1
v=spf1 mx a include:ispgateway.de ~all
BIMI_RECORDS 1
v=spf1 mx a include:ispgateway.de ~all
MTA_STS_RECORDS 1
v=spf1 mx a include:ispgateway.de ~all
TLS Certificates (3)
| Common Name | Issuer | Expires |
|---|---|---|
www.kalender-365.de |
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., 2.5.4.11=http://certs.starfieldtech.com/repository/, CN=Starfield Secure Certificate Authority - G2 | Mon, 18 Jan 2027 03:21:15 +0000 |
Starfield Secure Certificate Authority - G2 |
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2 | Sat, 03 May 2031 07:00:00 +0000 |
Starfield Root Certificate Authority - G2 |
C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Root Certificate Authority - G2 | Thu, 31 Dec 2037 23:59:59 +0000 |
Subdomains (1)
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
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 receiptEd25519 Receipt
- Receipt ID
rcpt_3f2ecdb9d6ba3d67- Output Hash
ed68d7cf32a89fae727b8ac0457d35ebf194a1a2eb229a81d0105e7bb2367642- Signature
ed25519:8d0651d105b7975b62e2984bcac9909bffbfcfb02a8a99ac0c40df92603b7a0fb6216530c2693dbf34069af5606b407eff92d51d9f0dffca7bf9ed902e27420b- Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9- Parent
(genesis)- Plane
- fast