Infrastructure - https://ukuat.org 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 194.163.173.180 does not match any cert SAN: mail.ikasmeridis.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

Multi-Resolver DNS Speed

Mean 71ms across 3 resolvers (spread 142ms)

REVIEW

Mean 71ms across 3 resolvers (spread 142ms)

Google: 20ms

Got: 20ms via 8.8.8.8:53

Quad9: 32ms

Got: 32ms via 9.9.9.9:53

Cloudflare: 162ms

Got: 162ms via 1.1.1.1:53

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

HTTP Probe Timing

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

REVIEW

DNS Lookup

36 ms

TCP Connect

65 ms

TLS Handshake

32 ms

Time to First Byte

1.40 s

Total Time

1.43 s

Connection waterfall

DNS Lookup 36 ms TCP Connect 65 ms TLS Handshake 32 ms Server Processing 1.26 s Content Transfer 28 ms

B

TLS Certificate Expiry & Recommendations

38 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

38

days left

0d 30d 60d 90d+

Recommended actions

Submit your domain to hstspreload.org to be added to the Chrome preload list
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 Cloudflare (host cdnjs.cloudflare.com, 3 assets); document served directly from origin

REVIEW

Assets on Cloudflare (host cdnjs.cloudflare.com, 3 assets); document served directly from origin

Document not behind existing CDN (Cloudflare serves the assets)

The page's subresources are delivered by Cloudflare (cdnjs.cloudflare.com, 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: cf-ray: a49e815d3e505d3e-CDG

Assets on Cloudflare: cdnjs.cloudflare.com (assets: 3), cache BYPASS

Got: cf-ray: a49e815d3e505d3e-CDG

Assets on a CDN, document is not: Cloudflare

Document origin not attributed

Asset hosts on a CDN

cdnjs.cloudflare.com — Cloudflare · assets: 3 · Cache Status: BYPASS

Other asset hosts

fonts.googleapis.com — assets: 2 · below probe threshold
www.google.com — assets: 1 · below probe threshold
www.googletagmanager.com — assets: 1 · below probe threshold
www.gstatic.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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.

A

DNS Records

1 A records, 269 ms lookup

PASS

1 A records, 269 ms lookup

Resolves to 1 IPv4 address(es)

Got: 194.163.173.180

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: dns1.registrar-servers.com, dns2.registrar-servers.com

3 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (269 ms)

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

Got: 269 ms

A	194.163.173.180
AAAA	—
CNAME	—
NS	dns1.registrar-servers.com, dns2.registrar-servers.com
MX	10 mx.zoho.eu 20 mx2.zoho.eu 50 mx3.zoho.eu
TXT	SPF v=spf1 include:eu.zcsend.net include:_spf.mailersend.net ~all
CAA	Lookup not available with standard resolver

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

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://ukuat.org

https://ukuat.org

940 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://ukuat.org	200	940 ms	HTTP/1.1	nginx

A+

Crawlability

robots.txt present, sitemap with 11 URLs

PASS

robots.txt present, sitemap with 11 URLs

robots.txt is present

Got: 0 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 11 entries

Sitemap index with 11 child sitemaps

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed

sitemap.xml 200 OK

Type Sitemap Index URLs 11 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

https://www.ukuat.org/

200https://ukuat.org/

HTTP → HTTPS

301http://ukuat.org/ → https://ukuat.org/

Consistent

A+

Domain Intelligence

ukuat.org — via NameCheap, Inc., 9 years, 3 months old, hosted on CONTABO - Contabo GmbH, DE

PASS

ukuat.org — via NameCheap, Inc., 9 years, 3 months old, hosted on CONTABO - Contabo GmbH, DE

Domain registered until Aug 14, 2027 (10 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: NameCheap, Inc.

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: CONTABO - Contabo GmbH, DE

Got: AS51167

Domain expiry

299 days

August 14, 2027

SSL certificate

38 days

Issued by Let's Encrypt

Domain age

9 years, 3 months

Registered August 14, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CONTABO - Contabo GmbH, DE

ASN AS51167

194.163.173.180

Registrar

NameCheap, Inc.

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 NameCheap, Inc.

Created August 14, 2017 (9 years, 3 months ago)

Expires August 14, 2027 (10 months)

Last Updated August 12, 2026

Name Servers dns1.registrar-servers.com, dns2.registrar-servers.com

DNSSEC Not enabled

Hosting

IP Address 194.163.173.180

ASN AS51167 (CONTABO - Contabo GmbH, DE)

Provider CONTABO - Contabo GmbH, DE

Data source: rdap (0.6s)

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