Skip to content
https://ntv.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from Santa Clara, United States
308 Permanent Redirect
Checks
9
4 PASS 2 REVIEW 3 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 308 Expected: 301 redirect to HTTPS

www / non-www

200https://www.ntv.ru/
200https://ntv.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://ntv.ru/ → http://www.ntv.ru

HTTP version does not redirect to HTTPS

D
TLS Certificate Expiry & Recommendations
Action
13 days until leaf cert expires — 4 issues to address
FIX

Certificate validity

13
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 13 days remaining
  • 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
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
Redirect Chain
1 redirect(s), 1584 ms total
REVIEW
1 redirect(s), 1584 ms total
Info::
Single redirect
Got: https://ntv.ru → https://www.ntv.ru (308)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1584 ms total
Got: 1584 ms

https://ntv.ru

736 ms · HTTP/1.1

308

https://www.ntv.ru

849 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ntv.ru308736 msHTTP/1.1
2https://www.ntv.ru200849 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

A
DNS Records
2 A records, 356 ms lookup
PASS
2 A records, 356 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 185.129.100.166, 185.129.100.162
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns7.ntv.ru, ns8.ntv.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 (356 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 356 ms
A185.129.100.166, 185.129.100.162
AAAA—
CNAME—
NSns7.ntv.ru, ns8.ntv.ru
MX
20 kmx3.ntv.ru
20 kmx2.ntv.ru
TXT
globalsign-domain-verification=nH8IulQrEEKIz-hJtse5dTSNQRA1gZ6Ia7_Aw_5kTf
MS=ms27674064
ku//pjQsaxYlZd75lCQqj3N3mVbRpgt5Vx+YlyYruJ8CiJLY8f4/XdfTMTraSAuZinT/0OYLO5/fgYD0...
globalsign-domain-verification=gQB4AGTczRQkni3-BS_bbhm4RyzSe0j-DlnRAh3n-O
String: abgsfetd9845nnf900
d750d73e-c3fd-42fb-adf0-ae2e559685a0
yandex-verification: 847f9c4f6d1da5e1
google-site-verification=k-0xYlEfnU4U9-nydXj1eYCC_2ErulCcKvTv3wMlfx4
globalsign-domain-verification=HY1EPqeDU48OGI-ziHcvxZyRXElKY-eN1cSPkjyoU3
globalsign-domain-verification=s_PfrHWgUpgptiLlPSTXBvKpbwO88CEV-5Tf9KVmV5
SPF v=spf1 ip4:195.3.240.0/22 ip4:195.46.176.103 ip4:185.129.100.135 -all
google-site-verification=nsg4d0tBBCW2qMgCRkv1xJZHxKt-KnbYPkJo8Qj5cNo
CAALookup not available with standard resolver
Resolved in 356 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.

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+
Crawlability
robots.txt present, sitemap with 3080 URLs
PASS
robots.txt present, sitemap with 3080 URLs
Info::
robots.txt is present
Got: 959 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3080 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 959 B Sitemaps referenced 1 User-agents TelegramBot, Yandex, *, trendkite-akashic-crawler, PetalBot Blocking No — crawling allowed
User-agent: TelegramBot
Disallow: /video
Disallow: /embed
Disallow: /login
Disallow: /search
Disallow: /forms
Disallow: /ntv
Disallow: /finder
Disallow: /private


User-agent: Yandex
Disallow: /embed
Disallow: /login
Disallow: /search
Disallow: /forms
Disallow: /ntv
Disallow: /finder
Disallow: /private
Disallow: /*/photogal/*
Disallow: /sobytie
Disallow: */comments
Disallow: */vcomments
Disallow: /video/embed
Disallow: /rest/
Clean-param: __twitter_impression&__ref&from&amp_lite&autoplay&ap&nid&cid&fi&pi&_gl&ref&id&mailru&og&link&ref&tv&rel&wmode

User-agent: *
Disallow: /login
Disallow: /video/embed/*
Disallow: /search
Disallow: /forms
Disallow: /ntv
Disallow: /finder
Disallow: /private
Disallow: /rest
Disallow: /foto
Disallow: */comments
Disallow: */vcomments
Disallow: /sobytie

User-agent: trendkite-akashic-crawler
Disallow: /

User-agent: PetalBot
Disallow: /

Host: https://www.ntv.ru/
Sitemap: https://www.ntv.ru/exp/yandex/sitemap_last.jsp
sitemap.xml 200 OK
Type URL Set URLs 3080 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ntv.ru — via RU-CENTER-RU, 29 years, 8 months old, hosted on DDOS-GUARD, RU
PASS
ntv.ru — via RU-CENTER-RU, 29 years, 8 months old, hosted on DDOS-GUARD, RU
Info::
Domain registered until Jan 31, 2027 (9 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: DDOS-GUARD, RU
Got: AS57724
Domain expiry

230 days

January 31, 2027

SSL certificate

13 days

Issued by GlobalSign nv-sa

Domain age

29 years, 8 months

Registered January 7, 1997

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DDOS-GUARD, RU

ASN AS57724

185.129.100.162

Registrar

RU-CENTER-RU

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created January 7, 1997 (29 years, 8 months ago)
Expires January 31, 2027 (9 months)
Name Servers ns7.ntv.ru, ns8.ntv.ru
Registrant JS "TELEKOMPANIIA NTV"
Hosting
IP Address 185.129.100.162
ASN AS57724 (DDOS-GUARD, RU)
Provider DDOS-GUARD, 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 736 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
184 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
182 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
187 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
737 ms
Total Time Total request time from DNS lookup through full response.
737 ms

Connection waterfall

DNS Lookup 184 ms TCP Connect 182 ms TLS Handshake 187 ms Server Processing 182 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