Skip to content
https://crpt.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
3 PASS 5 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.crpt.ru/
200https://crpt.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
Domain Intelligence
crpt.ru — via RU-CENTER-RU, 15 years, 1 months old, hosted on DDOS-GUARD, RU
REVIEW
crpt.ru — via RU-CENTER-RU, 15 years, 1 months old, hosted on DDOS-GUARD, RU
Critical::
Domain expires in 24 days
This domain expires on May 11, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 11, 2026
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: DDOS-GUARD, RU
Got: AS57724
Domain expiry

EXPIRED

May 11, 2026

SSL certificate

338 days

Issued by GlobalSign nv-sa

Domain age

15 years, 1 months

Registered May 11, 2011

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DDOS-GUARD, RU

ASN AS57724

91.215.43.194

Registrar

RU-CENTER-RU

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created May 11, 2011 (15 years, 1 months ago)
Expires May 11, 2026 (24 days)
Name Servers ns3.servicepipe.ru, ns4-l2.nic.ru, ns4.servicepipe.ru, ns8-l2.nic.ru
Registrant LLC "TSENTR RAZVITIIA PERSPEKTIVNYKH TEKHNOLOGII"
Hosting
IP Address 91.215.43.194
ASN AS57724 (DDOS-GUARD, RU)
Provider DDOS-GUARD, RU
Data source: whois (0.7s)

This domain expires on May 11, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Connection waterfall

DNS Lookup 439 ms TCP Connect 12 ms TLS Handshake 16 ms Server Processing 906 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
338 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

338
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, 449 ms lookup
PASS
1 A records, 449 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 91.215.43.194
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3.servicepipe.ru, ns4.servicepipe.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
Info::
2 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
Warning::
DNS resolution is slow (449 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 449 ms
A91.215.43.194
AAAA—
CNAME—
NSns3.servicepipe.ru, ns4.servicepipe.ru, ns4-l2.nic.ru, ns8-l2.nic.ru
MX
5 mx03.crpt.ru
10 mx01.crpt.ru
TXT
SPF v=spf1 mx ip4:91.236.205.1 ip4:185.225.32.46 ip4:185.175.46.143 a:mail.onyma.ru ...
202012301942022pirciq5bzhcaonf7sheuw7aouume1kb8hk3sl7mwdqke3rkkv
202012301944014p6iite3ebfinhutc38epbw9iob2ue5t7tfwii1oxooxjiimq0
202012301945022dgloh8qxqp6uoejqg2uooxx70932uzgmosdpsokoekxizm1co
2020123019480116dgqjdn97dja8jcu43nz76q69v1xncdohuutnu9thsy4kwe6z
202012301950021p07mbkxrs4qjt1h2mlg5p3bt5hl8kr1fax5gf2q4odsv1nkey
202012301951024wrgkl90ucfo9ac79dg1q0irccvv6498tse2eoje87oufg6p9u
_globalsign-domain-verification=pzGd9pdBJpsewPxjaHHosSO0V7x1kQObcvdog1Wl_4
CAALookup not available with standard resolver
Resolved in 449 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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

https://crpt.ru

776 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://crpt.ru200776 msHTTP/1.1ddos-guard
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 0 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
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.

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 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback