CONTINUOUS INTERNET TELEMETRY24H DRIFT2,366 material changesacross 2,133 domains · -1,032 vs yesterdayDNS DRIFT15 domains changed DNS providertop destination cloudflare.com · -12 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,324 curated domains not answering-6,394 vs yesterdayERRORS10,911 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,366 material changesacross 2,133 domains · -1,032 vs yesterdayDNS DRIFT15 domains changed DNS providertop destination cloudflare.com · -12 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,324 curated domains not answering-6,394 vs yesterdayERRORS10,911 responded with an errorlast probe · 5xx / 404 / 429 / 403

linkedin.com.br

Observed 2026-07-13T00:28:22.307998346+00:00 (21h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Secured byDigiCert
Registered withDOMAIN-PROTECTION
IPv6 · 1 subdomain · push_legacy
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat linkedin.com.br actually stands on - every host below is a signed observation
linkedin.com.br
A / AAAA
130.211.32.142600:1901:0:d5ad::
Cloudflareserves the site
NS
dns1.p09.nsone.netdns2.p09.nsone.netdns3.p09.nsone.netdns4.p09.nsone.net+4 more
nsone.net + azure-dns.com + moreanswers its DNS
MX
mail.linkedin.commail-c.linkedin.com
linkedin.comreceives its email
TLS
linkedin.com.br
DigiCert Incissued its certificate

DNS Records

A 1

  • 130.211.32.14

AAAA 1

  • 2600:1901:0:d5ad::

MX 2

  • 10mail.linkedin.com
  • 10mail-c.linkedin.com

TXT 9

  • _tsgahuwh8sqco9dxizlyzqhpnp60b0f
  • v=spf1 -all
  • 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; p=
  • v=spf1 -all
  • v=DKIM1; p=
  • v=spf1 -all
  • v=DKIM1; p=
  • v=spf1 -all

NS 8

  • dns1.p09.nsone.net
  • dns2.p09.nsone.net
  • dns3.p09.nsone.net
  • dns4.p09.nsone.net
  • ns1-42.azure-dns.com
  • ns2-42.azure-dns.net
  • ns3-42.azure-dns.org
  • ns4-42.azure-dns.info

SOA 1

  • ns1-42.azure-dns.com hostmaster.linkedin.com

CAA 1

  • contactemail "caarecordaware@microsoft.com"

TLS Certificates (3)

Common NameIssuerExpires
linkedin.com.br C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1 Sat, 28 Nov 2026 23:59:59 +0000
DigiCert Global G2 TLS RSA SHA256 2020 CA1 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Sat, 29 Mar 2031 23:59:59 +0000
DigiCert Global Root G2 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Fri, 15 Jan 2038 12:00:00 +0000

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

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

Ed25519 Receipt

Receipt ID
0dd3bd45-ddd0-485a-b0ab-300a1be139e0
Output Hash
b1413da334571882b7c7b411f34fff7257477084afa6374632d08b1761618017
Signature
ed25519:460ed7031290e74d7ba701c1e60fbea79b6682f4c7a828ac65fdd539e7ad7dbfb7d7747697ba88519856eb92502c36480c84d1ed4c18ea4e5dfd95cb5db2720d
Public Key
ed25519:178c3bd0f57d9d64b83cc4630753381e1a465005a2bbba3d032371f24af0bfd8
Parent
(genesis)
Plane
fast
Verify this in your browser