CONTINUOUS INTERNET TELEMETRY24H DRIFT402 material changesacross 346 domains · -1,234 vs yesterdayDNS DRIFT3 domains changed DNS providertop destination cloudflare.com · -14 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -7 vs yesterdayNOW50,166 curated domains not answering+35,743 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block24H DRIFT402 material changesacross 346 domains · -1,234 vs yesterdayDNS DRIFT3 domains changed DNS providertop destination cloudflare.com · -14 vs yesterdayEMAIL DRIFT1 domain switched email providertop destination google.com · -7 vs yesterdayNOW50,166 curated domains not answering+35,743 vs yesterdayERRORS8,524 responded with an errorlast probe · 5xx / 404 / TLSTHROTTLED2,335 throttled or blocked our scanner429 rate-limit / 403 bot-block

amazonaws.com.cn

Observed 2026-07-15T04:55:18.535Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
2 subdomains · tranco_5k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat amazonaws.com.cn actually stands on - every host below is a signed observation
amazonaws.com.cn
A / AAAA
43.192.37.20140.179.122.23552.83.70.2552.81.170.225+2 more
Cloudflareserves the site
NS
ns-2419.awsdns-cn-23.bizns-intl-630.awsdns-cn-39.comns-1733.awsdns-cn-44.netns-630.awsdns-cn-39.com+2 more
awsdns-cn-23.biz + awsdns-cn-39.com + moreanswers its DNS
MX
mail.nwcdcloud.cn
nwcdcloud.cnreceives its email

HTTPS probe

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

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

DNS Records

A 6

  • 43.192.37.20
  • 140.179.122.235
  • 52.83.70.25
  • 52.81.170.225
  • 54.223.86.57
  • 52.83.128.157

MX 1

  • 10mail.nwcdcloud.cn

TXT 5

  • v=spf1 ip4:52.83.214.130 ip4:52.83.103.181 ip4:52.83.99.146 ip4:69.231.146.73 ip4:43.192.5.4 include:amazon.com -all
  • TS1760027
  • spf2.0/pra ip4:52.83.214.130 ip4:52.83.103.181 ip4:52.83.99.146 ip4:69.231.146.73 ip4:43.192.5.4 include:amazon.com -all
  • MS=ms46061738
  • v=DMARC1; p=quarantine; pct=100; rua=mailto:report@dmarc.amazon.com; ruf=mailto:report@dmarc.amazon.com

NS 6

  • ns-2419.awsdns-cn-23.biz
  • ns-intl-630.awsdns-cn-39.com
  • ns-1733.awsdns-cn-44.net
  • ns-630.awsdns-cn-39.com
  • ns-3287.awsdns-cn-13.cn
  • ns-intl-3287.awsdns-cn-13.cn

SOA 1

  • dns-external-route53.cn-north-1.amazonaws.com.cn root.amazon.com

TLS Certificates (0)

None.

Subdomains (2)

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

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

Ed25519 Receipt

Receipt ID
2ced20af-1448-4a17-bbf3-fc8c92e5fc14
Output Hash
fc2568dbcfde80111ea836a2a8107b10781a8db4e0874d09ebf526cee95d2b6a
Signature
ed25519:8ba338965a62cb3e134ee17a90f2cb501655b0da35eaee3ccab3b9c8439fd2af72d68eec53fa32439e066f6db052847f6f0b1c42b7378a5a593db407314b9e0f
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser