Skip to content
https://tomsk.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 2 REVIEW 3 FIX
D
Redirect Chain
Action
2 redirect(s), 2611 ms total
FIX
2 redirect(s), 2611 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://tomsk.ru to https://www.tomsk.ru/
Warning::
Redirect overhead: 2611 ms total
Got: 2611 ms

https://tomsk.ru

974 ms · HTTP/1.1

301

http://www.tomsk.ru/

877 ms · HTTP/1.1

301

https://www.tomsk.ru/

759 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tomsk.ru301974 msHTTP/1.1nginx
2http://www.tomsk.ru/301877 msHTTP/1.1nginx
3https://www.tomsk.ru/200759 msHTTP/1.1nginx

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

Redirect directly from https://tomsk.ru to https://www.tomsk.ru/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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.tomsk.ru/
200https://tomsk.ru/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tomsk.ru/ → http://www.tomsk.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
83 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

83
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, 441 ms lookup
PASS
1 A records, 441 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 45.9.43.249
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: ns3.tomsk.ru, ns1.tomsk.ru, ns2.tomsk.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
Warning::
DNS resolution is slow (441 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 441 ms
A45.9.43.249
AAAA—
CNAME—
NSns3.tomsk.ru, ns1.tomsk.ru, ns2.tomsk.ru
MX
10 mail.tomsk.ru
TXT
SPF v=spf1 a mx ?all
CAALookup not available with standard resolver
Resolved in 441 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.

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 276 URLs
PASS
robots.txt present, sitemap with 276 URLs
Info::
robots.txt is present
Got: 412 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 276 entries
Info::
Sitemap index with 276 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 412 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin

Disallow: /wp-includes

Disallow: /wp-content/plugins

Disallow: /wp-content/cache

Disallow: /wp-json/

Disallow: /xmlrpc.php

Disallow: /readme.html

Disallow: /*?*

Disallow: /?s=

Allow: /wp-includes/*.css

Allow: /wp-includes/*.js

Allow: /wp-content/plugins/*.css

Allow: /wp-content/plugins/*.js

Allow: /*.css

Allow: /*.js


Sitemap: https://www.tomsk.ru/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 276 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
tomsk.ru — via RU-CENTER-RU, 28 years, 10 months old, hosted on BEGET-AS, RU
PASS
tomsk.ru — via RU-CENTER-RU, 28 years, 10 months old, hosted on BEGET-AS, RU
Info::
Domain registered until Oct 31, 2026 (6 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: BEGET-AS, RU
Got: AS198610
Domain expiry

140 days

October 31, 2026

SSL certificate

83 days

Issued by Let's Encrypt

Domain age

28 years, 10 months

Registered October 25, 1997

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

BEGET-AS, RU

ASN AS198610

45.9.43.249

Registrar

RU-CENTER-RU

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar RU-CENTER-RU
Created October 25, 1997 (28 years, 10 months ago)
Expires October 31, 2026 (6 months)
Name Servers ns1.tomsk.ru, ns2.tomsk.ru, ns3.tomsk.ru
Registrant LLC "Digest TV"
Hosting
IP Address 45.9.43.249
ASN AS198610 (BEGET-AS, RU)
Provider BEGET-AS, 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 762 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
218 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
180 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
182 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
762 ms
Total Time Total request time from DNS lookup through full response.
762 ms

Connection waterfall

DNS Lookup 218 ms TCP Connect 180 ms TLS Handshake 182 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