CONTINUOUS INTERNET TELEMETRY24H DRIFT3,199 material changesacross 2,780 domains · -199 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -3 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,312 curated domains not answering-6,406 vs yesterdayERRORS10,960 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,199 material changesacross 2,780 domains · -199 vs yesterdayDNS DRIFT24 domains changed DNS providertop destination digicertdns.com + digicertdns.net · -3 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination 365cool.com · -1 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,312 curated domains not answering-6,406 vs yesterdayERRORS10,960 responded with an errorlast probe · 5xx / 404 / 429 / 403

lynx.com

Observed 2026-07-12T18:55:26.077Z (11h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesAtlassianHubSpot
5 subdomains · hospitality
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat lynx.com actually stands on - every host below is a signed observation
lynx.com
A / AAAA
199.60.103.22
Cloudflareserves the site
NS
ns2-06.azure-dns.netns3-06.azure-dns.orgns1-06.azure-dns.comns4-06.azure-dns.info
azure-dns.net + azure-dns.org + moreanswers its DNS
MX
lynx-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.lynx.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/3
TLS issuernot observed
Behind Cloudflareyes
Response time245 ms
DNS resolutionNOERROR
Redirect chain
https://www.lynx.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

  • 199.60.103.22

MX 1

  • 10lynx-com.mail.protection.outlook.com

TXT 11

  • openai-domain-verification=dv-bdhEjJGDdFHmYfAUSebcsO65
  • cursor-domain-verification-80bzvx=JXYyqTBFoZn6Ejmi5gAjqkh49
  • anthropic-domain-verification-xx6st9=irShK3adaaf4CAxjeAXFyPFD9
  • atlassian-domain-verification=plIrDflSd2K8SncJ6Qn8OtexdxmEVJRIXjkosDNx5utgTwIweJb4XxkvTC1naILM
  • 67oqfm7lpsuses37vka22dcqjp
  • fr5oh22h6c98imdptnl61sfih
  • v=spf1 include:spf.protection.outlook.com include:_spf.atlassian.net include:4385221.spf01.hubspotemail.net include:_spf.salesforce.com include:spf.knowbe4.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
  • 9eqov4dkufo42q6g2qotv1fc5t
  • atlassian-sending-domain-verification=4137d03a-8fc5-41f5-8b9c-952afb5af5f9
  • _nn8el0pmjuyi279xdcykq6isett8szh

NS 4

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

SOA 1

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

TLS Certificates (0)

None.

Subdomains (5)

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

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

Ed25519 Receipt

Receipt ID
f0419a9f-f332-4fae-aa64-2d0c8f2ab1f8
Output Hash
2e30fe915e4da77460e99696994088e625289d81e2dc5d20795a13d7f283dbe6
Signature
ed25519:54840f4f82dfa7381484ac328eb583de60a4fbd9837e8cb05a00c3670fc8fb2a8093ee0cc17269ddfc23571ec60e3190ed92e0249f696dc0c0d7a04808842801
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser