lotus33br.com

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

This reading of lotus33br.com was taken 2d ago

lotus33br.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lotus33br.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 lotus33br.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Registered withSNAPNAMES 80, LLC
96 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 lotus33br.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

Up Responding normally (2xx) 200 OK
HTTP status200
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time115 ms
DNS resolutionNOERROR

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 6

A1NS2MX1TXT1SOA1

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-09 11:44 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_ad6d05ff428fb371
Output Hash
41bd32fba2d418561521a533a56b6ed94dfa4dd58d02dc5c16da3fa188a32afc
Signature
ed25519:a1ea63036311b0ff2494f0b1e69e7abe553571af0cea6acdbcead3b138435fba12fc1bd686987472dab7e3f4f41446a15fe53aa4f3cb6e3aae1b9a20a2808608
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT24,064 material changesacross 12,924 domains · 24h to ~3h agoROTATION54 domains moved DNS from kirklanddc.com to koaladns.com, 49 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email provider24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT3 changed registrar24hNOW264 curated domains not reachablelast probe, steadySITE ERRORS17,813 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 79,261 sites429 rate-limit / 403 bot-block, a posture signal