amperity.com

Observed Aug 23, 2026, 05:33 UTC (2d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of amperity.com was taken 2d ago

amperity.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting amperity.com under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch amperity.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Email byGoogle Workspace
Registered withNameCheap, Inc.
Also usesAtlassianAnthropicGoogle Search ConsoleDriftMicrosoft 365WrikeAtlassian StatuspageHubSpot
10 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for amperity.com in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

HTTPS probe

Rate-limited Rate limited us (429) 429 Too Many Requests - rate limited
HTTP status429
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time49 ms
DNS resolutionNOERROR
What this reading means

The host answered and asked us to slow down. Something is there and it is healthy enough to throttle.

It does NOT mean we were hammering the site. We probe a given domain minutes apart at most.

What produces this, in rough order of how often
  • A shared rate limit counts all traffic from an upstream network, not just ours.
  • A bot rule is expressed as a 429 rather than a block.

These are the known causes, not a diagnosis of this domain. We recorded that nothing answered; we did not measure why.

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

SIGNED-OUT VIEW Provider names, posture and counts are shown. The record values - every DNS answer, each subdomain hostname, raw TXT, IPs, cert names and WHOIS - are the product. Sign in for the full signed record, or use the API with a key.

DNS records 34

A1NS4MX5TXT23SOA1

TLS certificates 0

None.

Subdomains 10

10 subdomain hostnames observed and signed - the list itself is part of the paid record.

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; the only network request the check makes is for the published public keys.

Verify this receipt
Ed25519 receiptthe raw cryptographic proof
Receipt ID
rcpt_6107d03d55b00eb0
Output Hash
973fe19cbfde1d7613f3a7a2873b912aaee70df855dfbbcded0e343d8db8e73a
Signature
ed25519:8714726196c24e1de80be1ebe18cc181237e61899f7798f71547ef5aa5bda337539d3a29931a833d3bdea5af1e16724ecba26264bed39a178f1bdf9464baed0f
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT10,730 material changesacross 9,212 domains · 24h to ~2h agoROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination outlook.comREGISTRAR DRIFT1 changed registrar24hNOW456 curated domains not reachable+36 vs yesterdaySITE ERRORS17,743 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 78,814 sites429 rate-limit / 403 bot-block, a posture signal