Infrastructure - https://www.weston.com.ua BeaverCheck Audit

D

Multi-Resolver DNS Speed

Action

Mean 211ms across 3 resolvers (spread 574ms)

FIX

Mean 211ms across 3 resolvers (spread 574ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 57ms

Got: 57ms via 8.8.8.8:53

Cloudflare: 575ms

Got: 575ms via 1.1.1.1:53

High latency spread between resolvers: 574ms (min 1ms / max 575ms)

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

HTTP Probe Timing

Action

Total 2028 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

FIX

DNS Lookup

41 ms

TCP Connect

54 ms

TLS Handshake

58 ms

Time to First Byte

1.97 s

Total Time

2.03 s

Connection waterfall

DNS Lookup 41 ms TCP Connect 54 ms TLS Handshake 58 ms Server Processing 1.82 s Content Transfer 55 ms

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

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 185.68.16.92 does not match any cert SAN: proxy-2.default-host.net

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.

PTR for 2a00:7a60:0:105c::1 does not match any cert SAN: proxy-2.default-host.net

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

TLS Certificate Expiry & Recommendations

88 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

88

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
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: 508, /health: 508, /healthz: 508, /ping: 508, /status: 508.

A

DNS Records

1 A records, 60 ms lookup

PASS

1 A records, 60 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.68.16.92

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a00:7a60:0:105c::1

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 60 ms

Got: 60 ms

A	185.68.16.92
AAAA	2a00:7a60:0:105c::1
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.weston.com.ua

https://www.weston.com.ua

3274 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.weston.com.ua	200	3274 ms	HTTP/1.1	nginx

A+

IPv6 Readiness

IPv6 reachable (57 ms)

PASS

IPv6 reachable (57 ms)

IPv6 is configured and reachable at 2a00:7a60:0:105c::1

Got: 57 ms connect

IPv6 Ready

AAAA Records 2a00:7a60:0:105c::1 Connection Reachable (57 ms)

A+

Crawlability

robots.txt present, sitemap with 25 URLs

PASS

robots.txt present, sitemap with 25 URLs

robots.txt is present

Got: 1214 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 25 entries

robots.txt references sitemap

robots.txt 200 OK

Size 1214 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

# If the Joomla site is installed within a folder 
# eg www.example.com/joomla/ then the robots.txt file 
# MUST be moved to the site root 
# eg www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to all of the
# paths. 
# eg the Disallow rule for the /administrator/ folder MUST 
# be changed to read 
# Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/orig.html
#
# For syntax checking, see:
# http://tool.motoricerca.info/robots-checker.phtml

User-agent: *
Disallow: /administrator/
Disallow: /bin/
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /layouts/
Disallow: /libraries/
Disallow: /logs/
Disallow: /modules/
Disallow: /plugins/
Disallow: /tmp/
Disallow: /ba-click-lightbox-form-9/
Disallow: /ba-click-lightbox-form-12/
Disallow: /component/users/?view=registration&Itemid=101
Disallow: /component/users/?view=reset&Itemid=101
Disallow: /component/users/?view=remind&Itemid=101
Disallow: /calculator/
Disallow: /premium-dushovi-kabiny/
Disallow: //premium/
Allow: /calculator$

Sitemap: https://www.weston.com.ua/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 25 entries Valid XML Yes

Sample URLs:

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: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.weston.com.ua/

301https://weston.com.ua/

Preferred variant: www

HTTP → HTTPS

301http://www.weston.com.ua/ → https://www.weston.com.ua/

Consistent

A+

Domain Intelligence

weston.com.ua — via Internet Invest LLC, 6 years, 8 months old

PASS

weston.com.ua — via Internet Invest LLC, 6 years, 8 months old

Domain registered until Jan 17, 2027 (4 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: Internet Invest LLC

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.

Domain expiry

144 days

January 17, 2027

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

6 years, 8 months

Registered January 17, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:7a60:0:105c::1

Registrar

Internet Invest LLC

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Internet Invest LLC

Created January 17, 2020 (6 years, 8 months ago)

Expires January 17, 2027 (4 months)

Last Updated May 12, 2026

Name Servers ns1.fastdns.hosting, ns210.inhostedns.net, ns310.inhostedns.org

DNSSEC Not enabled

Registrant Registrant information is not published

Hosting

IP Address 2a00:7a60:0:105c::1

Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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