CONTINUOUS INTERNET TELEMETRY24H DRIFT2,522 material changesacross 2,302 domains · -29 vs yesterdayDNS DRIFT15 domains changed DNS providertop destination cloudflare.com · -1 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.comCERT DRIFT2 domains switched issuing CA24h · -3 vs yesterdayNOW3,329 curated domains not answeringlast probe, steadyERRORS10,919 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,522 material changesacross 2,302 domains · -29 vs yesterdayDNS DRIFT15 domains changed DNS providertop destination cloudflare.com · -1 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.comCERT DRIFT2 domains switched issuing CA24h · -3 vs yesterdayNOW3,329 curated domains not answeringlast probe, steadyERRORS10,919 responded with an errorlast probe · 5xx / 404 / 429 / 403

rio.cloud

Observed 2026-07-13T16:37:35.654Z (8h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesStripeDocuSignGoogle Search ConsoleSlackMiro
4 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat rio.cloud actually stands on - every host below is a signed observation
rio.cloud
A / AAAA
95.130.254.12
Cloudflareserves the site
NS
ns-1363.awsdns-42.orgns-1700.awsdns-20.co.ukns-137.awsdns-17.comns-755.awsdns-30.net
awsdns-42.org + awsdns-20.co.uk + moreanswers its DNS
MX
rio-cloud.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 307 → https://rio.cloud/de/
HTTP status307
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time258 ms
DNS resolutionNOERROR
Redirect chain
https://rio.cloud/de/

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

DNS Records

A 1

  • 95.130.254.12

MX 1

  • 0rio-cloud.mail.protection.outlook.com

TXT 17

  • SFMC-r6aVygPXvpUSzdOKO3OU3Xo5c8v-rYeRpDqnrDlk
  • openai-domain-verification=dv-aCYNymRi8sggk6R6MapMRttT
  • bw=/C7I2JEUqfInbQaVujo8VPFF4DjM2qv0NHYC/YG1aSwp
  • v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com a:zgateway.zuora.com -all
  • gradle-verification=26MP7STGVGQ1FTCU73I24R98HTJBG
  • amazonses:DA+b2L2WOJ00iSEml1pOj5DE7qjaeBtyB2uogat6taU=
  • configcat-domain-verification=08db2545-b938-4cd0-83a8-4cb10abb6d9c
  • onetrust-domain-verification=465023c1110248a6a23df4f2c38164cd
  • stripe-verification=FD595DEE882DD1A6A5A620B93C196B665E25562CD3FF25665749D53D6EDFA820
  • onetrust-domain-verification=1c2af2a8b6114c38a09486e8d16a1d93

NS 4

  • ns-1363.awsdns-42.org
  • ns-1700.awsdns-20.co.uk
  • ns-137.awsdns-17.com
  • ns-755.awsdns-30.net

SOA 1

  • ns-1363.awsdns-42.org awsdns-hostmaster.amazon.com

TLS Certificates (0)

None.

Subdomains (4)

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

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

Ed25519 Receipt

Receipt ID
cfe6ab72-5c76-4acd-925e-da0f779a8f53
Output Hash
877a383308bd246dbd421d51af44da3fa96b4b0e97cb647b412a64316ffaf91a
Signature
ed25519:211d62e9268a41c8f0fd99d8e244be19cfe6b5a81703e5d7c6931a889688ffcb912127f62b909a1240c5ddb6a915e10d8e489871e2248034171112bddb620f0e
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser