Skip to content
https://amista.cz

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 7 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.amista.cz/
200https://amista.cz/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://amista.cz/ → http://www.amista.cz/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
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
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
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
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 80.250.29.42: lookup 80.250.29.42: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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
36 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

36
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
Info::
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
Info::
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
Info::
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, 75 ms lookup
PASS
1 A records, 75 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 80.250.29.42
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns.forpsi.cz, ns.forpsi.net, ns.forpsi.it
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 75 ms
Got: 75 ms
A80.250.29.42
AAAA—
CNAME—
NSns.forpsi.cz, ns.forpsi.net, ns.forpsi.it
MX
0 amista-cz.m-v1.mx.microsoft
TXT
MS=ms52071253
atlassian-domain-verification=oWyjM4WgM3rynsFNW5avLY2AGhYx7ME/Y6BkVAGtbZa7TaSbiH...
SPF v=spf1 include:spf.protection.outlook.com ip4:81.0.202.54 a:mail2.wia.cz -all
uber-domain-verification=b2633148-a32b-4a6c-95be-808efd329ac5
apple-domain-verification=x06F8CiCMjoQRJ8g
CAALookup not available with standard resolver
Resolved in 75 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
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (RSASHA512)
A
Multi-Resolver DNS Speed
Mean 82ms across 3 resolvers (spread 26ms)
PASS
Mean 82ms across 3 resolvers (spread 26ms)
Info::
Cloudflare: 73ms
Got: 73ms via 1.1.1.1:53
Info::
Google: 74ms
Got: 74ms via 8.8.8.8:53
Info::
Quad9: 99ms
Got: 99ms via 9.9.9.9:53
A
Redirect Chain
1 redirect(s), 311 ms total
PASS
1 redirect(s), 311 ms total
Info::
Single redirect
Got: https://amista.cz → https://www.amista.cz/ (301)
Info::
WWW normalization redirect

https://amista.cz

109 ms · HTTP/1.1

301

https://www.amista.cz/

202 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://amista.cz301109 msHTTP/1.1Apache/2.4.62 (Debian)
2https://www.amista.cz/200202 msHTTP/1.1Apache/2.4.62 (Debian)

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 102 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 102 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /styleguide.html
Disallow: /admin
Sitemap: https://www.amista.cz/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
amista.cz — via INTERNET CZ, a.s., 20 years, 11 months old, hosted on WIA-AS - WIA spol. s.r.o., CZ
PASS
amista.cz — via INTERNET CZ, a.s., 20 years, 11 months old, hosted on WIA-AS - WIA spol. s.r.o., CZ
Info::
Domain registered until Feb 27, 2028 (1 years, 4 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: INTERNET CZ, a.s.
Warning::
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.
Info::
Hosting: WIA-AS - WIA spol. s.r.o., CZ
Got: AS21430
Domain expiry

489 days

February 27, 2028

SSL certificate

36 days

Issued by Let's Encrypt

Domain age

20 years, 11 months

Registered February 28, 2006

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

WIA-AS - WIA spol. s.r.o., CZ

ASN AS21430

80.250.29.42

Registrar

INTERNET CZ, a.s.

Unlocked 3 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 INTERNET CZ, a.s.
Created February 28, 2006 (20 years, 11 months ago)
Expires February 27, 2028 (1 years, 4 months)
Last Updated February 17, 2021
Name Servers ns.forpsi.cz, ns.forpsi.it, ns.forpsi.net
DNSSEC Enabled
Hosting
IP Address 80.250.29.42
ASN AS21430 (WIA-AS - WIA spol. s.r.o., CZ)
Provider WIA-AS - WIA spol. s.r.o., CZ
Data source: rdap (0.6s)

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 182 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
73 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
34 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
182 ms
Total Time Total request time from DNS lookup through full response.
182 ms

Connection waterfall

DNS Lookup 73 ms TCP Connect 34 ms TLS Handshake 38 ms Server Processing 36 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback