CONTINUOUS INTERNET TELEMETRY24H DRIFT3,091 material changesacross 2,775 domains · -307 vs yesterdayDNS DRIFT23 domains changed DNS providertop destination cloudflare.com · -4 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,310 curated domains not answering-6,408 vs yesterdayERRORS10,957 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT3,091 material changesacross 2,775 domains · -307 vs yesterdayDNS DRIFT23 domains changed DNS providertop destination cloudflare.com · -4 vs yesterdayEMAIL DRIFT3 domains switched email providertop destination h-email.net · -3 vs yesterdayCERT DRIFT8 domains switched issuing CA24h · +1 vs yesterdayNOW3,310 curated domains not answering-6,408 vs yesterdayERRORS10,957 responded with an errorlast probe · 5xx / 404 / 429 / 403

prolocation.net

Observed 2026-07-12T13:41:31.449Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Registered withRealtime Register B.V.
IPv6 · 20 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat prolocation.net actually stands on - every host below is a signed observation
prolocation.net
A / AAAA
94.228.131.802a00:d00:ff:131:94:228:131:80
Cloudflareserves the site
NS
cloudns8.prolocation.netns1.as41887.nlcloudns3.prolocation.netcloudns7.prolocation.net+2 more
prolocation.net + as41887.nl + moreanswers its DNS
MX
vmx01.prolocation.nlvmx02.prolocation.nlvmx03.prolocation.net
prolocation.nl + prolocation.netreceives its email

HTTPS probe

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

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

DNS Records

A 1

  • 94.228.131.80

AAAA 1

  • 2a00:d00:ff:131:94:228:131:80

MX 3

  • 10vmx01.prolocation.nl
  • 10vmx02.prolocation.nl
  • 10vmx03.prolocation.net

TXT 5

  • v=spf1 ip4:94.228.128.0/20 ip4:178.22.80.0/22 ip6:2a00:d00:ff:133::/64 ip6:2a00:d00:ff:129::/64 ip6:2a00:d00:ff:142::/64 ip6:2a00:d01:ff:905::/64 ip6:2001:610:188:140::/64 a mx -all
  • MS=7B72A3BA1BAB9628E40D365CD43985210A89AB1B
  • v=DMARC1; p=reject; rua=mailto:dmarcreports@prolocation.net; ruf=mailto:dmarcreports@prolocation.net; fo=1;
  • v=STSv1; id=20260619T151600;
  • v=DNSSEC1; (detected)

NS 6

  • cloudns8.prolocation.net
  • ns1.as41887.nl
  • cloudns3.prolocation.net
  • cloudns7.prolocation.net
  • cloudns4.prolocation.net
  • ns3.as41887.io

SOA 1

  • ns1.as41887.nl beheer.prolocation.net

CAA 1

  • issue sectigo.com

TLS Certificates (0)

None.

Subdomains (20)

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

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

Ed25519 Receipt

Receipt ID
f5775b44-9305-410a-b96c-66f817759516
Output Hash
31d93c2552590d466d6423186d8416ca0b0e71a8f9ca31b9d05d5c4dc3e9e5dd
Signature
ed25519:d6d7bd497d86e1c843501294b2c4896499e2b8dfff0afca8d17c828125893996e420bf559bd3fee1df756a4ebe73bc547151e5eb30e93268b42d3a7681a9980e
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser