Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction3 redirect(s), 1045 ms totalFIX
https://vkontakte.ru
196 ms · HTTP/1.1
https://vk.com/login?act=vkcomredirect&t...
218 ms · HTTP/1.1
https://vk.com/
197 ms · HTTP/1.1
https://m.vk.com/
435 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://vkontakte.ru | 302 | 196 ms | HTTP/1.1 | kittenx |
| 2 | https://vk.com/login?act=vkcomredirect&t... | 301 | 218 ms | HTTP/1.1 | kittenx |
| 3 | https://vk.com/ | 302 | 197 ms | HTTP/1.1 | kittenx |
| 4 | https://m.vk.com/ | 200 | 435 ms | HTTP/1.1 | kittenx |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCrawlabilityActionrobots.txt present, no sitemapFIX
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.
Learn more ▾ ▴
Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.
Source: Google Search Central
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: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
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 & Recommendations320 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records6 A records, 59 ms lookupPASS
| A | 87.240.132.72, 87.240.129.133, 87.240.132.67, 87.240.137.164, 93.186.225.194, 87.240.132.78 |
| AAAA | — |
| CNAME | — |
| NS | ns2.vkontakte.ru, ns3.vkontakte.ru, ns4.vkontakte.ru, ns1.vkontakte.ru |
| MX | 10 mxs.mail.ru |
| TXT | LD6VaYCKete4UB5FIx7snCoJ8bt1nGdeCWe4my5HH5psRaTlzAmvc _globalsign-domain-verification=jt5zCAVj_4ZDyUunMSNPHRO2tK_6Rx-HprLUBklQfp google-site-verification=1VsatdhGM8bfwvyiVeSJc1uYX55nJCqV7K1DsG9jQWQ _globalsign-domain-verification=ErbV_j6HG3Z2xAnANKCsqERfMRch3lwnLxix0f3ipY HARICA-cRTBWxgxeshB7eiGZxB SPF v=spf1 ip4:185.29.130.131/32 ip4:5.61.237.184/32 ip4:109.239.142.26/32 ip4:185.2... atJ1QQ0fGXlJSD9DKrPatRQAB83O7mfrJvGeRBNgitM= _globalsign-domain-verification=BPFwddh_Xx8EN00syGSxrWpZqc_AMn-oc_WQd3Xmka |
| CAA | Lookup not available with standard resolver |
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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencevkontakte.ru — via RU-CENTER-RU, 19 years, 9 months old, hosted on VKONTAKTE-SPB-AS vk.com, RUPASS
109 days
September 30, 2026
320 days
Issued by GlobalSign nv-sa
19 years, 9 months
Registered September 30, 2006
Status unknown
Protects against DNS spoofing
VKONTAKTE-SPB-AS vk.com, RU
ASN AS47541
87.240.137.164
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