Skip to content
https://forbes.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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.forbes.ru/
200https://forbes.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

EXPIRED

May 16, 2026

SSL certificate

278 days

Issued by GlobalSign nv-sa

Domain age

24 years, 3 months

Registered May 15, 2002

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

YANDEXCLOUD, RU

ASN AS200350

158.160.153.137

Registrar

RU-CENTER-RU

Unlocked 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created May 15, 2002 (24 years, 3 months ago)
Expires May 16, 2026 (24 days)
Name Servers ns1.yandexcloud.net, ns2.yandexcloud.net
Registrant JS "AS RUS MEDIA"
Hosting
IP Address 158.160.153.137
ASN AS200350 (YANDEXCLOUD, RU)
Provider YANDEXCLOUD, RU
Data source: whois (0.7s)

This domain expires on May 16, 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
TLS Certificate Expiry & Recommendations
278 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

278
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, 113 ms lookup
PASS
1 A records, 113 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 158.160.153.137
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: ns1.yandexcloud.net, ns2.yandexcloud.net
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: 113 ms
Got: 113 ms
A158.160.153.137
AAAA—
CNAME—
NSns1.yandexcloud.net, ns2.yandexcloud.net
MX
5 mx.yandex.net
TXT
yandex-verification: aebab198aaf74c8e
202201310452184fydqgsatwgz0dfaki4mwvqa0svu40cswdj9bydrqmhccskka4
rm_verify=d9d42927e0
_globalsign-domain-verification=KzZ1kmda1l9jGScXjPzuT4aihrsjEr1W6F_cK3PbGX
google-site-verification=2kLqxOrZDv01Jy4oNHNVooM9WeUei5k3_IslduW11fM
yandex-verification: 9500e27ac802615c
20210129213113546wiyl8qddirm5sn38wl1ayphhn4xq0iqgydf6erp8773zh8v
SPF v=spf1 ip4:5.188.161.147 ip4:91.224.182.43 include:_spf.yandex.net include:spf.u...
201901281203172yt2nylmkrrmbgpvrj47iffyyivou1lsjfrdub29vtktunv2a1
201912120917041o7awnepjdkf8xxypvpbvuxh03qvi6ok7qotgecocz7gca783u
yandex-verification: 1c472abcdbffb641
mailru-verification: 085fb278c668a61e
CAALookup not available with standard resolver
Resolved in 113 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
1 redirect(s), 803 ms total
PASS
1 redirect(s), 803 ms total
Info::
Single redirect
Got: https://forbes.ru → https://www.forbes.ru/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 803 ms total
Got: 803 ms

https://forbes.ru

223 ms · HTTP/1.1

301

https://www.forbes.ru/

580 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://forbes.ru301223 msHTTP/1.1ycalb
2https://www.forbes.ru/200580 msHTTP/1.1ycalb

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 33 URLs
PASS
robots.txt present, sitemap with 33 URLs
Info::
robots.txt is present
Got: 2164 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 33 entries
Info::
Sitemap index with 33 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2164 B Sitemaps referenced 2 User-agents YandexNews, *, Yandex Blocking No — crawling allowed
User-Agent: YandexNews
Allow: /newrss.xml

User-agent: *
Disallow: /*..*
Disallow: /*embed/
Disallow: /taxonomy/
Disallow: /searchsite/
Disallow: /nodesearch
Disallow: /explain/
Disallow: /blog/
Disallow: /amp/
Disallow: */photo/*
Disallow: /preview/*
Disallow: */slide/*
Disallow: */slideshow*
Disallow: /*.php
Disallow: /*.html
Disallow: /sobytiya/lyudi/79318-leonid-reiman-dose-svyazista
Disallow: /finansy/543439-nalogoviki-stali-po-neskol-ko-raz-vzyskivat-nedoimki-za-odno-narusenie
Disallow: /karera-i-svoy-biznes/384923-podarok-dlya-putina-zachem-vladelica-butika-christian-louboutin
Allow: *.css
Allow: *.js
Allow: *.gif
Allow: *.jpg
Allow: *.jpeg
Allow: *.png
Allow: *.svg
Allow: *.webp
Allow: *.woff
Allow: *.woff2
Allow: /ads.txt
Host: www.forbes.ru
Sitemap: https://www.forbes.ru/sitemap.xml

User-agent: Yandex
Disallow: /*..*
Disallow: /*embed/
Disallow: /taxonomy/
Disallow: /searchsite/
Disallow: /search
Disallow: /nodesearch
Disallow: /explain/
Disallow: /blog/
Disallow: /amp/
Disallow: */photo/*
Disallow: /preview/*
Disallow: */slide/*
Disallow: */slideshow*
Disallow: /*.php
Disallow: /*.html
Disallow: /sobytiya/lyudi/79318-leonid-reiman-dose-svyazista
Disallow: /finansy/543439-nalogoviki-stali-po-neskol-ko-raz-vzyskivat-nedoimki-za-odno-narusenie
Disallow: /karera-i-svoy-biznes/384923-podarok-dlya-putina-zachem-vladelica-butika-christian-louboutin
Allow: *.css
Allow: *.js
Allow: *.gif
Allow: *.jpg
Allow: *.jpeg
Allow: *.png
Allow: *.svg
Allow: *.webp
Allow: *.woff
Allow: *.woff2
Allow: /ads.txt
Clean-param: utm_source&utm_medium&utm_campaign&utm_referrer&from_rating&fbclid&page&mobile&guid&clid&id&fromtg&nw&photo&from&noredir&post&promo&s&spush&u&articleId&back&dsp_click_id&gallery&from_alt_domain&image&photoPopup&telegram&fs&ckick_id&cm_id&mibextid&amp&etext&b24form_user&bx_sender_conversion_id&utm_test&utm_follow&utm_follow_ch&mkt_tok&mindbox-message-key&search_api_views_fulltext&slide&hl&tpclid&disableGlobalInfoCollect&ref&t&clckid&utm_p&trk&sfns&utm&sfnsn&ai&calltouch_tm&source&type_sort&activity_category&geography&size_investment&payback_period&monthly_income&special_marks
Sitemap: https://www.forbes.ru/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 33 entries Valid XML Yes
Child Sitemaps:
A+
HTTP Probe Timing
Total 294 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
67 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
72 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
74 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
294 ms
Total Time Total request time from DNS lookup through full response.
294 ms

Connection waterfall

DNS Lookup 67 ms TCP Connect 72 ms TLS Handshake 74 ms Server Processing 81 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