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
BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /main/?a=td
Disallow: /main/?a=templates
Disallow: /secure/
Disallow: /*?ajax=1
Disallow: /feat/
Disallow: /qa/index.php/user
Disallow: /qa/index.php/login
Disallow: /qa/index.php/register
Disallow: /qa/index.php/tag
Disallow: /qa/index.php/hot
Disallow: /qa/index.php/questions
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations160 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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, 28 ms lookupPASS
| A | 193.109.246.46 |
| AAAA | — |
| CNAME | — |
| NS | ns1.ucoz.ru, ns3.ucoz.ru, ns2.ucoz.ru |
| MX | 1 mx100.ucozmail.com |
| TXT | google-site-verification=OLfI5UQlUmD2-HUs0sd54A4coTj3i-d7UmQpZp87wUc _globalsign-domain-verification=1Oqv63PtDK7_g_xQPe6J2sNOZ_fDZE3QzQvnsAwTmm google-site-verification=B-Am6kjHorjuBRHPcfYkPQFWBYdP5faY5CqnAIYiNbo SPF v=spf1 mx a:mx100.ucozmail.com ~all |
| 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.
ARedirect Chain1 redirect(s), 688 ms totalPASS
https://ucoz.ru
304 ms · HTTP/1.1
https://www.ucoz.ru/
384 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ucoz.ru | 301 | 304 ms | HTTP/1.1 | nginx |
| 2 | https://www.ucoz.ru/ | 200 | 384 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligenceucoz.ru — via R01-RU, 20 years, 11 months old, hosted on COMPUBYTE-AS, CYPASS
66 days
August 20, 2026
160 days
Issued by GlobalSign nv-sa
20 years, 11 months
Registered August 20, 2005
Status unknown
Protects against DNS spoofing
COMPUBYTE-AS, CY
ASN AS204343
193.109.246.46
R01-RU
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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