Skip to content
https://narod.ru

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
116 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 86 ms lookup
PASS
1 A records, 86 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.109.246.46
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.ucoz.net, ns2.ucoz.net, ns1.ucoz.net
Info::
3 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: 86 ms
Got: 86 ms
A193.109.246.46
AAAA—
CNAME—
NSns3.ucoz.net, ns2.ucoz.net, ns1.ucoz.net
MX
10 mx2.yandex.ru
10 mx3.yandex.ru
10 mx1.yandex.ru
TXT
_globalsign-domain-verification=JRUsdpasXzISZtmMkVttYdAEq9x_rWM7zNATFv0tIC
_globalsign-domain-verification=2iMm8CN-zGSjw4ZOBEu5XxjRAKzNWqkVAoG71hSBZh
SPF v=spf1 redirect=_spf.yandex.ru
google-site-verification=7VI8d8CoYJ_xAcllGlcxGJka9DCdjR-mnmm8bSOpZd8
_globalsign-domain-verification=FBhRuohLURn12A3LZm-Sq-RXsLgtV1-LDlg535Qat5
_globalsign-domain-verification=vWofeUd8cfdyzsn-MqPxWMQ4tqstXo0P6bNSO01Vr8
CAALookup not available with standard resolver
Resolved in 86 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://narod.ru

https://narod.ru

635 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://narod.ru200635 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 1003 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 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 1003 B Sitemaps referenced 0 User-agents rogerbot, linkdexbot/2.0, Baiduspider-video, ia_archiver, SolomonoBot, AhrefsBot, dotbot, dotbot/1.1, Genieo, Baiduspider-image, *, SemrushBot, AhrefsBot/5.0, Baiduspider, MJ12bot Blocking No — crawling allowed
User-agent: ia_archiver
User-Agent: SolomonoBot
User-agent: SemrushBot
User-agent: AhrefsBot
User-agent: AhrefsBot/5.0
User-agent: MJ12bot
User-agent: dotbot
User-agent: dotbot/1.1
User-agent: rogerbot
User-agent: linkdexbot/2.0
User-agent: Genieo
User-agent: Baiduspider
User-agent: Baiduspider-video
User-agent: Baiduspider-image
Disallow: /

User-agent: *
Allow: /*.js
Allow: /*.css
Allow: /*.jpg
Allow: /*.png
Allow: /*.gif
Allow: /*?page
Allow: /*?ref=
Disallow: /*?
Disallow: /stat/
Disallow: /index/1
Disallow: /index/3
Disallow: /register
Disallow: /index/5
Disallow: /index/7
Disallow: /index/8
Disallow: /index/9
Disallow: /index/sub/
Disallow: /panel/
Disallow: /admin
Disallow: /admin/
Disallow: /informer/
Disallow: /secure/
Disallow: /poll/
Disallow: /search/
Disallow: /abnl/
Disallow: /*_escaped_fragment_=
Disallow: /*-*-*-*-987$
Disallow: /shop/order/
Disallow: /shop/printorder/
Disallow: /shop/checkout/
Disallow: /shop/user/
Disallow: /*0-*-0-17$
Disallow: /*-0-0-
Disallow: /disk/
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.narod.ru/
200https://narod.ru/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
narod.ru — via R01-RU, 26 years, 9 months old, hosted on COMPUBYTE-AS, CY
PASS
narod.ru — via R01-RU, 26 years, 9 months old, hosted on COMPUBYTE-AS, CY
Info::
Domain registered until Dec 31, 2026 (8 months remaining)
Info::
Registrar: R01-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: COMPUBYTE-AS, CY
Got: AS204343
Domain expiry

172 days

December 31, 2026

SSL certificate

116 days

Issued by GlobalSign nv-sa

Domain age

26 years, 9 months

Registered December 9, 1999

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

COMPUBYTE-AS, CY

ASN AS204343

193.109.246.46

Registrar

R01-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 R01-RU
Created December 9, 1999 (26 years, 9 months ago)
Expires December 31, 2026 (8 months)
Name Servers ns1.ucoz.net, ns2.ucoz.net, ns3.ucoz.net
Registrant LLC "Ucoz Media"
Hosting
IP Address 193.109.246.46
ASN AS204343 (COMPUBYTE-AS, CY)
Provider COMPUBYTE-AS, CY
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 600 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
86 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
111 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
249 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
599 ms
Total Time Total request time from DNS lookup through full response.
600 ms

Connection waterfall

DNS Lookup 86 ms TCP Connect 111 ms TLS Handshake 249 ms Server Processing 154 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback