Skip to content
https://rondainvest.cz

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 194.182.91.225 does not match any cert SAN: host225-91-182-194.serverdedicati.aruba.it
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.
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
69 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

69
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, 76 ms lookup
PASS
1 A records, 76 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 194.182.91.225
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: ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 76 ms
Got: 76 ms
A194.182.91.225
AAAA—
CNAME—
NSns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu
MX
10 mail.rondainvest.cz
TXT
SPF v=spf1 a mx include:spf.smartemailing.cz include:spf.affilbox.cz -all
atlassian-domain-verification=ukiE0JJIIa8BJZ38v/CF4lsWJJaUxalEvLVzqhTWLTEsGnGpEf...
openai-domain-verification=dv-AfbkdfW9iISJFO5ahYbcuMNK
google-site-verification=i4VitK-vPpUMkaLRunjdlvD1MzXq_A0VW6Axr861szI
CAALookup not available with standard resolver
Resolved in 76 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 (RSASHA256)
A
Multi-Resolver DNS Speed
Mean 59ms across 3 resolvers (spread 79ms)
PASS
Mean 59ms across 3 resolvers (spread 79ms)
Info::
Cloudflare: 29ms
Got: 29ms via 1.1.1.1:53
Info::
Google: 42ms
Got: 42ms via 8.8.8.8:53
Info::
Quad9: 108ms
Got: 108ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://rondainvest.cz

https://rondainvest.cz

175 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rondainvest.cz200175 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 349 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 349 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /*?utm_
Disallow: /*&utm_
Disallow: /*?gad_
Disallow: /*&gad_
Disallow: /*?gclid=
Disallow: /*&gclid=
Disallow: /*?gbraid=
Disallow: /*&gbraid=
Disallow: /*?wbraid=
Disallow: /*&wbraid=
Disallow: /*?_gl=
Disallow: /*&_gl=

Sitemap: https://rondainvest.cz/wp-sitemap.xml



A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.rondainvest.cz/
200https://rondainvest.cz/

Preferred variant: non-www

HTTP → HTTPS

301http://rondainvest.cz/ → https://rondainvest.cz/

Consistent

A+
Domain Intelligence
rondainvest.cz — via Hosting Concepts B.V., 9 years, 5 months old, hosted on INTERNET-CZ - INTERNET CZ, a.s., CZ
PASS
rondainvest.cz — via Hosting Concepts B.V., 9 years, 5 months old, hosted on INTERNET-CZ - INTERNET CZ, a.s., CZ
Info::
Domain registered until Jul 10, 2028 (1 years, 7 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Hosting Concepts B.V.
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: INTERNET-CZ - INTERNET CZ, a.s., CZ
Got: AS24806
Domain expiry

596 days

July 10, 2028

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

9 years, 5 months

Registered July 11, 2017

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

INTERNET-CZ - INTERNET CZ, a.s., CZ

ASN AS24806

194.182.91.225

Registrar

Hosting Concepts B.V.

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 Hosting Concepts B.V.
Created July 11, 2017 (9 years, 5 months ago)
Expires July 10, 2028 (1 years, 7 months)
Last Updated June 5, 2023
Name Servers ns1.openprovider.nl, ns2.openprovider.be, ns3.openprovider.eu
DNSSEC Enabled
Hosting
IP Address 194.182.91.225
ASN AS24806 (INTERNET-CZ - INTERNET CZ, a.s., CZ)
Provider INTERNET-CZ - INTERNET CZ, a.s., CZ
Data source: rdap (0.7s)

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 303 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
58 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.
76 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
236 ms
Total Time Total request time from DNS lookup through full response.
303 ms

Connection waterfall

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

Send Feedback