Skip to content
https://vk.me

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
Crawlability
Action
no robots.txt, sitemap with 0 URLs
REVIEW
no robots.txt, sitemap with 0 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

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

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
314 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

314
days left
0d 30d 60d 90d+

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 Records
6 A records, 67 ms lookup
PASS
6 A records, 67 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 87.240.132.78, 87.240.129.133, 87.240.132.72, 87.240.137.164, 93.186.225.194, 87.240.132.67
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.vkontakte.ru, ns2.vkontakte.ru, ns3.vkontakte.ru, ns4.vkontakte.ru
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 67 ms
Got: 67 ms
A87.240.132.78, 87.240.129.133, 87.240.132.72, 87.240.137.164, 93.186.225.194, 87.240.132.67
AAAA
CNAME
NSns1.vkontakte.ru, ns2.vkontakte.ru, ns3.vkontakte.ru, ns4.vkontakte.ru
MX
0 mx.vk.com
TXT
SPF v=spf1 -all
_globalsign-domain-verification=_AUAD9_npQGWkZWkHemy_YJLe_wLqZcdzcbf74TP7j
_globalsign-domain-verification=uwZs48HV005U7VCshf3dueaCUvM16p09NhOSxC1fZw
_globalsign-domain-verification=iAGxHRDOiw9AkcoqIoEOsJz_MkIFQ7AhHMoI0kSSRK
LD6VaYCKete4UB5FIx7snCoJ8bt1nGdeCWe4my5HH5psRaTlzAmvc
HARICA-w8CluQWUKn0gHs1Hcjr
_globalsign-domain-verification=OU9ZfOZPEfiR3cyBs182s9FWh77AZXsGR_41NgoLlZ
CAALookup not available with standard resolver
Resolved in 67 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 484 ms total
PASS
1 redirect(s), 484 ms total
Info::
Single redirect
Got: https://vk.me → https://vk.me/app (301)

https://vk.me

184 ms · HTTP/1.1

301

https://vk.me/app

300 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vk.me301184 msHTTP/1.1kittenx
2https://vk.me/app200300 msHTTP/1.1kittenx

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.vk.me/
200https://vk.me/

Preferred variant: non-www

HTTP → HTTPS

301http://vk.me/ https://vk.me/

Consistent

A+
Domain Intelligence
vk.me — via Regional Network Information Center, JSC dba RU-CENTER, 16 years, 11 months old, hosted on VKONTAKTE-SPB-AS vk.com, RU
PASS
vk.me — via Regional Network Information Center, JSC dba RU-CENTER, 16 years, 11 months old, hosted on VKONTAKTE-SPB-AS vk.com, RU
Info::
Domain registered until Jul 24, 2026 (3 months remaining)
Info::
Registrar: Regional Network Information Center, JSC dba RU-CENTER
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: VKONTAKTE-SPB-AS vk.com, RU
Got: AS47541
Domain expiry

10 days

July 24, 2026

SSL certificate

314 days

Issued by GlobalSign nv-sa

Domain age

16 years, 11 months

Registered July 24, 2009

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

VKONTAKTE-SPB-AS vk.com, RU

ASN AS47541

87.240.132.72

Registrar

Regional Network Information Center, JSC dba RU-CENTER

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar Regional Network Information Center, JSC dba RU-CENTER
Created July 24, 2009 (16 years, 11 months ago)
Expires July 24, 2026 (3 months)
Last Updated July 27, 2025
Name Servers ns1.vkontakte.ru, ns2.vkontakte.ru, ns3.vkontakte.ru, ns4.vkontakte.ru
Registrant Privacy protection service - whoisproxy.ru
Hosting
IP Address 87.240.132.72
ASN AS47541 (VKONTAKTE-SPB-AS vk.com, RU)
Provider VKONTAKTE-SPB-AS vk.com, RU
Data source: whois (1.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 241 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
67 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
57 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
60 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
241 ms
Total Time Total request time from DNS lookup through full response.
241 ms

Connection waterfall

DNS Lookup 67 ms TCP Connect 57 ms TLS Handshake 60 ms Server Processing 58 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback