CONTINUOUS INTERNET TELEMETRY24H DRIFT2,253 material changesacross 2,053 domains · +294 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW4,511 curated domains not answering+1,082 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT2,253 material changesacross 2,053 domains · +294 vs yesterdayDNS DRIFT19 domains changed DNS providertop destination cloudflare.comEMAIL DRIFT8 domains switched email providertop destination outlook.com · +5 vs yesterdayNOW4,511 curated domains not answering+1,082 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

sooma.com

Observed 2026-07-15T00:03:33.615Z (20h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Registered withRealtime Register B.V.
Also usesGoogle Search Console
18 subdomains · tranco_40k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat sooma.com actually stands on - every host below is a signed observation
sooma.com
A / AAAA
213.205.79.2
Cloudflareserves the site
NS
berlin.sooma.comtokyo.sooma.compalermo.sooma.comlisbon.sooma.com+1 more
sooma.comanswers its DNS
MX
smtpin1.smail.eusmtpin2.smail.eu
smail.eureceives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://sooma.com/pt-pt/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1968 ms
DNS resolutionNOERROR
Redirect chain
https://sooma.com/pt-pt/

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

DNS Records

A 1

  • 213.205.79.2

MX 2

  • 10smtpin1.smail.eu
  • 20smtpin2.smail.eu

TXT 9

  • v=spf1 mx include:_spfi.smail.eu include:spf.mydomainprovider.com ip4:94.46.130.39 ip4:94.46.130.38 -all
  • MS=ms23280504
  • MS=5A2F72FE03514B6BF8FA6F22A2D49FB2C5203934
  • paddle-verification=fc74dada
  • nosintegrator-ethiack-verification=870c013d88922dd646354cde731d36f5986ece897c70d3069f93162bccefa3beaadc20e5842722f32c131f0a2de31d5c6fe3e0c178db6fb708f77cfa0e373c1b
  • google-site-verification=m52ytjdPFb76nC2rMxY8TUf69x8c_MniXZSdMyW1rNI
  • yahoo-verification-key=9lzB+rGdMJxGUxNCBdlMWpbQXbMIeQcMK6WObrzITgo=
  • v=DMARC1; p=reject; rua=mailto:dmarc+sooma.com@sooma.com; ruf=mailto:dmarcf+sooma.com@sooma.com; fo=1
  • v=DNSSEC1; (detected)

NS 5

  • berlin.sooma.com
  • tokyo.sooma.com
  • palermo.sooma.com
  • lisbon.sooma.com
  • rio.sooma.com

SOA 1

  • berlin.sooma.com support.sooma.com

CAA 3

  • iodef mailto:caa.incident.reporting@sooma.com
  • issue letsencrypt.org
  • issue certum.pl

TLS Certificates (0)

None.

Subdomains (18)

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

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

Ed25519 Receipt

Receipt ID
d2528be8-2da0-45ab-86e6-fb339c9b8115
Output Hash
06e717368750d5d730ff5cd9fa4a26dad8343abc37730b51e75b2e81c117f7e0
Signature
ed25519:f38bb27a0425150e16c27b4ff8b711a0dea35d1290310c38e607cc275b29ad6e15dd311c35fa70b239c4bb48450395eb1eca3ebc610227ce9c2632dc6052fd0c
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser