CONTINUOUS INTERNET TELEMETRY24H DRIFT2,861 material changesacross 2,519 domains · -537 vs yesterdayDNS DRIFT21 domains changed DNS providertop destination cloudflare.com · -6 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination reyrey.com · -2 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,307 curated domains not answering-6,411 vs yesterdayERRORS10,966 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,861 material changesacross 2,519 domains · -537 vs yesterdayDNS DRIFT21 domains changed DNS providertop destination cloudflare.com · -6 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination reyrey.com · -2 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,307 curated domains not answering-6,411 vs yesterdayERRORS10,966 responded with an errorlast probe · 5xx / 404 / 429 / 403

checkdomain.de

Observed 2026-07-13T01:41:26.513Z (8h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byZendesk
Also usesZoomDockerSlackAtlassianGoogle Search Console
14 subdomains · tranco_20k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat checkdomain.de actually stands on - every host below is a signed observation
checkdomain.de
A / AAAA
31.47.251.5
Cloudflareserves the site
NS
ns.checkdomain.dens2.checkdomain.de
checkdomain.deanswers its DNS
MX
m1.checkdomain.dem2.checkdomain.de
Zendeskreceives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.checkdomain.de/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time898 ms
DNS resolutionNOERROR
Redirect chain
https://www.checkdomain.de/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 31.47.251.5

MX 2

  • 10m1.checkdomain.de
  • 20m2.checkdomain.de

TXT 14

  • teamviewer-sso-verification=2b4fee964a8c4e6996c85993bdfceea3
  • ZOOM_verify_swigHX81TKO6Lpvl3mzY_Q
  • v=spf1 include:_spf.cio.g1i.one include:mx.spf.checkdomain.de include:web1.spf.checkdomain.de include:spf.protection.outlook.com include:secure-mailgate.com include:mail.zendesk.com ip4:212.123.41.224/28 ip6:2a01:4f8:221:11cd:9734:4c26:6044:5f33 include:_spf.hostedemail.com ~all
  • pandadoc-domain-verification=be4pxxLjnr7zjZP8CGnMxe
  • apple-domain-verification=axE5Zek5oqkQpmY1
  • docker-verification=672e8e8e-3881-4f08-abdf-9b53d432afed
  • slack-domain-verification=0HwLoCeQR6NKLoHLzYRHNapepuf2S14afrziBMYN
  • atlassian-domain-verification=KKeihQSanTHe0l1pqlAF48oghg9rSqxhRZakMd/Gq8e8xTF/maaW2agw60HZU5va
  • google-site-verification=I0k-91zTnc8en6LAb7lt91WCg7rBlINQFic7CuplaP4
  • Sendinblue-code:ed3757f69b55cef27022dda6ad660908

NS 2

  • ns.checkdomain.de
  • ns2.checkdomain.de

SOA 1

  • ns.checkdomain.de hostmaster.checkdomain.de

TLS Certificates (0)

None.

Subdomains (14)

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; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for checkdomain.de. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for checkdomain.de <a href="https://domaindrift.io/t/checkdomain.de"> <img src="https://domaindrift.io/badge/checkdomain.de.svg" width="300" height="64" alt="DomainDrift signed observations for checkdomain.de"> </a>

Ed25519 Receipt

Receipt ID
c94523ba-0bf4-4e75-99c1-a67c3f3b20b6
Output Hash
3969f2117dad386c24df767c04dbf9b506a1b5ed9339e665310afdd23dcbb21c
Signature
ed25519:7fd38dd295823d74f6fe2149541a67ef1da5de974db5e4fe1ad2f8080964ddaa77096e50af010c0edb4cab6e398f245ab4557798610f86bd1801e4958ab8ca0b
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser