CONTINUOUS INTERNET TELEMETRY24H DRIFT1,810 material changesacross 1,618 domains · +388 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination yandexcloud.net · -19 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -4 vs yesterdayNOW1,106 curated domains not answering+396 vs yesterdayERRORS4,988 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED7,738 throttled or blocked our scanner429 rate-limit / 403 bot-blockMOVERtiktok.comDMARC enforcement downgraded: p=reject → no DMARC record24H DRIFT1,810 material changesacross 1,618 domains · +388 vs yesterdayDNS DRIFT2 domains changed DNS providertop destination yandexcloud.net · -19 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -4 vs yesterdayNOW1,106 curated domains not answering+396 vs yesterdayERRORS4,988 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED7,738 throttled or blocked our scanner429 rate-limit / 403 bot-blockMOVERtiktok.comDMARC enforcement downgraded: p=reject → no DMARC record

linkedin.cz

Observed 2026-07-18T02:11:23.307Z (7h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
IPv6 · 1 subdomain · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat linkedin.cz actually stands on - every host below is a signed observation
linkedin.cz
A / AAAA
108.174.10.242620:109:c002::6cae:a18
Cloudflareserves the site
NS
ns4-42.azure-dns.infons2-42.azure-dns.netns3-42.azure-dns.orgns1-42.azure-dns.com
azure-dns.info + azure-dns.net + moreanswers its DNS

HTTPS probe

redirect Redirecting (3xx) 301 → https://cz.linkedin.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time240 ms
DNS resolutionNOERROR
Redirect chain
https://cz.linkedin.com/
MCP This domain advertises an AI service endpoint at _mcp._tcp.
v=DKIM1; p= v=spf1 -all

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

DNS Records

A 1

  • 108.174.10.24

AAAA 1

  • 2620:109:c002::6cae:a18

MX 1

  • 0

TXT 7

  • v=spf1 -all
  • cjmxh13fjgycwhxsckyl4n2yvq129z16
  • qc6x16rykkmzj6spl29nrnlmv6918tbx
  • v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com
  • v=DKIM1; (detected)
  • v=spf1 -all
  • v=DKIM1; p=

NS 4

  • ns4-42.azure-dns.info
  • ns2-42.azure-dns.net
  • ns3-42.azure-dns.org
  • ns1-42.azure-dns.com

SOA 1

  • ns1-42.azure-dns.com azuredns-hostmaster.microsoft.com

CAA 1

  • contactemail caarecordaware@microsoft.com

TLS Certificates (0)

None.

Subdomains (1)

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

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

Ed25519 Receipt

Receipt ID
04b0b226-e22a-47e2-bde6-2104cdec705d
Output Hash
765974f4d57bfe36f24fb1d06d8ab5ad6e44b18e5d5892ceea6d20e1d59292ce
Signature
ed25519:0b8d9e413b7e564fc1a53115c9c39fbfdb641671dea3ecd2d2bd002bf264ec6fa590c07821621a9a25912e5e7512f4574ec7a12a363b65c9238108bfd993f50e
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser