Skip to content
https://1tv.ru

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
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 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 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.1tv.ru/
200https://1tv.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://1tv.ru/ → http://www.1tv.ru/

HTTP version does not redirect to HTTPS

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
TLS Certificate Expiry & Recommendations
122 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

122
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, 76 ms lookup
PASS
1 A records, 76 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 178.248.233.188
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns-q1.1tv.ru, ns1.edgedns.ru, ns4-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
Info::
DNS resolution time: 76 ms
Got: 76 ms
A178.248.233.188
AAAA—
CNAME—
NSns-q1.1tv.ru, ns1.edgedns.ru, ns4-l2.nic.ru
MX
10 mail3.1tv.ru
20 mail2.1tv.ru
TXT
SPF v=spf1 ip4:95.167.219.139 ip4:81.211.33.239 ip4:81.177.156.239 ~all
_globalsign-domain-verification=rqtEAGUBWOt_owZ3QIn7m6dKcy1rPIPQFsK_x7ErQ0
yandex-verification: a9badaac31c9061c
_globalsign-domain-verification=sNSY24k3JB4IjDl9wUvB23o9283W_C1x-jvtJuDQmP
_globalsign-domain-verification=z7dTxxm34vxCb4_E2igAIaAzqeHy2LE2h40hOmBM48
CAALookup not available with standard resolver
Resolved in 76 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), 608 ms total
PASS
1 redirect(s), 608 ms total
Info::
Single redirect
Got: https://1tv.ru → https://www.1tv.ru/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 608 ms total
Got: 608 ms

https://1tv.ru

252 ms · HTTP/1.1

301

https://www.1tv.ru/

355 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://1tv.ru301252 msHTTP/1.1QRATOR
2https://www.1tv.ru/200355 msHTTP/1.1QRATOR

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 639 URLs
PASS
robots.txt present, sitemap with 639 URLs
Info::
robots.txt is present
Got: 234 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 639 entries
Info::
Sitemap index with 639 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 234 B Sitemaps referenced 0 User-agents *, Yandex Blocking No — crawling allowed
User-agent: *
Crawl-delay: 1
Host: https://www.1tv.ru
Disallow: /free
Disallow: /profile
Disallow: /profile/
Disallow: /search
Disallow: /search/

User-agent: Yandex
Allow: /news/index_for_ya.rss
Allow: /yandex_zen.rss
Crawl-delay: 1
sitemap.xml 200 OK
Type Sitemap Index URLs 639 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
1tv.ru — via RU-CENTER-RU, 24 years old, hosted on HLL-AS, RU
PASS
1tv.ru — via RU-CENTER-RU, 24 years old, hosted on HLL-AS, RU
Info::
Domain registered until Jul 29, 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: HLL-AS, RU
Got: AS51115
Domain expiry

EXPIRED

July 29, 2026

SSL certificate

122 days

Issued by GlobalSign nv-sa

Domain age

24 years

Registered July 28, 2002

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

HLL-AS, RU

ASN AS51115

178.248.233.188

Registrar

RU-CENTER-RU

Unlocked 3 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 July 28, 2002 (24 years ago)
Expires July 29, 2026 (3 months)
Name Servers ns1.edgedns.ru, ns4-l2.nic.ru, ns-q1.1tv.ru
Registrant Joint stock company "First channel"
Hosting
IP Address 178.248.233.188
ASN AS51115 (HLL-AS, RU)
Provider HLL-AS, RU
Data source: whois (0.9s)

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

Connection waterfall

DNS Lookup 109 ms TCP Connect 29 ms TLS Handshake 35 ms Server Processing 200 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