Infrastructure - https://ukrspecsystems.ua BeaverCheck Audit

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

REVIEW

0/1 IPs match cert SAN

PTR for 35.187.82.108 does not match any cert SAN: 108.82.187.35.bc.googleusercontent.com

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

Redirect Chain

1 redirect(s), 1427 ms total

REVIEW

1 redirect(s), 1427 ms total

Single redirect

Got: https://ukrspecsystems.ua → https://ukrspecsystems.com/ (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://ukrspecsystems.ua

Redirect overhead: 1427 ms total

Got: 1427 ms

Cross-domain redirect detected

https://ukrspecsystems.ua

489 ms · HTTP/1.1

302

https://ukrspecsystems.com/

938 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://ukrspecsystems.ua	302	489 ms	HTTP/1.1	openresty
2	https://ukrspecsystems.com/	200	938 ms	HTTP/1.1	cloudflare

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

35 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

35

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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 Google Cloud CDN (host blog-api.getblog.app, 3 assets); document served directly from origin

REVIEW

Assets on Google Cloud CDN (host blog-api.getblog.app, 3 assets); document served directly from origin

Document not behind existing CDN (Google Cloud CDN serves the assets)

The page's subresources are delivered by Google Cloud CDN (blog-api.getblog.app, 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: via: 1.1 google

Assets on Google Cloud CDN: blog-api.getblog.app (assets: 3)

Got: via: 1.1 google

Assets on a CDN, document is not: Google Cloud CDN

Document origin not attributed

Asset hosts on a CDN

blog-api.getblog.app — Google Cloud CDN · assets: 3

Other asset hosts

res2.weblium.site — assets: 30 · not attributed
wl-apps.yourwebsite.life — assets: 12 · not attributed
www.googletagmanager.com — assets: 5 · Google
cdnjs.cloudflare.com — assets: 2 · below probe threshold
connect.facebook.net — assets: 2 · below probe threshold
ajax.googleapis.com — assets: 1 · below probe threshold
googleads.g.doubleclick.net — assets: 1 · below probe threshold
leadbooster-chat.pipedrive.com — assets: 1 · below probe threshold
snap.licdn.com — assets: 1 · below probe threshold
static.cloudflareinsights.com — assets: 1 · below probe threshold
webforms.pipedrive.com — assets: 1 · below probe threshold
www.google-analytics.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

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

PASS

1 A records, 22 ms lookup

Resolves to 1 IPv4 address(es)

Got: 35.187.82.108

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: ns3.weblium.com, ns1.weblium.com, ns2.weblium.com, ns4.weblium.com

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: 22 ms

Got: 22 ms

A	35.187.82.108
AAAA	—
CNAME	—
NS	ns3.weblium.com, ns1.weblium.com, ns2.weblium.com, ns4.weblium.com
MX	—
TXT	inactive
CAA	Lookup not available with standard resolver

Resolved in 22 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+

Multi-Resolver DNS Speed

Mean 9ms across 3 resolvers (spread 9ms)

PASS

Mean 9ms across 3 resolvers (spread 9ms)

Quad9: 6ms

Got: 6ms via 9.9.9.9:53

Cloudflare: 8ms

Got: 8ms via 1.1.1.1:53

Google: 15ms

Got: 15ms via 8.8.8.8:53

A+

Crawlability

robots.txt present, sitemap with 2 URLs

PASS

robots.txt present, sitemap with 2 URLs

robots.txt is present

Got: 108 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 2 entries

Sitemap index with 2 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *
Sitemap: https://ukrspecsystems.com/sitemap.xml
Disallow: /.sw_/_host_/_replacer_
# reserved

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

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

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.ukrspecsystems.ua/

200https://ukrspecsystems.ua/

Preferred variant: non-www

HTTP → HTTPS

301http://ukrspecsystems.ua/ → https://ukrspecsystems.ua/

Consistent

A+

Domain Intelligence

ukrspecsystems.ua — via BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD', 3 years, 1 months old, hosted on Google Cloud

PASS

ukrspecsystems.ua — via BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD', 3 years, 1 months old, hosted on Google Cloud

Domain registered until Aug 31, 2027 (11 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: BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD'

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: Google Cloud

Got: AS396982

Domain expiry

343 days

August 31, 2027

SSL certificate

35 days

Issued by Let's Encrypt

Domain age

3 years, 1 months

Registered August 31, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

35.187.82.108

Registrar

BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD'

Unlocked 2 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 BUREAU OF PATENT ATTORNEYS OF 'PATENTSERVIS LTD'

Created August 31, 2023 (3 years, 1 months ago)

Expires August 31, 2027 (11 months)

Last Updated November 4, 2024

Name Servers ns1.weblium.com, ns2.weblium.com

DNSSEC Not enabled

Registrant not published

Hosting

IP Address 35.187.82.108

ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)

Provider Google Cloud

Data source: rdap (0.9s)

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

A

HTTP Probe Timing

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

PASS

DNS Lookup

20 ms

TCP Connect

145 ms

TLS Handshake

165 ms

Time to First Byte

479 ms

Total Time

480 ms

Connection waterfall

DNS Lookup 20 ms TCP Connect 145 ms TLS Handshake 165 ms Server Processing 149 ms Content Transfer 0 ms