Skip to content
https://max.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
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

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 39 bytes
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.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 39 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /_api_
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
297 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

297
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
3 A records, 76 ms lookup
PASS
3 A records, 76 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 155.212.204.74, 155.212.204.140, 155.212.204.5
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.ok.ru, ns3.ok.ru, ns2.ok.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: 76 ms
Got: 76 ms
A155.212.204.74, 155.212.204.140, 155.212.204.5
AAAA
CNAME
NSns1.ok.ru, ns3.ok.ru, ns2.ok.ru
MX
10 emx.mail.ru
TXT
59d322b4-4f7e-47e7-9c73-440b62fa0586
SPF v=spf1 include:_spf.notify.vk.company include:_spf.mail.ru
google-site-verification=CZZtwl-zxUeGdPSEHisSQ6gzSCCx6gIyAkEhZYmPJQk
_globalsign-domain-verification=O0uFXBuyZL8rUKtLk6lEDfEnqmExErEqWa3JEnUQLc
CAALookup not available with standard resolver
Resolved in 76 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://max.ru

https://max.ru

221 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://max.ru200221 msHTTP/1.1kittenx
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.max.ru/
200https://max.ru/

Preferred variant: non-www

HTTP → HTTPS

301http://max.ru/ https://max.ru/

Consistent

A+
Domain Intelligence
max.ru — via RU-CENTER-RU, 27 years, 1 months old, hosted on VK-AS, RU
PASS
max.ru — via RU-CENTER-RU, 27 years, 1 months old, hosted on VK-AS, RU
Info::
Domain registered until Aug 31, 2026 (4 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: VK-AS, RU
Got: AS47764
Domain expiry

79 days

August 31, 2026

SSL certificate

297 days

Issued by GlobalSign nv-sa

Domain age

27 years, 1 months

Registered August 9, 1999

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

VK-AS, RU

ASN AS47764

155.212.204.5

Registrar

RU-CENTER-RU

Unlocked 3 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 9, 1999 (27 years, 1 months ago)
Expires August 31, 2026 (4 months)
Name Servers ns1.ok.ru, ns2.ok.ru, ns3.ok.ru
Registrant OBShchESTVO S OGRANIChENNOY OTVETSTVENNOSTU KOMMUNIKACIONNAYa PLATFORMA
Hosting
IP Address 155.212.204.5
ASN AS47764 (VK-AS, RU)
Provider VK-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

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

Connection waterfall

DNS Lookup 69 ms TCP Connect 68 ms TLS Handshake 71 ms Server Processing 75 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback