CONTINUOUS INTERNET TELEMETRY24H DRIFT25,322 material changesacross 24,507 domains · 24h to ~14h ago · -12,700 vs yesterdayROTATION55 domains moved DNS from kirklanddc.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW563 curated domains not reachable+32 vs yesterdaySITE ERRORS33,717 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,858 sites429 rate-limit / 403 bot-block, a posture signal

linkup.com

Observed Aug 3, 2026, 08:59 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of linkup.com was taken 4d ago

linkup.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting linkup.com 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 linkup.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byMimecast
Secured byLet's Encrypt
Also usesGoogle Search ConsoleHubSpot
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 18:53 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 linkup.com actually stands on - every host below is a signed observation
linkup.com
A / AAAA
94.247.142.1
Cloudflareserves the site
NS
raina.ns.cloudflare.comvin.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
eu-smtp-inbound-1.mimecast.comeu-smtp-inbound-2.mimecast.com
Mimecastreceives its email
TLS
linkup.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 94.247.142.1

MX 2

  • 10eu-smtp-inbound-1.mimecast.com
  • 10eu-smtp-inbound-2.mimecast.com

TXT 12

  • 0ed1fe018a6b9d1fd927344be5951f0a6b538fb5eb
  • 6p59ocpj2jq9edf7319rdcqtvm
  • MS=444F543C147299AF8D84F5A21E35BD0E651F077F
  • MS=ms64158077
  • apple-domain-verification=mBkeV8rdlWVPURji
  • ce2786e2-fdae-4203-a014-f0ad237176e9
  • globalsign-domain-verification=4B927BA65EEFDE3D3967F1534FDD297A
  • globalsign-domain-verification=535cd633e4cd473e191024709983b887
  • globalsign-domain-verification=de665244645ba89017c40ea6bbb9ee6a
  • google-site-verification=-wlVNbVVIE6RhqnQoMiLOud91Pwkq74EO-6m2P3UNeY

NS 2

  • raina.ns.cloudflare.com
  • vin.ns.cloudflare.com

SOA 1

  • raina.ns.cloudflare.com dns.cloudflare.com

CAA 22

  • iodef "mailto:certs@linkup.com"
  • issue "amazon.com"
  • issue "amazonaws.com"
  • issue "amazontrust.com"
  • issue "awstrust.com"
  • issue "comodoca.com"
  • issue "digicert.com; cansignhttpexchanges=yes"
  • issue "globalsign.com"
  • issue "godaddy.com"
  • issue "letsencrypt.org"

MCP_RECORDS 2

  • globalsign-domain-verification=535cd633e4cd473e191024709983b887
  • globalsign-domain-verification=de665244645ba89017c40ea6bbb9ee6a

DMARC_RECORDS 1

  • v=DMARC1;p=reject;rua=mailto:19623206fa@rua.easydmarc.us;ruf=mailto:19623206fa@ruf.easydmarc.us;fo=1;

BIMI_RECORDS 2

  • globalsign-domain-verification=535cd633e4cd473e191024709983b887
  • globalsign-domain-verification=de665244645ba89017c40ea6bbb9ee6a

MTA_STS_RECORDS 2

  • globalsign-domain-verification=535cd633e4cd473e191024709983b887
  • globalsign-domain-verification=de665244645ba89017c40ea6bbb9ee6a

TLS Certificates (4)

Common NameIssuerExpires
linkup.com C=US, O=Let's Encrypt, CN=YE1 Tue, 15 Sep 2026 23:13:59 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

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_0fc6cfc31692a8bd
Output Hash
8fd04067610b770c2de210159e0bc4f38ea7f2451739d3075c05a4e7d899dab7
Signature
ed25519:cbb58d5b423dbae31e7bd0f8e96255ed9444ef4e9144ed4c6f9c02cfc525b2b7802ecb57af709c239bb1e5bce78e316d983eca02051b7488c555a5ec5ed0970b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser