musicplayer.com

Observed Aug 29, 2026, 17:08 UTC (8h 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.

Verify this receipt yourself + Watch this domain

Not responding

Runs onAmazon

Registered withGoDaddy.com, LLC

Also usesGoogle Search Console

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 musicplayer.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

Timed out No response within the timeout Connection timed out - no response within 3s

HTTP status0

Servernot observed

TLS protocolnot observed

TLS issuernot observed

Behind Cloudflareno

Time spent waiting6,200 ms (2 attempts, 3s each) - nothing answered

DNS resolutionNOERROR

What this reading means

Nothing answered on 443 inside our budget: 2 attempts of 3s each, from Cloudflare's network. DNS resolved, so the name and its delegation are fine - the failure is below that, at the connection or HTTP layer.

It does NOT mean the site is down for everyone. Our budget is deliberately tight so a two-million-domain sweep stays affordable, and a site that is merely slow will miss it while working fine in a browser.

Probed from Cloudflare's network. A site can be healthy and still not answer us: use the live checks on the domain page to run the same probe from your own network and compare.

What produces this, in rough order of how often

The origin takes longer than 3s to send its first byte - real users see this as a slow site, not a broken one.
A firewall DROPS our packets rather than refusing them. A refusal would have come back as "connection refused"; silence is what a drop rule looks like from outside.
Traffic from datacenter or cloud networks is filtered. We egress from Cloudflare, which many origins treat differently from a residential connection.
An AAAA record is published for an address that is not actually serving, so clients that prefer IPv6 hang.
The origin only answers browser-like requests. We identify ourselves as DomainDrift rather than impersonating a browser.

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 6

A2NS2TXT1SOA1

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_c9ef397c150b7dc4
Output Hash: 50110e15db9302ca49c9afc2fb07585c8ca0c42bf6bd7af4933ab4b9df7c5b0f
Signature: ed25519:7ee46ef3067f811ff1d7e9aa0c55b23b40622a515880405c97efaf28c43cc1c6a8057624655d72e0cd41baf0650dfabfe7fd458ebd3ad563ae1deea16ef94601
Public Key: ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent: (genesis)
Plane: fast