Infrastructure - https://zira.uz BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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.

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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

Redirect Chain

1 redirect(s), 1269 ms total

REVIEW

1 redirect(s), 1269 ms total

Single redirect

Got: https://zira.uz → https://zira.uz/ru/ (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://zira.uz

Redirect overhead: 1269 ms total

Got: 1269 ms

https://zira.uz

440 ms · HTTP/1.1

302

https://zira.uz/ru/

829 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://zira.uz	302	440 ms	HTTP/1.1	nginx
2	https://zira.uz/ru/	200	829 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

169 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

169

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

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

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

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, 350 ms lookup

PASS

1 A records, 350 ms lookup

Resolves to 1 IPv4 address(es)

Got: 116.203.151.79

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1363.awsdns-42.org, ns-2039.awsdns-62.co.uk, ns-378.awsdns-47.com, ns-883.awsdns-46.net

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (350 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 350 ms

A	116.203.151.79
AAAA	—
CNAME	—
NS	ns-1363.awsdns-42.org, ns-2039.awsdns-62.co.uk, ns-378.awsdns-47.com, ns-883.awsdns-46.net
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com
TXT	google-site-verification=Uzp6lt6QHm8uJ43KzzTEdMAir4Eobl9S9Sa60ZzuNuk SPF v=spf1 include:servers.mcsv.net ?all
CAA	Lookup not available with standard resolver

Resolved in 350 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

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A

CAA Records

issue: digicert.com, letsencrypt.org, sectigo.com

PASS

issue: digicert.com, letsencrypt.org, sectigo.com

CAA issue tag present — authorized CA(s): digicert.com, letsencrypt.org, sectigo.com

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+

Reverse DNS

1/1 IPs match cert SAN

PASS

1/1 IPs match cert SAN

PTR for 116.203.151.79 matches certificate SAN: zira.uz

A+

Multi-Resolver DNS Speed

Mean 3ms across 3 resolvers (spread 7ms)

PASS

Mean 3ms across 3 resolvers (spread 7ms)

Quad9: 0ms

Got: 0ms via 9.9.9.9:53

Cloudflare: 3ms

Got: 3ms via 1.1.1.1:53

Google: 7ms

Got: 7ms via 8.8.8.8:53

A+

Crawlability

robots.txt present, sitemap with 9 URLs

PASS

robots.txt present, sitemap with 9 URLs

robots.txt is present

Got: 143 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 9 entries

Sitemap index with 9 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 143 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://zira.uz/sitemap.xml
Sitemap: https://zira.uz/sitemap.html

sitemap.xml 200 OK

Type Sitemap Index URLs 9 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.zira.uz/

200https://zira.uz/

Preferred variant: non-www

HTTP → HTTPS

301http://zira.uz/ → https://zira.uz/

Consistent

A+

Domain Intelligence

zira.uz — via ISP Sarkor Telecom, 9 years, 3 months old, hosted on Hetzner

PASS

zira.uz — via ISP Sarkor Telecom, 9 years, 3 months old, hosted on Hetzner

Domain registered until May 12, 2031 (4 years, 11 months remaining)

Registrar: ISP Sarkor Telecom

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.

Hosting: Hetzner

Got: AS24940

Domain expiry

1765 days

May 12, 2031

SSL certificate

169 days

Issued by Sectigo Limited

Domain age

9 years, 3 months

Registered May 10, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

116.203.151.79

Registrar

ISP Sarkor Telecom

Unlocked 4 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 ISP Sarkor Telecom

Created May 10, 2017 (9 years, 3 months ago)

Expires May 12, 2031 (4 years, 11 months)

Last Updated May 12, 2026

Name Servers ns-1363.awsdns-42.org., ns-2039.awsdns-62.co.uk., ns-883.awsdns-46.net., ns-378.awsdns-47.com.

Registrant REDACTED FOR PRIVACY

Hosting

IP Address 116.203.151.79

ASN AS24940 (HETZNER-AS - Hetzner Online GmbH, DE)

Provider Hetzner

Data source: rdap (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 443 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

133 ms

TCP Connect

94 ms

TLS Handshake

99 ms

Time to First Byte

443 ms

Total Time

443 ms

Connection waterfall

DNS Lookup 133 ms TCP Connect 94 ms TLS Handshake 99 ms Server Processing 117 ms Content Transfer 0 ms