bidstreamserver.com
Observed Aug 16, 2026, 12:22 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.
Cloudflare
Let's EncryptHTTPS probe
The site answered with a 5xx, so the edge and TLS are working and the application behind them is not.
It does NOT mean the domain or its DNS is misconfigured - the request got all the way to an application to fail there.
- The origin is erroring or mid-deploy.
- An upstream in front of the origin cannot reach it.
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".
DNS Records
A 1
206.189.236.43
NS 3
ns1.digitalocean.comns2.digitalocean.comns3.digitalocean.com
SOA 1
ns1.digitalocean.com hostmaster.bidstreamserver.com
TLS Certificates (0)
None.
Subdomains (5)
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 receiptEd25519 Receipt
- Receipt ID
rcpt_089cd7a593fdc821- Output Hash
f6d6ee203f086e883a936c70cdefdab9f59d081dd029f85efcf8774a2e2f675b- Signature
ed25519:23b34b5cae578ae3315c0a1ccd073cf7af9caef1eecc82fd9cb357b088c9df48951ac2726af55e7cd37cebe779aa6fd673fadde1cd4290c69d3afc1a5dbb780a- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast