CONTINUOUS INTERNET TELEMETRY24H DRIFT2,181 material changesacross 1,981 domains · +222 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT9 domains switched email providertop destination google.com · +6 vs yesterdayNOW3,476 curated domains not answeringlast probe, steadyERRORS8,528 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,334 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT2,181 material changesacross 1,981 domains · +222 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT9 domains switched email providertop destination google.com · +6 vs yesterdayNOW3,476 curated domains not answeringlast probe, steadyERRORS8,528 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,334 throttled or blocked our scanner429 rate-limit / 403 bot-block

regen.network

Observed 2026-07-15T08:27:59.760Z (9h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byGoogle Workspace
Registered withSquarespace Domains II LLC
Also usesHubSpot
5 subdomains · web3_defi
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat regen.network actually stands on - every host below is a signed observation
regen.network
A / AAAA
198.202.211.1
Cloudflareserves the site
NS
dns4.p03.nsone.netdns2.p03.nsone.netdns1.p03.nsone.netdns3.p03.nsone.net
nsone.netanswers its DNS
MX
alt1.aspmx.l.google.comalt4.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.com+1 more
Google Workspacereceives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.regen.network/
HTTP status301
Servercloudflare
TLS protocolHTTP/3
TLS issuernot observed
Behind Cloudflareyes
Response time251 ms
DNS resolutionNOERROR
Redirect chain
https://www.regen.network/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 198.202.211.1

MX 5

  • 5alt1.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 1aspmx.l.google.com

TXT 4

  • v=spf1 a mx include:_spf.mlsend.com include:45264802.spf04.hubspotemail.net include:amazonses.com include:_spf.mlsend.com include:_spf.google.com -all
  • 76798391-210d-47db-a5d1-58c3e83a4a9b=39debd4a3154331cc1d187880dbdcd5bcd458cd25bbd963bfc9b865795d59bc1
  • v=DMARC1; p=quarantine; rua=mailto:dmarc-notify@regen.network; adkim=r; aspf=r
  • v=DKIM1; (detected)

NS 4

  • dns4.p03.nsone.net
  • dns2.p03.nsone.net
  • dns1.p03.nsone.net
  • dns3.p03.nsone.net

SOA 1

  • dns1.p03.nsone.net domains+netlify.netlify.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 regen.network. It updates itself. It attests a signed observation - not that the site is safe.

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

Ed25519 Receipt

Receipt ID
ce850e4e-3a55-4a92-bd32-e42e5c09f650
Output Hash
ff730b7df544a042e3952aee2ea2ea3b30b5d1833fc089c678e80f28c1123837
Signature
ed25519:7574909d67072731b46246a4589a6d656e1fe174a61c28c8ad2fa38196445c1f8c355b0a9a87a2208e2cc01d394c2ab95f12176aa3e81193d53e782cc4ce6e0c
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser