maybelline.fr

Observed Aug 16, 2026, 18:43 UTC (10h 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.

Up right now
Runs onCloudflare
Secured byGoogle Trust Services
Also usesMicrosoft 365Facebook/MetaGoogle Search Console
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for maybelline.fr 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.

INFRASTRUCTURE MAPwhat maybelline.fr actually stands on - every host below is a signed observation
maybelline.fr
A / AAAA
104.18.35.191172.64.152.652606:4700:440d::6812:23bf2a06:98c1:3100::ac40:9841
Cloudflareserves the site
NS
adam.ns.cloudflare.comleia.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
maybelline.fr
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 104.18.35.191
  • 172.64.152.65

AAAA 2

  • 2606:4700:440d::6812:23bf
  • 2a06:98c1:3100::ac40:9841

TXT 4

  • MS=ms86183360
  • facebook-domain-verification=647gpagrg91pwogl8xqg3w2ogoysll
  • google-site-verification=9IjmTYl7u0Y5XxAcRor3Q1tb3vP2Q2eAHBAyn8GmUUM
  • v=spf1 -all

NS 2

  • adam.ns.cloudflare.com
  • leia.ns.cloudflare.com

SOA 1

  • adam.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
maybelline.fr C=US, O=Google Trust Services, CN=WE1 Thu, 01 Oct 2026 04:59:32 +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.

WILDCARD DNSobserved 2026-08-16 18:43 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 Receipt

Receipt ID
rcpt_cf04f2ab5e36cd6a
Output Hash
b32c576536cc0e0b081fb83f653735920b7bfc97264936143e1da3421cc22c0b
Signature
ed25519:81f3cbead6e50448d2e501c139215507f4aac05ba522693a2b29f916cbb329c611e1b80d22774649635162726f02e78c1f62593f895deca11d40c8039c2f2f06
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,452 material changesacross 38,568 domains · 24h to ~80m ago · +1,212 vs yesterdayROTATION58 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hEMAIL DRIFT4 domains switched email providertop destination alltheemails.comNOW581 curated domains not reachablelast probe, steadySITE ERRORS34,974 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,472 sites429 rate-limit / 403 bot-block, a posture signal