myshopify.com

Observed Sep 15, 2026, 23:05 UTC (4m 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 · content on subdomains
Runs onCloudflare
Registered withMarkMonitor Inc.
Also usesFacebook/MetaGoogle Search Console
96 subdomains · tranco_1k
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

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

Content on subdomains The apex returns 404 by design; this domain serves its pages on subdomains 404 Not Found - domain resolves but no content at root
HTTP status404
Servercloudflare
TLS protocolHTTP/3
TLS issuernot observed
Behind Cloudflareyes
Response time133 ms
DNS resolutionNOERROR
What this reading means

This domain serves its content on subdomains, not the bare apex, so a 404 at the root is expected. The wildcard DNS and the subdomains below are what it is actually running.

It does NOT mean the site is broken or missing. A platform like this puts every tenant on its own subdomain and leaves the apex empty on purpose.

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 13

A1NS4TXT7SOA1

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-07 22:31 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_1ca8d6bf3aec9f7c
Output Hash
90e5721929aca9a980625950426f96ca026d4e9edcc3f5073ff1143a64f0f9e0
Signature
ed25519:78c145fe0188fc31a4597dc9537867f085c4be6bfdb5343ee2d4efcfe449830ef5b5a98aacd132ec4bacc2152e673332b23996d2e131c61f5e7afb1a4931f302
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
CONTINUOUS INTERNET TELEMETRY24H DRIFT24,664 material changesacross 19,845 domains · 24h to ~2h ago · +15,129 vs yesterdayROTATION51 domains moved DNS from koaladns.com to magpiedns.com, 49 moved backa rotation loop, not a migration · 24hNOW657 curated domains not reachable+34 vs yesterdaySITE ERRORS17,630 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 79,965 sites429 rate-limit / 403 bot-block, a posture signal