CONTINUOUS INTERNET TELEMETRY24H DRIFT3,080 material changesacross 2,832 domains · -318 vs yesterdayDNS DRIFT17 domains changed DNS providertop destination cloudflare.com · -10 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,323 curated domains not answering-6,395 vs yesterdayERRORS10,911 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,080 material changesacross 2,832 domains · -318 vs yesterdayDNS DRIFT17 domains changed DNS providertop destination cloudflare.com · -10 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,323 curated domains not answering-6,395 vs yesterdayERRORS10,911 responded with an errorlast probe · 5xx / 404 / 429 / 403

bundesregierung.de

Observed 2026-07-13T17:36:05.481Z (3h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesGoogle Search Console
5 subdomains · government_expanded
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat bundesregierung.de actually stands on - every host below is a signed observation
bundesregierung.de
A / AAAA
185.173.230.38185.173.231.38
Cloudflareserves the site
NS
d.babieldns.dec.babieldns.deb.babieldns.dea.babieldns.de
babieldns.deanswers its DNS
MX
mx1.bund.demx2.bund.de
bund.dereceives its email

HTTPS probe

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

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

DNS Records

A 2

  • 185.173.230.38
  • 185.173.231.38

MX 2

  • 10mx1.bund.de
  • 10mx2.bund.de

TXT 6

  • google-site-verification=mh3FEex8OWm7UvzF-hDaUzopzDUXhxhUBNobuWl1oPo
  • v=spf1 mx a include:_spf1.bund.de include:spf.init.de ip4:185.173.230.63/32 ip4:185.173.231.63/32 -all
  • _globalsign-domain-verification=xHSfIn-OfLZnmDuofXnVUvNaZQBRRABavb2Woaatu8
  • _telesec-domain-validation=314624_2023-01-17_G44CRqCuTjmqNyJbENsRuJr07zX4hOpH7LMrRWSAsEa5ANe8ir
  • v=DMARC1; p=reject; pct=100; sp=quarantine; rua=mailto:dmarc-reports@babiel.net; ruf=mailto:dmarc-reports@babiel.net; fo=1;
  • v=DNSSEC1; (detected)

NS 4

  • d.babieldns.de
  • c.babieldns.de
  • b.babieldns.de
  • a.babieldns.de

SOA 1

  • a.babieldns.de admin.babiel.com

TLS Certificates (0)

None.

Subdomains (5)

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 bundesregierung.de. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
2958fbc7-4c7a-4461-addd-5db968cb4b4f
Output Hash
ff205d2871a61be7b599b29ceedae5da0a555713f0195da9fa1e9617c38cf5c8
Signature
ed25519:08bca3ba8a90f0ccad7ffd31888fe1e3f570edbaf511a1d17aeff7b014a7a14c81db51def2ed6394e96b0409a08eb05170aca14011bb9edd3c3142d2fd9c480f
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser