eazia-sdac.ru

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.

• 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-shaped requests. We identify ourselves honestly 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.