Skip to content
https://albastor.ru

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
Multi-Resolver DNS Speed
Action
Mean 591ms across 3 resolvers (spread 1497ms)
FIX
Mean 591ms across 3 resolvers (spread 1497ms)
Info::
Google: 63ms
Got: 63ms via 8.8.8.8:53
Info::
Cloudflare: 150ms
Got: 150ms via 1.1.1.1:53
Info::
Quad9: 1560ms
Got: 1560ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 1497ms (min 63ms / max 1560ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 45.8.99.142 does not match any cert SAN: 1192731-cv37940.tw1.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.
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
Domain Intelligence
albastor.ru — via REGRU-RU, 1 years, 11 months old, hosted on TimeWeb-AS - JSC _TIMEWEB_, RU
REVIEW
albastor.ru — via REGRU-RU, 1 years, 11 months old, hosted on TimeWeb-AS - JSC _TIMEWEB_, RU
Critical::
Domain expires in 29 days
This domain expires on December 15, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires Dec 15, 2026
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

22 days

December 15, 2026

SSL certificate

41 days

Issued by Let's Encrypt

Domain age

1 years, 11 months

Registered December 15, 2024

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

TimeWeb-AS - JSC _TIMEWEB_, RU

ASN AS9123

45.8.99.142

Registrar

REGRU-RU

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar REGRU-RU
Created December 15, 2024 (1 years, 11 months ago)
Expires December 15, 2026 (29 days)
Name Servers ns1.kzla.ru, ns2.kzla.ru
Hosting
IP Address 45.8.99.142
ASN AS9123 (TimeWeb-AS - JSC _TIMEWEB_, RU)
Provider TimeWeb-AS - JSC _TIMEWEB_, RU
Data source: whois (1.0s)

This domain expires on December 15, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

41
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
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 104 ms lookup
PASS
1 A records, 104 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 45.8.99.142
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.kzla.ru, ns2.kzla.ru
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 104 ms
Got: 104 ms
A45.8.99.142
AAAA—
CNAME—
NSns1.kzla.ru, ns2.kzla.ru
MX
0 mail.albastor.ru
TXT
mailruverify
SPF v=spf1 a mx ip4:45.8.99.142 -all
CAALookup not available with standard resolver
Resolved in 104 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
CAA Records
issue: letsencrypt.org
PASS
issue: letsencrypt.org
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://albastor.ru

https://albastor.ru

519 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://albastor.ru200519 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 44 URLs
PASS
robots.txt present, sitemap with 44 URLs
Info::
robots.txt is present
Got: 2052 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 44 entries
Info::
Sitemap index with 44 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2052 B Sitemaps referenced 1 User-agents *, Yandex, bingbot Blocking No — crawling allowed
# Основные правила для всех поисковых систем

User-agent: *

Disallow: /js/modules/EOKit/
Disallow: /admin/

Disallow: /administrator/

Disallow: /backend/

Disallow: /cp/

Disallow: /control/

Disallow: /panel/

Disallow: /login/

Disallow: /auth/

Disallow: /user/

Disallow: /account/

Disallow: /cache/

Disallow: /caches/

Disallow: /tmp/

Disallow: /temp/

Disallow: /logs/

Disallow: /backup/

Disallow: /backups/

Disallow: /sql/

Disallow: /database/

Disallow: /cart/

Disallow: /basket/

Disallow: /checkout/

Disallow: /order/

Disallow: /personal/

Disallow: /profile/

Disallow: /search/

Disallow: /bc/

Disallow: /system/

Disallow: /registration/

Disallow: /favorites/

Disallow: /uslugi/


# Запрет страниц с техническими параметрами (предотвращение дублей)

Disallow: /*?sort=

Disallow: /*&sort=

Disallow: /*?order=

Disallow: /*&order=

Disallow: /*?filter=

Disallow: /*&filter=

Disallow: /*?mode=

Disallow: /*&mode=

Disallow: /*?view=

Disallow: /*&view=

Disallow: /*?curPos=

Disallow: /*&curPos=

Disallow: /*?cur_cc=

Disallow: /*&cur_cc=

Disallow: /*?isNaked=

Disallow: /*&isNaked=

Disallow: /*?etext=

Disallow: /*&etext=

Disallow: /*?ybaip=

Disallow: /*&ybaip=

Disallow: /*?gtm_latency=

Disallow: /*>m_latency=

Disallow: /*?nc_ctpl=

Disallow: /*&nc_ctpl=

Disallow: /*?_ym_status-check=

Disallow: /*&_ym_status-check=

Disallow: /*?_ym_lang=

Disallow: /*&_ym_lang=


# Явные разрешения для важных разделов

Allow: /*/catalog/

Allow: /*mobile$


# Указание карты сайта и основного зеркала (для Яндекса)

Sitemap: https://albastor.ru/sitemap.xml

Host: https://albastor.ru

# Индивидуальные настройки для Яндекса (задержка между запросами)

User-agent: Yandex

Crawl-delay: 1

# Индивидуальные настройки для Bing

User-agent: bingbot

Crawl-delay: 1
sitemap.xml 200 OK
Type Sitemap Index URLs 44 entries Valid XML Yes
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A
HTTP Probe Timing
Total 654 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.
57 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
124 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
596 ms
Total Time Total request time from DNS lookup through full response.
654 ms

Connection waterfall

DNS Lookup 109 ms TCP Connect 57 ms TLS Handshake 124 ms Server Processing 306 ms Content Transfer 58 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback