bogema1.ru
Observed Aug 16, 2026, 14:09 UTC (16h 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 EncryptSteady. No change on record for bogema1.ru 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
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
91.228.225.102
MX 2
10mx1.timeweb.ru10mx2.timeweb.ru
TXT 2
v=spf1 include:_spf.timeweb.ru ~allv=DNSSEC1; (detected)
NS 4
ns1.timeweb.runs3.timeweb.orgns4.timeweb.orgns2.timeweb.ru
SOA 1
ns1.timeweb.ru dns.timeweb.ru
TLS Certificates (0)
None.
Subdomains (2)
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_53431ed53a4d6ea4- Output Hash
adf9ef27e86ca7ddb7f28c0274deb904dce32efa424463ab567cc600408faa07- Signature
ed25519:0fd4223eb7d5ebc174060a8e3b16f70248a81268148411953b94c7e473762f326995d12da2e3a37b1ac47274ae2452d1f9175d47967d0402c8c23860d745d40c- Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff- Parent
(genesis)- Plane
- fast