CONTINUOUS INTERNET TELEMETRY24H DRIFT2,542 material changesacross 2,314 domains · -9 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT5 domains switched email providertop destination google.comCERT DRIFT4 domains switched issuing CA24h · -1 vs yesterdayNOW3,331 curated domains not answeringlast probe, steadyERRORS10,917 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,542 material changesacross 2,314 domains · -9 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT5 domains switched email providertop destination google.comCERT DRIFT4 domains switched issuing CA24h · -1 vs yesterdayNOW3,331 curated domains not answeringlast probe, steadyERRORS10,917 responded with an errorlast probe · 5xx / 404 / 429 / 403

jpberlin.de

Observed 2026-07-13T11:35:33.267Z (13h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesGoogle Search Console
11 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat jpberlin.de actually stands on - every host below is a signed observation
jpberlin.de
A / AAAA
185.97.174.97
Cloudflareserves the site
NS
ns.jpberlin.dedns4.cloudns.netdns7.cloudns.netns2.jpberlin.de+1 more
jpberlin.de + cloudns.netanswers its DNS
MX
mx2.jpberlin.demx-n.jpberlin.demx3.jpberlin.demx1.jpberlin.de
jpberlin.dereceives its email

HTTPS probe

ok Responding normally (2xx) 200 OK
HTTP status200
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1553 ms
DNS resolutionNOERROR

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

DNS Records

A 1

  • 185.97.174.97

MX 4

  • 10mx2.jpberlin.de
  • 50mx-n.jpberlin.de
  • 20mx3.jpberlin.de
  • 10mx1.jpberlin.de

TXT 5

  • v=spf1 mx include:_spf.jpberlin.de ~all
  • google-site-verification=rKtyr1-BDhpns_b3f5CHCYam9sRahVCNUenzY-XMwmc
  • have-i-been-pwned-verification=5363f14ab484eda7d5bb6ddcdadb0295
  • v=DMARC1; p=none; sp=none; adkim=r; aspf=r; pct=100; rua=mailto:abuse+arf@heinlein-support.de; rf=afrf; fo=1;
  • v=DNSSEC1; (detected)

NS 5

  • ns.jpberlin.de
  • dns4.cloudns.net
  • dns7.cloudns.net
  • ns2.jpberlin.de
  • ns3.jpberlin.de

SOA 1

  • ns.jpberlin.de root.jpberlin.de

CAA 4

  • issue digicert.com
  • iodef mailto:mail@heinlein-support.de
  • iodef mailto:security@heinlein-support.de
  • issue letsencrypt.org

TLS Certificates (0)

None.

Subdomains (11)

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

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

Ed25519 Receipt

Receipt ID
bcb09b02-eac7-4c7e-9a03-b87476d04e84
Output Hash
e1ce163777c7c15b584c3024209f552ea703796dde643a0f11c001729906185d
Signature
ed25519:d16a820caef7c318e0cfb636eb89b31f096f6ff0d7a4b00879a2b7030868a52b2a24be1db1795d12913fe9c05bf223ebf60d9f28870af4c7a5ad0bc063835405
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser