CONTINUOUS INTERNET TELEMETRY24H DRIFT1,886 material changesacross 1,715 domains · -73 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW8,879 curated domains not answering+5,450 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT1,886 material changesacross 1,715 domains · -73 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW8,879 curated domains not answering+5,450 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

lrz.de

Observed 2026-07-14T17:17:10.640Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesGoogle Search ConsoleZoom
IPv6 · 68 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat lrz.de actually stands on - every host below is a signed observation
lrz.de
A / AAAA
129.187.254.92001:4ca0:0:103::81bb:fe09
Cloudflareserves the site
NS
dns2.lrz.bayerndns3.lrz.eudns1.lrz.de
lrz.bayern + lrz.eu + moreanswers its DNS
MX
postrelay2.lrz.depostrelay1.lrz.de
lrz.dereceives its email

HTTPS probe

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

  • 129.187.254.9

AAAA 1

  • 2001:4ca0:0:103::81bb:fe09

MX 2

  • 100postrelay2.lrz.de
  • 100postrelay1.lrz.de

TXT 12

  • _telesec-domain-validation=342343_2025-04-09_4aBfZM59EiUBoZY1FjeG3bJESJjEvz5eiOMjYtWUtSTrgaSlHZ
  • HARICA-BLoBBL4RVjxhtBKZMhQ
  • adobe-idp-site-verification=e3cfd187f14222c3543809079d97034193253e92972ebb1319112d45522073e1
  • apple-domain-verification=pv7vIHO8HI7wOb3h
  • google-site-verification=aery99S4-qQNyQyHH2_P3UlwnXrfYgKa-BHwwKDRY1w
  • MS=DE0B9CA4BB75DB02492F692CCC82F76F708512A5
  • ZOOM_verify_U19bXiZbRpCHdlwiBU647w
  • sophos-domain-verification=1a4fcd30b32aa8612b04abdf18154cb0b3a2b246a0edbe98bcda3599f1ed9ce6
  • v=spf1 redirect=_spf.mail.lrz.de
  • _telesec-domain-validation=354726_2026-02-04_zSJyIi4tWMe32yF3pXU7ayGx6LVKJsLshMrwtAylL7IlSqQvWI

NS 3

  • dns2.lrz.bayern
  • dns3.lrz.eu
  • dns1.lrz.de

SOA 1

  • dns1.lrz.de hostmaster.lrz.de

CAA 4

  • issue harica.gr
  • issue telesec.de
  • issue pki.dfn.de
  • issue sectigo.com

TLS Certificates (0)

None.

Subdomains (68)

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

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

Ed25519 Receipt

Receipt ID
3e0a45f7-cc51-4196-87b5-22bff22bd623
Output Hash
54b7a58d93978a69ec0077dd28419d5bb2e06d20fbedd15cf374c6c2c73c80b4
Signature
ed25519:8cce5382f3f3660464c189a51492adc352c1e8424854bc5f932455ce4f5863bedd635967d3a9a4e28aa3537301e59027179567730970e3cfe67461c42711fe00
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser