Skip to content
https://zadelrf.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
7 PASS 9 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.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 185.225.34.23: lookup 185.225.34.23: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
HTTP Probe Timing
Action
Total 1566 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
246 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
250 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
254 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.00 s
Total Time Total request time from DNS lookup through full response.
1.57 s

Connection waterfall

DNS Lookup 246 ms TCP Connect 250 ms TLS Handshake 254 ms Server Processing 254 ms Content Transfer 563 ms
B
TLS Certificate Expiry & Recommendations
78 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 250 ms lookup
PASS
1 A records, 250 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.225.34.23
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: dns1.yandex.net, dns2.yandex.net
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (250 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 250 ms
A185.225.34.23
AAAA—
CNAME—
NSdns1.yandex.net, dns2.yandex.net
MX
10 mx.yandex.net
TXT
yandex-verification: b04cfe27eb45ac78
SPF v=spf1 ip4:109.68.191.28 ip4:185.225.34.23 include:spf.unisender.com include:_sp...
mailru-verification: 9dfcd4654e0ae5b1
CAALookup not available with standard resolver
Resolved in 250 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

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 2ms across 3 resolvers (spread 3ms)
PASS
Mean 2ms across 3 resolvers (spread 3ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 2ms
Got: 2ms via 1.1.1.1:53
Info::
Google: 4ms
Got: 4ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://zadelrf.ru

https://zadelrf.ru

247 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://zadelrf.ru200247 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 164 URLs
PASS
robots.txt present, sitemap with 164 URLs
Info::
robots.txt is present
Got: 3259 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 164 entries
Info::
Sitemap index with 164 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3259 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *                   
Disallow: /cgi-bin             
Disallow: /wp-admin/            
Allow: /wp-admin/admin-ajax.php 
Disallow: /?                    
Disallow: *?s=                  
Disallow: *&s=                  
Disallow: /search               
Disallow: /author/              
Disallow: */embed$              
Disallow: */xmlrpc.php          
Disallow: *utm*=                
Disallow: *openstat=            
Disallow: *ybaip*
Disallow: /ybaip
Clean-param: _wpnonce
Clean-param: utm
Clean-param: ysclid
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_filter_kol-vo-kulachkov=2&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_filter_diametr-mm=250&wpf_count=24&wpf_fbv=1
Allow: /category/frezernaya-osnastka/povorotnye-stoly/?wpf_count=24&wpf_fbv=1&wpf_filter_proizvoditel=detron
Allow: /category/frezernaya-osnastka/povorotnye-stoly/?wpf_count=24&wpf_fbv=1&wpf_filter_proizvoditel=tjr
Allow: /category/frezernaya-osnastka/povorotnye-stoly/?wpf_count=24&wpf_fbv=1&wpf_filter_proizvoditel=gsa
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=300
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_kol-vo-kulachkov=3
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_kol-vo-kulachkov=4
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=100
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=125
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=200
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=300
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=400
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=500
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=315
Allow: /category/tokarnaja-osnastka/tokarnye-patrony/?wpf_count=24&wpf_fbv=1&wpf_filter_diametr-mm=80
Allow: /category/tokarnaja-osnastka/barfidery/?wpf_filter_proizvoditel=fedek&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/barfidery/?wpf_filter_proizvoditel=barload&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_filter_standart-hvostovika=bmt&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_filter_naznachenie-bmt=65&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_filter_privodnaya-mufta=5480&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_count=24&wpf_fbv=1&wpf_filter_naznachenie-bmt=55
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_count=24&wpf_fbv=1&wpf_filter_standart-hvostovika=vdi
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?w&wpf_filter_tiporazmer-hvostovika=30&wpf_count=24&wpf_fbv=1
Allow: /category/tokarnaja-osnastka/privodnye-bloki/?wpf_filter_tiporazmer-hvostovika=40&wpf_count=24&wpf_fbv=1

 
Sitemap: http://zadelrf.ru/sitemap_index.xml
Sitemap: https://zadelrf.ru/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 164 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.zadelrf.ru/
200https://zadelrf.ru/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
zadelrf.ru — via RU-CENTER-RU, 12 years, 10 months old, hosted on BEGET-AS - Beget LLC, RU
PASS
zadelrf.ru — via RU-CENTER-RU, 12 years, 10 months old, hosted on BEGET-AS - Beget LLC, RU
Info::
Domain registered until Oct 3, 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: BEGET-AS - Beget LLC, RU
Got: AS198610
Domain expiry

119 days

October 3, 2026

SSL certificate

78 days

Issued by Let's Encrypt

Domain age

12 years, 10 months

Registered October 3, 2013

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BEGET-AS - Beget LLC, RU

ASN AS198610

185.225.34.23

Registrar

RU-CENTER-RU

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created October 3, 2013 (12 years, 10 months ago)
Expires October 3, 2026 (3 months)
Name Servers dns1.yandex.net, dns2.yandex.net
Registrant Obshchestvo s ogranichennoj otvetstvennostyu "ZADEL"
Hosting
IP Address 185.225.34.23
ASN AS198610 (BEGET-AS - Beget LLC, RU)
Provider BEGET-AS - Beget LLC, RU
Data source: whois (1.2s)

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