Skip to content
https://vc.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
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

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 30 ms TLS Handshake 32 ms Server Processing 721 ms Content Transfer 69 ms
B
TLS Certificate Expiry & Recommendations
46 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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 Records
1 A records, 32 ms lookup
PASS
1 A records, 32 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.65.149.135
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: noel.ns.cloudflare.com, iris.ns.cloudflare.com
Info::
5 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: 32 ms
Got: 32 ms
A185.65.149.135
AAAA—
CNAME—
NSnoel.ns.cloudflare.com, iris.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
unione-validate-hash=f8fe15ae30d4c85dfc69ad32d41493fe
google-site-verification=v2y6SdaU4Wssh1fQ-1HfeUUPSKqstRKx57cRa55CAxc
google-site-verification=EhOmqrGwgr8d691233bfPUksRilpeC8zQjmDjuSGqWg
google-site-verification=QAshzMiTgqQrqZvs57AJB63AAekjqdscbYfxZR_Zhiw
yandex-verification: 4d06a9eecc0ffb0c
SPF v=spf1 include:_spf.yandex.net include:spf.unisender.ru include:amazonses.com in...
mailru-verification: ac9eabe4562708b2
spf2.0/mfrom,pra include:senderid.unisender.com ~all
yandex-verification: 43e29126cf206c81
yandex-verification: 8a3a198679134aa5
CAALookup not available with standard resolver
Resolved in 32 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://vc.ru

https://vc.ru

753 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vc.ru200753 msHTTP/1.1QRATOR
A+
Crawlability
robots.txt present, sitemap with 606 URLs
PASS
robots.txt present, sitemap with 606 URLs
Info::
robots.txt is present
Got: 558 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 606 entries
Info::
Sitemap index with 606 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 558 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /my$
Disallow: /my/
Disallow: /notifications$
Disallow: /editor$
Disallow: /repost$
Disallow: /bookmarks$
Disallow: /drafts$
Disallow: /auth$
Disallow: /settings$
Disallow: /plus$
Disallow: /appearance$
Disallow: /discovery$
Disallow: /p/health$
Disallow: /admin$
Disallow: /email/unsubscribeDigest/*
Disallow: /m$
Disallow: /m/
Disallow: /cabinet$
Disallow: /achievements$
Disallow: /achievements/
Disallow: /*?redesign
Disallow: /*?from=rss*
Disallow: /*?modal=auth*
Disallow: /*?ref=*
Disallow: /*?writing=*
Disallow: /*?comment=*
sitemap.xml 200 OK
Type Sitemap Index URLs 606 entries Valid XML Yes
Child Sitemaps:
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.vc.ru/
200https://vc.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://vc.ru/ → https://vc.ru

Consistent

A+
Domain Intelligence
vc.ru — via RU-CENTER-RU, 22 years old, hosted on HLL-AS, RU
PASS
vc.ru — via RU-CENTER-RU, 22 years old, hosted on HLL-AS, RU
Info::
Domain registered until Aug 2, 2026 (3 months remaining)
Info::
Registrar: RU-CENTER-RU
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: HLL-AS, RU
Got: AS51115
Domain expiry

16 days

August 2, 2026

SSL certificate

46 days

Issued by Let's Encrypt

Domain age

22 years

Registered August 2, 2004

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

HLL-AS, RU

ASN AS51115

185.65.149.135

Registrar

RU-CENTER-RU

Unlocked 2 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created August 2, 2004 (22 years ago)
Expires August 2, 2026 (3 months)
Name Servers iris.ns.cloudflare.com, noel.ns.cloudflare.com
Registrant OOO Komitet
Hosting
IP Address 185.65.149.135
ASN AS51115 (HLL-AS, RU)
Provider HLL-AS, RU
Data source: whois (0.8s)

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.

Why this matters

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback