Infrastructure - https://fortza.net BeaverCheck Audit

D

CDN & Delivery

Action

No CDN (document or assets)

FIX

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)

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.

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

42 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

42

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: 500, /health: 500, /healthz: 500, /ping: 500, /status: 500.

A+

DNS Records

1 A records, 50 ms lookup

PASS

1 A records, 50 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.248.197.90

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns1.gazduire.net, ns2.gazduire.net

3 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 50 ms

Got: 50 ms

A	185.248.197.90
AAAA	—
CNAME	—
NS	ns1.gazduire.net, ns2.gazduire.net
MX	10 mx.zoho.eu 20 mx2.zoho.eu 50 mx3.zoho.eu
TXT	SPF v=spf1 ip4:185.248.197.0 ip4:185.248.197.90 ip4:185.248.196.2 ip4:185.248.196.12... facebook-domain-verification=2vkia7zxf1c4ix3i9fwyzyp6ziw8cy
CAA	Lookup not available with standard resolver

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

No CNAME record present

A+

Reverse DNS

1/1 IPs match cert SAN

PASS

1/1 IPs match cert SAN

PTR for 185.248.197.90 matches certificate SAN: fortza.net

A

Multi-Resolver DNS Speed

Mean 68ms across 3 resolvers (spread 60ms)

PASS

Mean 68ms across 3 resolvers (spread 60ms)

Google: 31ms

Got: 31ms via 8.8.8.8:53

Cloudflare: 82ms

Got: 82ms via 1.1.1.1:53

Quad9: 91ms

Got: 91ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://fortza.net

https://fortza.net

170 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://fortza.net	200	170 ms	HTTP/1.1

A+

Crawlability

robots.txt present, sitemap with 9 URLs

PASS

robots.txt present, sitemap with 9 URLs

robots.txt is present

Got: 111 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 111 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

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

Sitemap: https://fortza.net/wp-sitemap.xml

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

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

500https://www.fortza.net/

200https://fortza.net/

HTTP → HTTPS

301http://fortza.net/ → https://fortza.net/

Consistent

A+

Domain Intelligence

fortza.net — via Global Domain Group LLC, 9 years, 6 months old, hosted on GNET-AS - Tes Euro Media SRL, RO

PASS

fortza.net — via Global Domain Group LLC, 9 years, 6 months old, hosted on GNET-AS - Tes Euro Media SRL, RO

Domain registered until May 17, 2027 (6 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: Global Domain Group 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.

Hosting: GNET-AS - Tes Euro Media SRL, RO

Got: AS51295

Domain expiry

206 days

May 17, 2027

SSL certificate

42 days

Issued by Let's Encrypt

Domain age

9 years, 6 months

Registered May 17, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

GNET-AS - Tes Euro Media SRL, RO

ASN AS51295

185.248.197.90

Registrar

Global Domain Group LLC

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 Global Domain Group LLC

Created May 17, 2017 (9 years, 6 months ago)

Expires May 17, 2027 (6 months)

Last Updated May 6, 2026

Name Servers ns1.fortza.net, ns2.fortza.net

DNSSEC Not enabled

Hosting

IP Address 185.248.197.90

ASN AS51295 (GNET-AS - Tes Euro Media SRL, RO)

Provider GNET-AS - Tes Euro Media SRL, RO

Data source: rdap (0.4s)

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 226 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

1 ms

TCP Connect

55 ms

TLS Handshake

58 ms

Time to First Byte

225 ms

Total Time

227 ms

Connection waterfall

DNS Lookup 1 ms TCP Connect 55 ms TLS Handshake 58 ms Server Processing 111 ms Content Transfer 2 ms