linkedin.in

Observed Aug 10, 2026, 10:18 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of linkedin.in was taken 2d ago

linkedin.in is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting linkedin.in under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch linkedin.in Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Secured byDigiCert
IPv6 · 1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-11 12:55 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat linkedin.in actually stands on - every host below is a signed observation
linkedin.in
A / AAAA
108.174.10.242620:109:c002::6cae:a18
2620serves the site
NS
ns1-42.azure-dns.comns2-42.azure-dns.netns3-42.azure-dns.orgns4-42.azure-dns.info
azure-dns.com + azure-dns.net + moreanswers its DNS
MX
mail-c.linkedin.commail.linkedin.com
linkedin.comreceives its email
TLS
linkedin.at
DigiCert Incissued its certificate

DNS Records

A 1

  • 108.174.10.24

AAAA 1

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

MX 2

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

TXT 4

  • 5wt3yb9yk378c3k623qn87zrq459cz44
  • _i8acwcqnenmjs2pgrtguor1m8y3zsam
  • ll12ksx4bhvbpsh713ht0k150ldwttb9
  • v=spf1 -all

NS 4

  • 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 azuredns-hostmaster.microsoft.com

CAA 1

  • contactemail "caarecordaware@microsoft.com"

MCP_RECORDS 2

  • v=DKIM1; p=
  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:yfy3q-9359@rua.dmarc.emailanalyst.com; ruf=mailto:d@ruf.agari.com

BIMI_RECORDS 2

  • v=DKIM1; p=
  • v=spf1 -all

MTA_STS_RECORDS 2

  • v=DKIM1; p=
  • v=spf1 -all

TLS Certificates (2)

Common NameIssuerExpires
linkedin.at C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1 Sun, 20 Sep 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

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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_660b879c64a95d96
Output Hash
4470bafbfed1a82c4b44bd57d0db3944ad746d8f7c6111f54a08b039971e9f32
Signature
ed25519:be639719882dda97aa7593db28afc83cca35532a278f2088726d72e2bc132a6f87e3dc00a2508110501e3c7b84b4c68dfa52ba61de6fdc06546cdead1e2d8b0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT31,069 material changesacross 27,732 domains · 24h to ~45m ago · +19,271 vs yesterdayROTATION61 domains moved DNS from magpiedns.com to koaladns.com, 59 moved backa rotation loop, not a migration · 24hNOW520 curated domains not reachablelast probe, steadySITE ERRORS36,547 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,586 sites429 rate-limit / 403 bot-block, a posture signal