listerine-jp.com

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

This reading of listerine-jp.com was taken 12d ago

listerine-jp.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting listerine-jp.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 listerine-jp.com 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 withKey-Systems GmbH
Also usesGoogle Search Console
IPv6 · 2 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 listerine-jp.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

Bot-blocked Blocked our probe (WAF / bot protection) 403 blocked by cloudflare - bot protection active
HTTP status403
Servercloudflare
TLS protocolHTTP/3
TLS issuernot observed
Behind Cloudflareyes
Response time71 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 20

A2AAAA2NS8MX2TXT5SOA1

TLS certificates 0

None.

Subdomains 2

2 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_6bda5ffab524e9cf
Output Hash
9b244c8f758bc5008954d62d0b3052e5c0d13c88f5164745539580451b2df693
Signature
ed25519:e518f330971f3760996f7f7e41c110c6467fefb696adaefcafbd0315a05a3b56d503271fe38b6d366e7fd5e5227a28b90853a9e95c37c68b0abd9761ff1cbb0b
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT30,061 material changesacross 23,618 domains · 24h to ~2h agoROTATION60 domains moved DNS from koaladns.com to magpiedns.com, 60 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT3 changed registrar24hNOW610 curated domains not reachablelast probe, steadySITE ERRORS17,392 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 79,534 sites429 rate-limit / 403 bot-block, a posture signal