Skip to content
https://yadi.sk

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1611 ms total
FIX
3 redirect(s), 1611 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://yadi.sk
Warning::
Redirect overhead: 1611 ms total
Got: 1611 ms
Info::
Cross-domain redirect detected

https://yadi.sk

263 ms · HTTP/1.1

302

https://disk.yandex.fr

344 ms · HTTP/1.1

301

https://disk.yandex.ru/

280 ms · HTTP/1.1

302

https://360.yandex.ru/disk/

724 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yadi.sk302263 msHTTP/1.1
2https://disk.yandex.fr301344 msHTTP/1.1
3https://disk.yandex.ru/302280 msHTTP/1.1
4https://360.yandex.ru/disk/200724 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 677 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 677 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /pay/
Allow: /pay/tariffs/
Disallow: /activation_failed
Disallow: /cfg
Disallow: /folder
Disallow: /copy
Disallow: /download/Yandex.Disk.Mac.dmg
Disallow: /download/YandexDiskSetup.exe
Disallow: /download/YandexDiskSetupPack.exe
Disallow: /client/
Disallow: /models/
Disallow: /tuning/
Disallow: /gift
Disallow: /payment/
Disallow: /ping
Disallow: /monitoring.txt
Disallow: /public
Disallow: /a/
Disallow: /d/
Disallow: /i/
Disallow: /mail
Disallow: /edit/
Disallow: /auth/
Disallow: /version/
Disallow: /search-app/
Disallow: /public3/
Disallow: /error/
Disallow: /auth.html

Clean-param: from&utm_source&utm_medium&utm_campaign&get&turbo&src

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
151 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

151
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, 65 ms lookup
PASS
1 A records, 65 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 87.250.250.50
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a02:6b8::2:50
Info::
2 nameserver(s) configured
Got: ns3.yandex.ru, ns4.yandex.ru
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 65 ms
Got: 65 ms
A87.250.250.50
AAAA2a02:6b8::2:50
CNAME
NSns3.yandex.ru, ns4.yandex.ru
MX
TXT
_globalsign-domain-verification=J9y0JvfB-kygkZGzfkpNnO5cF1NunJhC6Vhbukh0iC
45e3b7565dc5130458f2bead528f8f6000d78f2b5fd904b06355c19f0cd3e4f
96ecd6928cf6313019cf2d11dc11d6fa945e5d808fcd391ce076bcd6968aa39
CAALookup not available with standard resolver
Resolved in 65 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
IPv6 Readiness
IPv6 reachable (69 ms)
PASS
IPv6 reachable (69 ms)
Info::
IPv6 is configured and reachable at 2a02:6b8::2:50
Got: 69 ms connect
IPv6 Ready
AAAA Records 2a02:6b8::2:50 Connection Reachable (69 ms)
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

302https://www.yadi.sk/
200https://yadi.sk/

Preferred variant: non-www

HTTP → HTTPS

301http://yadi.sk/ https://yadi.sk/

Consistent

A
Domain Intelligence
yadi.sk — via Safenames Ltd, 14 years old
PASS
yadi.sk — via Safenames Ltd, 14 years old
Warning::
Domain expires in 66 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 27, 2026
Info::
Registrar: Safenames Ltd
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

EXPIRED

June 27, 2026

SSL certificate

151 days

Issued by GlobalSign nv-sa

Domain age

14 years

Registered June 27, 2012

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a02:6b8::2:50

Registrar

Safenames Ltd

Locked 2 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
Registrar Safenames Ltd
Created June 27, 2012 (14 years ago)
Expires June 27, 2026 (2 months)
Last Updated June 19, 2025
Name Servers ns3.yandex.ru, ns4.yandex.ru
Registrant YANDEX LLC.
Hosting
IP Address 2a02:6b8::2:50
Data source: whois (0.6s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

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

Source: ICANN renewal policy

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 315 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
71 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
70 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
73 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
316 ms
Total Time Total request time from DNS lookup through full response.
316 ms

Connection waterfall

DNS Lookup 71 ms TCP Connect 70 ms TLS Handshake 73 ms Server Processing 101 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