samaramuz.ru

Observed Aug 16, 2026, 04:34 UTC (1d 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.

Not responding
Runs onCloudflare
2 subdomains · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

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

INFRASTRUCTURE MAPwhat samaramuz.ru actually stands on - every host below is a signed observation
samaramuz.ru
A / AAAA
5.101.114.102
Cloudflareserves the site
NS
dns2.dns-root.orgdns3.dns-root.prodns1.dns-root.ru
dns-root.org + dns-root.pro + moreanswers its DNS
MX
mail.samaramuz.ru
samaramuz.rureceives its email

HTTPS probe

server_error Server error (5xx) 526 Server Error
HTTP status526
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time682 ms
DNS resolutionNOERROR
What this reading means

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.

What produces this, in rough order of how often
  • 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

  • 5.101.114.102

MX 1

  • 10mail.samaramuz.ru

TXT 1

  • v=spf1 a mx ~all

NS 3

  • dns2.dns-root.org
  • dns3.dns-root.pro
  • dns1.dns-root.ru

SOA 1

  • dns1.dns-root.ru support.fastvps.hosting

TLS Certificates (0)

None.

Subdomains (2)

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 Receipt

Receipt ID
rcpt_ad2470d93b9fb496
Output Hash
4999efa34f25976a4d751bf1769d90a5c29c23ed23daf2a6de80590411d0e089
Signature
ed25519:04f1e4b70425bcf0b7e8a5c368c932988b1b09aa83e24eaa8c47d33c6a72f126363fc3de76666fa9c7ac9365957ebd068916c2abae8862d29d0bab02946df401
Public Key
ed25519:7aad40f2d6399c207fe2fc15aade04a78324787a355d36725cc90687f9e10cff
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,452 material changesacross 38,568 domains · 24h to ~80m ago · +1,212 vs yesterdayROTATION58 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hEMAIL DRIFT4 domains switched email providertop destination alltheemails.comNOW581 curated domains not reachablelast probe, steadySITE ERRORS34,974 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,472 sites429 rate-limit / 403 bot-block, a posture signal