CONTINUOUS INTERNET TELEMETRY24H DRIFT3,246 material changesacross 2,824 domains · -152 vs yesterdayDNS DRIFT22 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -5 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,962 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,246 material changesacross 2,824 domains · -152 vs yesterdayDNS DRIFT22 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -5 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,962 responded with an errorlast probe · 5xx / 404 / 429 / 403

heidelberg.com

Observed 2026-07-12T16:32:39.245Z (15h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesDocuSignGoogle Search ConsoleAtlassianMiro
9 subdomains · manufacturing
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat heidelberg.com actually stands on - every host below is a signed observation
heidelberg.com
A / AAAA
5.44.96.79
Cloudflareserves the site
NS
ns1.heidelberg.comns2.heidelberg.com
heidelberg.comanswers its DNS
MX
heidelberg-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

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

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

DNS Records

A 1

  • 5.44.96.79

MX 1

  • 5heidelberg-com.mail.protection.outlook.com

TXT 21

  • brevo-code:a4e2850914c69e1c7dfb295d08c702c1
  • docusign=cfbe89a7-4c68-4d04-962b-61b853ab7cf7
  • bw=cbzmWRHeDVDoMvCb6WvZ19z2jYfKpC3x7GQZdtwrC29K
  • pardot991622=d01dab3ad53e88957202c915d49ffe9fb20a04c6f5e61eab71d3c3dec242ae64
  • 6aFDF11x200II79Isx4LLtjBULhrsfen5vnk4h9B1DJC1biMaxVx+4iAI27KjOQGA3rGJgR/30H9OOBgUzG7Ww==
  • pardot973933=18b9619800eb86b55b895fda2d75a1acd791f0efbf9ec073f00be731d7b1fc59
  • teamviewer-sso-verification=03da593653d74fe29b61c44a5edae2b6
  • apple-domain-verification=PytmDtgCcIt7q4Lq
  • bw=rFqV9F3wzHzIH17mSZBSsyJ4h1hMVg3dn0vWmreQsh6g
  • mongodb-site-verification=G5wV4LrloeRk5yT0WJtQ0tbXlW1koXuC

NS 2

  • ns1.heidelberg.com
  • ns2.heidelberg.com

SOA 1

  • ns1.heidelberg.com dnsadmin.heidelberg.com

TLS Certificates (0)

None.

Subdomains (9)

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

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

Ed25519 Receipt

Receipt ID
cb6647b0-59b6-42de-9dc4-e5d29460d342
Output Hash
940743694be16329375eb3d1bf35dc2fdab3deb6bf4165afc38002c85ad77a64
Signature
ed25519:4aa033c70236a49e5bb7f0fed3bff77dc783b260fa0bf9fbd65ac1b404ed7fb49f893de919650869db8403606df0309ef0f5d94419149145b0673ce962141d0a
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser