CONTINUOUS INTERNET TELEMETRY24H DRIFT2,889 material changesacross 2,543 domains · -509 vs yesterdayDNS DRIFT20 domains changed DNS providertop destination cloudflare.com · -7 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination reyrey.com · -2 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,962 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,889 material changesacross 2,543 domains · -509 vs yesterdayDNS DRIFT20 domains changed DNS providertop destination cloudflare.com · -7 vs yesterdayEMAIL DRIFT4 domains switched email providertop destination reyrey.com · -2 vs yesterdayCERT DRIFT7 domains switched issuing CA24hNOW3,308 curated domains not answering-6,410 vs yesterdayERRORS10,962 responded with an errorlast probe · 5xx / 404 / 429 / 403

princess.com

Observed 2026-07-12T19:22:45.795Z (15h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Also usesGoogle Search Console
hospitality
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat princess.com actually stands on - every host below is a signed observation
princess.com
A / AAAA
23.61.42.245
Cloudflareserves the site
NS
usw4.akam.netusw1.akam.neteur6.akam.netasia2.akam.net+4 more
akam.netanswers its DNS
MX
carnival-com.mail.protection.outlook.commail3.princess.commail4.princess.com
Microsoft 365receives its email

HTTPS probe

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

  • 23.61.42.245

MX 3

  • 10carnival-com.mail.protection.outlook.com
  • 20mail3.princess.com
  • 20mail4.princess.com

TXT 9

  • _mos0p3osi2wew4qka5hj1xx58gtdbi9
  • knowbe4-site-verification=87f853c8a6ca37a55c53ae74128096d
  • ms-domain-verification=e0e21981-40d9-413a-a1eb-e0a09e1b82bf
  • google-site-verification=ixM2oqt9-U0I3kLeLwSOjQ3GiW8cJi8EVXgx5oHfbQk
  • v=spf1 mx include:spf.protection.outlook.com include:spf.sabre.com -all
  • MS=ms38124960
  • mMQ5O/EO3cz7AwkgnO9tHKVXD8e2fKOvBWL9kzEvLSrSX2sA377sOoBTceG1WAyyBg/BW8AWxT7+md+I7Wccew==
  • google-site-verification=HN8PcjJUWyXbAN73m22wtBm6Nlk3tKkCjF3Fam4SCLo
  • v=DMARC1; p=reject; rua=mailto:carnivaldmarc@carnival.com; pct=100

NS 8

  • usw4.akam.net
  • usw1.akam.net
  • eur6.akam.net
  • asia2.akam.net
  • ns1-208.akam.net
  • ns1-136.akam.net
  • usc4.akam.net
  • use9.akam.net

SOA 1

  • princess.com domains.princess.com

TLS Certificates (0)

None.

Subdomains (8)

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

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

Ed25519 Receipt

Receipt ID
cf3dd7f3-1f85-4269-abdc-e94cc3f1d0bc
Output Hash
01659a5566f52b91b7f647967c21417b7925b58c06ccc16c352376d00a0b0929
Signature
ed25519:8857405e1ae9ede9040658020be8696f53a515a017e439925f7820441a8adc047a65f3f68b04d4cae4603de81bae7bd94495e53767b0af639f6bcaf8b89ce30b
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser