Skip to content
https://key-hub.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 10 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 85.193.80.103 does not match any cert SAN: server.key-hub.ru
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 109ms across 3 resolvers (spread 97ms)
REVIEW
Mean 109ms across 3 resolvers (spread 97ms)
Info::
Google: 64ms
Got: 64ms via 8.8.8.8:53
Info::
Cloudflare: 102ms
Got: 102ms via 1.1.1.1:53
Info::
Quad9: 161ms
Got: 161ms via 9.9.9.9:53
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

C
TLS Certificate Expiry & Recommendations
Action
26 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

26
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 26 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
C
CDN & Delivery
Action
Assets on Cloudflare (host unpkg.com, 3 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host unpkg.com, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (unpkg.com, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: cf-ray: a3c96f9bfd33d093-CDG
Info::
Assets on Cloudflare: unpkg.com (assets: 3), cache HIT
Got: cf-ray: a3c96f9bfd33d093-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • unpkg.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • fonts.googleapis.com — assets: 4 · Google
  • chat.key-hub.ru — assets: 1 · below probe threshold
  • mc.yandex.com — assets: 1 · below probe threshold
  • mc.yandex.ru — assets: 1 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
1 A records, 70 ms lookup
PASS
1 A records, 70 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 85.193.80.103
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns4.timeweb.org, ns2.timeweb.ru, ns1.timeweb.ru, ns3.timeweb.org
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 70 ms
Got: 70 ms
A85.193.80.103
AAAA—
CNAME—
NSns4.timeweb.org, ns2.timeweb.ru, ns1.timeweb.ru, ns3.timeweb.org
MX
10 server.key-hub.ru
TXT
google-site-verification=uR6eoJ5Ld3PMhCpSyVPy_Rud_KgfE1LDa-EsCYNQaXQ
SPF v=spf1 ip4:85.193.80.103 -all
CAALookup not available with standard resolver
Resolved in 70 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://key-hub.ru

https://key-hub.ru

692 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://key-hub.ru200692 msHTTP/1.1LiteSpeed
A+
Crawlability
robots.txt present, sitemap with 13 URLs
PASS
robots.txt present, sitemap with 13 URLs
Info::
robots.txt is present
Got: 603 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 13 entries
Info::
Sitemap index with 13 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 603 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Disallow: /wp-login.php

Disallow: /cart/

Disallow: /checkout/

Disallow: /my-account/


Disallow: /?s=

Disallow: /*?add-to-cart=

Disallow: /*?orderby=

Disallow: /*?filter_

Disallow: /*?min_price=

Disallow: /*?max_price=


Disallow: */feed/

Disallow: */comments/

Disallow: /author/


Disallow: /wp-content/uploads/wc-logs/

Disallow: /wp-content/uploads/woocommerce_transient_files/

Disallow: /wp-content/uploads/woocommerce_uploads/


Allow: /wp-admin/admin-ajax.php


Sitemap: https://key-hub.ru/wp-sitemap.xml

Host: key-hub.ru
Clean-param: etext /
sitemap.xml 200 OK
Type Sitemap Index URLs 13 entries Valid XML Yes
Child Sitemaps:
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

https://www.key-hub.ru/
200https://key-hub.ru/

HTTP → HTTPS

302http://key-hub.ru/ → https://key-hub.ru/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
key-hub.ru — via REGRU-RU, 3 years, 2 months old, hosted on TimeWeb-AS - JSC _TIMEWEB_, RU
PASS
key-hub.ru — via REGRU-RU, 3 years, 2 months old, hosted on TimeWeb-AS - JSC _TIMEWEB_, RU
Info::
Domain registered until Jul 17, 2027 (10 months remaining)
Info::
Registrar: REGRU-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: TimeWeb-AS - JSC _TIMEWEB_, RU
Got: AS9123
Domain expiry

300 days

July 17, 2027

SSL certificate

26 days

Issued by Let's Encrypt

Domain age

3 years, 2 months

Registered July 17, 2023

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

TimeWeb-AS - JSC _TIMEWEB_, RU

ASN AS9123

85.193.80.103

Registrar

REGRU-RU

Unlocked 4 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 REGRU-RU
Created July 17, 2023 (3 years, 2 months ago)
Expires July 17, 2027 (10 months)
Name Servers ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org
Hosting
IP Address 85.193.80.103
ASN AS9123 (TimeWeb-AS - JSC _TIMEWEB_, RU)
Provider TimeWeb-AS - JSC _TIMEWEB_, RU
Data source: whois (0.7s)

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

Connection waterfall

DNS Lookup 112 ms TCP Connect 89 ms TLS Handshake 92 ms Server Processing 91 ms Content Transfer 183 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback