prime-revenue.com

Observed Jun 12, 2026, 06:46 UTC (81d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of prime-revenue.com was taken 81d ago

prime-revenue.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting prime-revenue.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 prime-revenue.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
DRIFT

Steady. No change on record for prime-revenue.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

Server error Server error (5xx) 525 Server Error
HTTP status525
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time108 ms
DNS resolutionNOERROR
What this reading means

The site answered with a 5xx, so the edge and TLS are working and the application behind them is not.

It does NOT mean the domain or its DNS is misconfigured - the request got all the way to an application to fail there.

What produces this, in rough order of how often
  • The origin is erroring or mid-deploy.
  • An upstream in front of the origin cannot reach it.

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 5

A2NS2SOA1

TLS certificates 0

None.

Subdomains 1

1 subdomain hostname 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_58de06af22ca4768
Output Hash
e2e98988b338437522d47ea1e51256c6bb3a4e76d8b6f98ebd10859f0cd0c1b5
Signature
ed25519:3c0a04cdf971715cba14bb4084e01ac544c54bd0edee46cf3daf380b2c709bfc44d830289d8f8627d8ae48ec60d6c13d186adcf20e6a41e13f6ae2707ab6d40b
Public Key
ed25519:1aafb422ddb6beba51f7cabe4ce1c400d51da23b2ec829bd74c9f89bb99801da
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT4,385 material changesacross 2,462 domains · 24h to ~75m ago · +200 vs yesterdayROTATION54 domains moved DNS from magpiedns.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT3 changed registrar24hNOW565 curated domains not reachablelast probe, steadySITE ERRORS18,223 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,774 sites429 rate-limit / 403 bot-block, a posture signal