Skip to content
https://rt.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://rt.com/ → https://rt.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 175 ms lookup
PASS
1 A records, 175 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 91.215.41.4
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru, ens-a.rttv.ru, ens-k.rttv.ru
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: 175 ms
Got: 175 ms
A91.215.41.4
AAAA—
CNAME—
NSens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru, ens-a.rttv.ru, ens-k.rttv.ru
MX
10 mx.yandex.net
TXT
google-site-verification=WQjoV9sBpeuI20b2jwEoXYRcxCSUnexj6gCdSNdN9rs
yandex-verification: 952c89f52932efa3
SPF v=spf1 redirect=_spf.yandex.net
CAALookup not available with standard resolver
Resolved in 175 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), 528 ms total
PASS
1 redirect(s), 528 ms total
Info::
Single redirect
Got: https://rt.com → https://www.rt.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 528 ms total
Got: 528 ms

https://rt.com

137 ms · HTTP/1.1

301

https://www.rt.com/

391 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rt.com301137 msHTTP/1.1ddos-guard
2https://www.rt.com/200391 msHTTP/1.1ddos-guard

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 22 URLs
PASS
robots.txt present, sitemap with 22 URLs
Info::
robots.txt is present
Got: 1289 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 22 entries
Info::
Sitemap index with 22 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1289 B Sitemaps referenced 2 User-agents Googlebot, bingbot, * Blocking No — crawling allowed
User-agent: Googlebot
Disallow: /search*
Disallow: /preview*
Disallow: /register*
Disallow: /login*
Disallow: /requestresetpass*
Disallow: /*/video/
Disallow: /shortcode/
Disallow: /preview/
Disallow: /api/
Disallow: /rtmobile/
Disallow: /listing/
Disallow: /widget/
Disallow: /schedulejson/
Disallow: /vote/
Disallow: /russia-today
Disallow: /russia-today/
Disallow: *?
Allow: /static/fonts/icon/
Allow: /static/css/
Allow: /static/js/

User-agent: bingbot
Disallow: /search*
Disallow: /preview*
Disallow: /register*
Disallow: /login*
Disallow: /requestresetpass*
Disallow: /*/video/
Disallow: /shortcode/
Disallow: /preview/
Disallow: /api/
Disallow: /rtmobile/
Disallow: /listing/
Disallow: /widget/
Disallow: /schedulejson/
Disallow: /vote/
Disallow: *?
Allow: /static/fonts/icon/
Allow: /static/css/
Allow: /static/js/

User-agent: *
Disallow: /search*
Disallow: /preview*
Disallow: /register*
Disallow: /login*
Disallow: /requestresetpass*
Disallow: /*/video/
Disallow: /shortcode/
Disallow: /preview/
Disallow: /api/
Disallow: /rtmobile/
Disallow: /listing/
Disallow: /widget/
Disallow: /schedulejson/
Disallow: /vote/
Disallow: *?
Allow: /static/fonts/icon/
Allow: /static/css/
Allow: /static/js/

Sitemap: https://www.rt.com/sitemap.xml
Sitemap: https://www.rt.com/newssitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 22 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
rt.com — via Regional Network Information Center, JSC dba RU-CENTER, 35 years old, hosted on DDOS-GUARD, RU
PASS
rt.com — via Regional Network Information Center, JSC dba RU-CENTER, 35 years old, hosted on DDOS-GUARD, RU
Info::
Domain registered until Sep 22, 2026 (5 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Regional Network Information Center, JSC dba RU-CENTER
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

100 days

September 22, 2026

SSL certificate

53 days

Issued by Let's Encrypt

Domain age

35 years

Registered September 23, 1991

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DDOS-GUARD, RU

ASN AS57724

91.215.41.4

Registrar

Regional Network Information Center, JSC dba RU-CENTER

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Regional Network Information Center, JSC dba RU-CENTER
Created September 23, 1991 (35 years ago)
Expires September 22, 2026 (5 months)
Last Updated September 25, 2025
Name Servers ens-a.rttv.ru, ens-k.rttv.ru, ens-u.rttv.ru, ns1.rttv.ru, ns2.rttv.ru
DNSSEC Not enabled
Hosting
IP Address 91.215.41.4
ASN AS57724 (DDOS-GUARD, RU)
Provider DDOS-GUARD, RU
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 159 ms TCP Connect 30 ms TLS Handshake 33 ms Server Processing 73 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