3secureserver.xyz

Observed Aug 24, 2026, 13:36 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of 3secureserver.xyz was taken 1d ago

3secureserver.xyz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting 3secureserver.xyz 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 3secureserver.xyz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Guarded by a firewall
Runs onCloudflare
Registered withOwnRegistrar, Inc.
5 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 3secureserver.xyz 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

Bot-blocked Blocked our probe (WAF / bot protection) 403 blocked by cloudflare - bot protection active
HTTP status403
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time1,861 ms
DNS resolutionNOERROR
What this reading means

A security layer answered instead of the site. That is a working defence doing its job, and we record it as its own state rather than as a failure.

It does NOT mean the site is down or misconfigured. It also does not mean we were treated as hostile - most rules of this kind refuse every non-browser client alike.

What produces this, in rough order of how often
  • A WAF or bot-management rule refuses non-browser user agents by default.
  • Automated traffic from datacenter networks is challenged as a matter of policy.

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 7

A1NS2MX1TXT2SOA1

TLS certificates 0

None.

Subdomains 5

5 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_96fecfbdd0080498
Output Hash
70264d5ae9edfdbcf5e7900f3bfa78923c5e40d4795dbb6f6f511a55b787d547
Signature
ed25519:154d9803e70261dcebefa6fcb946279ce2c4df4c97f43b37d4cb27e759ce9a90fb1aafadeec9f6bac66d4e0ff7e13e8d45e1d7487488299fb5058933935bee07
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT4,399 material changesacross 2,862 domains · 24h to ~2h agoDNS DRIFT96 domains changed DNS providertop destination koaladns.com · +13 vs yesterdayEMAIL DRIFT2 domains switched email provider24hREGISTRAR DRIFT2 changed registrar24hNOW520 curated domains not reachable+100 vs yesterdaySITE ERRORS17,745 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 78,737 sites429 rate-limit / 403 bot-block, a posture signal