CONTINUOUS INTERNET TELEMETRY24H DRIFT28,782 material changesacross 26,712 domains · last 24hROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 53 moved backa rotation loop, not a migration · 24hNOW598 curated domains not reachablelast probe, steadySITE ERRORS33,529 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,415 sites429 rate-limit / 403 bot-block, a posture signal

lancome.jp

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

This reading of lancome.jp was taken 5d ago

lancome.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lancome.jp 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 lancome.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Email byProofpoint
Secured byGoogle Trust Services
Also usesFacebook/MetaFigmaGoogle Search Console
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 22:49 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat lancome.jp actually stands on - every host below is a signed observation
lancome.jp
A / AAAA
172.64.149.239104.18.38.172a06:98c1:310d::6812:26112606:4700:440d::ac40:95ef
Cloudflareserves the site
NS
algin.ns.cloudflare.comrose.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
mxa-002fa101.gslb.pphosted.commxb-002fa101.gslb.pphosted.com
Proofpointreceives its email
TLS
lancome.jp
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 172.64.149.239
  • 104.18.38.17

AAAA 2

  • 2a06:98c1:310d::6812:2611
  • 2606:4700:440d::ac40:95ef

MX 2

  • 10mxa-002fa101.gslb.pphosted.com
  • 10mxb-002fa101.gslb.pphosted.com

TXT 5

  • MS=ms39969714
  • facebook-domain-verification=uv3t88zfp584r03jgd4rvtp7ezgz3q
  • figma-domain-verification=c424bc6af3b7647cf8a06852bcb817be547d3f958b450d4514f05229f5289273-1712856071
  • google-site-verification=ovgFWa-SKV4MOwqIEjNbzgIyla9T93Xu1u0CU2bL6CE
  • v=spf1 mx include:spf-002fa101.pphosted.com include:cust-spf.exacttarget.com a:production.jp.loreal.demandware.net a:development.jp.loreal.demandware.net -all

NS 2

  • algin.ns.cloudflare.com
  • rose.ns.cloudflare.com

SOA 1

  • algin.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:tnoff9hr@ag.eu.dmarcadvisor.com; aspf=s; adkim=s;

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
lancome.jp C=US, O=Google Trust Services, CN=WE1 Sun, 18 Oct 2026 19:26:39 +0000
WE1 C=US, O=Google Trust Services LLC, CN=GTS Root R4 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R4 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (0)

None observed.

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 Receipt

Receipt ID
rcpt_b278a246cb354603
Output Hash
fbe0c6f302b8ade7356911a1822c6c29c44810badd40a705414ee85b47a88dcc
Signature
ed25519:1c4419c15e26385cf94a7bba9f8b5cf5d0d762ceb97d3a7b61bdee7de809a38291472ef3fe4725856d87663de0357c22aa26790c3091f75a50a3ad568169dd0d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser