CONTINUOUS INTERNET TELEMETRY24H DRIFT1,913 material changesacross 1,726 domains · -165 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination alidns.com · +1 vs yesterdayEMAIL DRIFT8 domains switched email providertop destination google.comCERT DRIFT46 domains switched issuing CA24hNOW1,976 curated domains not answering+850 vs yesterdayERRORS14,073 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED37,194 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT1,913 material changesacross 1,726 domains · -165 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination alidns.com · +1 vs yesterdayEMAIL DRIFT8 domains switched email providertop destination google.comCERT DRIFT46 domains switched issuing CA24hNOW1,976 curated domains not answering+850 vs yesterdayERRORS14,073 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED37,194 throttled or blocked our scanner429 rate-limit / 403 bot-block

leevalley.com

Observed Jul 19, 2026, 06:46 UTC (3h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesFacebook/MetaGoogle Search Console
9 subdomains · tranco_100k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat leevalley.com actually stands on - every host below is a signed observation
leevalley.com
A / AAAA
76.76.21.21
Cloudflareserves the site
NS
ns1-03.azure-dns.comns3-03.azure-dns.orgns2-03.azure-dns.netns4-03.azure-dns.info
azure-dns.com + azure-dns.org + moreanswers its DNS
MX
lvmail2.leevalley.comlvmail1.leevalley.com
leevalley.comreceives its email

HTTPS probe

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

  • 76.76.21.21

MX 2

  • 20lvmail2.leevalley.com
  • 10lvmail1.leevalley.com

TXT 8

  • openai-domain-verification=dv-ZKNpGpI9yRjUbv0KF6kPEPs2
  • amazonses:8No9DXtc9JBjSAt2A5MHH817Ixpp5B3C4c3TpQp0fAQ=
  • MS=ms23190269
  • facebook-domain-verification=isd05kf8d86mlnnn7g48ohv12li6lb
  • anthropic-domain-verification-1cfndp=PcP0EVpaNoSnvao0KeshQ0tzc
  • v=spf1 a ip4:207.35.224.150/32 ip4:207.164.225.16/32 include:spf.protection.outlook.com -all
  • google-site-verification=2v_KUs8TkVxN0w36GP0X5CBwQ4rEmOczaTAvSPVXgWw
  • v=DMARC1; p=quarantine; fo=0; rua=mailto:pgweb@leevalley.com; ruf=mailto:pgweb@leevalley.com

NS 4

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

SOA 1

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

CAA 1

  • issue digicert.com

TLS Certificates (0)

None.

Subdomains (9)

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

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

Ed25519 Receipt

Receipt ID
988f0b6e-8c6d-4bac-b905-908e9c25da74
Output Hash
85cc22c6d6f7802a635413fc9f9dfa993f4018c0a89b3b5f031934cfec9137c1
Signature
ed25519:f5b887c6824162fd15d65257adcaa3a0868f8bd61c877dd0e04bbbf840ecd42cc8e5f12137122f30a13d853567a1f1bd29e4cee5c1364b3e639d66cc744f5109
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser