CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 14,396 material changesacross 13,841+ domains · 24h to ~10h ago · a floor, 14h of 24 walkedSHIFT6 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signal

younglifestore.com

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

This reading of younglifestore.com was taken 1d ago

younglifestore.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting younglifestore.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 younglifestore.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Secured byLet's Encrypt
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-02 14: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 younglifestore.com actually stands on - every host below is a signed observation
younglifestore.com
A / AAAA
23.227.38.65
Cloudflareserves the site
NS
ns-1019.awsdns-63.netns-1208.awsdns-23.orgns-2011.awsdns-59.co.ukns-369.awsdns-46.com
awsdns-63.net + awsdns-23.org + moreanswers its DNS
TLS
younglifestore.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 23.227.38.65

NS 4

  • ns-1019.awsdns-63.net
  • ns-1208.awsdns-23.org
  • ns-2011.awsdns-59.co.uk
  • ns-369.awsdns-46.com

SOA 1

  • ns-369.awsdns-46.com awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; pct=100

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
younglifestore.com C=US, O=Let's Encrypt, CN=YE2 Thu, 03 Sep 2026 23:45:33 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_c71f8d210e896250
Output Hash
49c57b0e3d8e2db6179da18eadc4cb9a032f81cd5d9d2acbdc321ab3c72e229e
Signature
ed25519:955e192c61cae545a15fe32f5dbe8a170acfe20f215eb45146f1548fb6f4f69660cbf723868c2235ac6b5ed3f3564a182cab24fb9c0e3ae99b865fbda0702f0d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser