paypal-account.com

Observed Aug 25, 2026, 04:14 UTC (3m ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Not responding
Runs onCloudflare
Registered withSav.com, LLC
96 subdomains · watched
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for paypal-account.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 time190 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.

MCP This domain advertises an AI service endpoint at _mcp._tcp.
1 endpoint - withheld

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 10

A2NS2MX1TXT4SOA1

TLS certificates 0

None.

Subdomains 96

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

WILDCARD DNSobserved 2026-08-25 04:14 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works

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_de5e853bee14c16f
Output Hash
e3e403bb93c5f75ef4e4413d10bff7e1ea2499ce6516e20d2299c2acee7c68a2
Signature
ed25519:ef02a9a1506613e73bffde91777ae53dc3765033e0ea681d4d0cdd7e2b3112d7dc7d62d052a0cfeb630eaee2e9b342f31e28a7dc2609b5e0a6256ddf84bba804
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT10,605 material changesacross 8,939 domains · 24h to ~60m agoROTATION60 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination outlook.comREGISTRAR DRIFT2 changed registrar24hNOW441 curated domains not reachablelast probe, steadySITE ERRORS17,747 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 78,830 sites429 rate-limit / 403 bot-block, a posture signal