Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations271 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records1 A records, 224 ms lookupPASS
| A | 95.181.181.56 |
| AAAA | — |
| CNAME | — |
| NS | ns3-l2.nic.ru, ns4-l2.nic.ru, ns8-l2.nic.ru, ns4-cloud.nic.ru, ns8-cloud.nic.ru |
| MX | 10 mail1.regnum.su 20 mail.regnum.su |
| TXT | yandex-verification: dc95a4dea6dcf4e4 SPF v=spf1 a mx mx:regnum.ru ip4:92.53.81.198 ip4:176.114.93.2 ~all google-site-verification=MXJzTpNyPWMLnUJR-qEesyBGYH9mQRvKysccT78Xt-g _globalsign-domain-verification=ejubTmq8oKlTYaWWgtb13t55jWglNWKvVarNUQwtzQ |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Redirect ChainNo redirects — direct accessPASS
https://regnum.ru
502 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://regnum.ru | 200 | 502 ms | HTTP/1.1 | nginx |
A+Crawlabilityrobots.txt present, sitemap with 12 URLsPASS
User-agent: Yandex
Disallow: /search
Disallow: /pdfnews/
Disallow: /pdf/article/
Disallow: /sneakpeek
Host: https://regnum.ru
Clean-param: fromamp&nw&&fromtg&site_id&ref&t&noredir&forprint&from&hbc&mkt_tok /
Clean-param: utm_follow&utm_partner_id&utm_site&utm_source&utm_medium&utm_term&utm_campaign&utm_follow_ch /
Clean-param: clid&id&erid /
User-agent: Googlebot
Disallow: /search
Disallow: /pdfnews/
Disallow: /pdf/article/
Disallow: /sneakpeek
Sitemap: https://regnum.ru/sitemap.xml
User-agent: *
Disallow: /search
Disallow: /pdfnews/
Disallow: /pdf/article/
Disallow: /sneakpeek
- https://regnum.ru/sitemap/admin.xml
- https://regnum.ru/sitemap/article.xml
- https://regnum.ru/sitemap/authors.xml
- https://regnum.ru/sitemap/dossiers.xml
- https://regnum.ru/sitemap/embed.xml
- https://regnum.ru/sitemap/images.xml
- https://regnum.ru/sitemap/news.xml
- https://regnum.ru/sitemap/opinion.xml
- https://regnum.ru/sitemap/photo.xml
- https://regnum.ru/sitemap/rubric.xml
- https://regnum.ru/sitemap/tags.xml
- https://regnum.ru/sitemap/videos.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceregnum.ru — via RD-RU, 24 years, 5 months old, hosted on EDGECENTERLLC, RUPASS
231 days
February 28, 2027
271 days
Issued by GlobalSign nv-sa
24 years, 5 months
Registered February 28, 2002
Status unknown
Protects against DNS spoofing
EDGECENTERLLC, RU
ASN AS210756
95.181.181.56
RD-RU
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice