CONTINUOUS INTERNET TELEMETRY24H DRIFT176 material changesacross 139 domains · -1,460 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination akam.net · -15 vs yesterdayNOW55,769 curated domains not answering+41,346 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT176 material changesacross 139 domains · -1,460 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination akam.net · -15 vs yesterdayNOW55,769 curated domains not answering+41,346 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

berlin.de

Observed 2026-07-15T11:06:46.483Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesGoogle Search Console
IPv6 · 8 subdomains · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat berlin.de actually stands on - every host below is a signed observation
berlin.de
A / AAAA
109.68.230.1452a00:13c8:f5::393:8a4d:2
Cloudflareserves the site
NS
ns-1460.awsdns-54.orgns-931.awsdns-52.netns-1719.awsdns-22.co.ukns-391.awsdns-48.com
awsdns-54.org + awsdns-52.net + moreanswers its DNS
MX
mailin.berlin.desecondary.snafu.de
berlin.de + snafu.dereceives its email

HTTPS probe

redirect Redirecting (3xx) 308 → https://www.berlin.de/
HTTP status308
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time192 ms
DNS resolutionNOERROR
Redirect chain
https://www.berlin.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

  • 109.68.230.145

AAAA 1

  • 2a00:13c8:f5::393:8a4d:2

MX 2

  • 10mailin.berlin.de
  • 50secondary.snafu.de

TXT 5

  • google-site-verification=tMQO2I0rVdhM-PmlH9jbp5sr8XzeZyAmnafwFKs2kgE
  • v=spf1 mx a:service.berlinonline.de ip6:2a01:4f8:c01f:e7::1 ip6:2a01:4f8:c01f:e7::2 ip6:2a01:4f8:c17:b1b6::1 ip6:2a01:4f8:c01f:e7::3 ip4:78.46.237.76 ip4:49.12.112.184 ip4:49.12.73.55 ip4:116.202.3.64 ip4:49.13.18.183 include:_spf1.berlin.de -all
  • kctmddpdsfra04p0iiqn0a2ct
  • abuseipdb-verification=LfrKgDpN
  • v=DMARC1; p=none; rua=mailto:dmarc_report@berlin.de

NS 4

  • ns-1460.awsdns-54.org
  • ns-931.awsdns-52.net
  • ns-1719.awsdns-22.co.uk
  • ns-391.awsdns-48.com

SOA 1

  • ns-931.awsdns-52.net awsdns-hostmaster.amazon.com

CAA 8

  • issue digicert.com
  • iodef mailto:webmaster@berlinonline.net
  • issue letsencrypt.org
  • issue comodoca.com
  • issue godaddy.com
  • issue telesec.de
  • issuewild letsencrypt.org
  • issue globalsign.com

TLS Certificates (0)

None.

Subdomains (8)

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

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

Ed25519 Receipt

Receipt ID
bd2cc7fb-76f9-4bc9-a5dd-2b9beaf5d5b6
Output Hash
31df3f69df029699c92053995d9726baad33a75b56efbfb9f7dc25048ef7f627
Signature
ed25519:c75991430a2920c4bce21c643606b693432d46821aceb8cc1925ac31cd321557a68340a5b1396bf359c2663c13d01b464d83ccfe12144d16fd73070dd7f00506
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser