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
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations326 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
A+DNS Records1 A records, 159 ms lookupPASS
| A | 46.17.206.11 |
| AAAA | — |
| CNAME | — |
| NS | a2.ns.ix.ru, ns8-l2.nic.ru, b2.ns.ix.ru, ns4-l2.nic.ru |
| MX | 20 ul-edge.skbkontur.ru 20 nv-edge.skbkontur.ru |
| TXT | 202005101118023pdj0ka4xwavmtw58whfgauk3ek69q7494875kum2pgkapezvc detectify-verification=e7bc5bceae9faed83ffd83c307775e62 2021042207140352phgdlpd7x6j1zlwyg0omsc0bho33zbfz3xjybqugowhdkbe7 google-site-verification=ojHVyltAh0s9xA2HQAVv8wljjGQz91VEJTmcQHCCTnc 202106090538085kjk0ajy8zx9b95i8mdg3prdb47oc0rqgd1nky2rv9nq2o6syv google-site-verification=GFfCh16899gZZfox8VkqTmorKo0vFGlh1ly2M_4jSU8 202106090555024nho1ykwibge93ux7qt29coc5z8s2ydj0khxzx6x1o5hzqymam google-site-verification=ARvz7hFSULiInY5oOK3LtKxlLnjwvt1_vndTtKw_UD8 202102250903052gwm6g7120eff6ossbgj3z6duabvet1r5h190ykm3kb122ijan google-site-verification=kv7r09mfAxTKmK0cUJ4JQBqQ-ULzdypToVNOy_PNwr0 202106090546064fmuf5miwquoosy7xz3uney0z79msmc4crb6itdamgqq3lqhpj 202101220943022jtyyspi82oey2i2x2xzyuq8kc8bit06xh5p74mb7hnf4rwwld SPF v=spf1 ip4:46.17.200.0/21 ip4:81.91.43.171/32 ip4:81.91.47.135/32 ip4:81.176.95.... 202004222125050xtyteywrc7rq4qf4ztakz30lalbwq837cdy2izhinbv6gtae3 mailru: 8f80fe843f86d46a |
| 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.
A+Redirect Chain0 redirect(s), 200 ms totalPASS
https://kontur.ru
200 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://kontur.ru | 403 | 200 ms | HTTP/1.1 |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencekontur.ru — via RU-CENTER-RU, 28 years, 11 months old, hosted on SKBKONTUR-AS, RUPASS
110 days
October 31, 2026
326 days
Issued by GlobalSign nv-sa
28 years, 11 months
Registered October 8, 1997
Status unknown
Protects against DNS spoofing
SKBKONTUR-AS, RU
ASN AS49675
46.17.206.11
RU-CENTER-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