Skip to content
https://www.nemocnica-bory.sk

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
17
7 PASS 10 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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)
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 132.220.94.60: lookup 132.220.94.60: 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.
B
Redirect Chain
1 redirect(s), 1054 ms total
REVIEW
1 redirect(s), 1054 ms total
Info::
Single redirect
Got: https://www.nemocnica-bory.sk → https://nemocnica-bory.sk/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1054 ms total
Got: 1054 ms

https://www.nemocnica-bory.sk

446 ms · HTTP/1.1

301

https://nemocnica-bory.sk/

608 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nemocnica-bory.sk301446 msHTTP/1.1
2https://nemocnica-bory.sk/200608 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.nemocnica-bory.sk/
200https://nemocnica-bory.sk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.nemocnica-bory.sk/ → https://nemocnica-bory.sk/

Consistent

B
TLS Certificate Expiry & Recommendations
87 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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 Cloudflare (host cdn-cookieyes.com, 5 assets); document served directly from origin (Microsoft Azure)
REVIEW
Assets on Cloudflare (host cdn-cookieyes.com, 5 assets); document served directly from origin (Microsoft Azure)
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdn-cookieyes.com, 5 assets), but the HTML document itself comes straight from the origin (Microsoft Azure). 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: a4e9744d4a391584-SJC
Info::
Assets on Cloudflare: cdn-cookieyes.com (assets: 5), cache HIT
Got: cf-ray: a4e9744d4a391584-SJC
Warning: Assets on a CDN, document is not: Cloudflare
Document origin Microsoft Azure

Asset hosts on a CDN

  • cdn-cookieyes.com — Cloudflare · assets: 5 · Cache Status: HIT

Other asset hosts

  • nemocnica-bory.sk — assets: 87 · Microsoft Azure
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 2 · below probe threshold
  • cdn.trustindex.io — assets: 1 · below probe threshold
  • scripts.claspo.io — assets: 1 · below probe threshold
  • www.google.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
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.
A
DNS Records
1 A records, 19 ms lookup
PASS
1 A records, 19 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 132.220.94.60
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 19 ms
Got: 19 ms
A132.220.94.60
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 19 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
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 21ms across 3 resolvers (spread 23ms)
PASS
Mean 21ms across 3 resolvers (spread 23ms)
Info::
Cloudflare: 7ms
Got: 7ms via 1.1.1.1:53
Info::
Quad9: 27ms
Got: 27ms via 9.9.9.9:53
Info::
Google: 30ms
Got: 30ms via 8.8.8.8:53
A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 130 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 130 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /galeria/
Disallow: /wp-admin/
Disallow: /wp-include/
Disallow: /en/fotogaleria/
Disallow: /fotogaleria/
sitemap.xml 200 OK
Type Sitemap Index URLs 9 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
nemocnica-bory.sk — via Webglobe, a.s., 6 years, 10 months old, hosted on Microsoft Azure
PASS
nemocnica-bory.sk — via Webglobe, a.s., 6 years, 10 months old, hosted on Microsoft Azure
Warning::
Domain expires in 85 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jan 16, 2027
Info::
Registrar: Webglobe, 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: Microsoft Azure
Got: AS8075
Domain expiry

85 days

January 16, 2027

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

6 years, 10 months

Registered January 16, 2020

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

132.220.94.60

Registrar

Webglobe, a.s.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Webglobe, a.s.
Created January 16, 2020 (6 years, 10 months ago)
Expires January 16, 2027 (2 months)
Last Updated February 4, 2026
Name Servers ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
Registrant Svet zdravia Development, a.s.
Hosting
IP Address 132.220.94.60
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.6s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 17 ms TCP Connect 143 ms TLS Handshake 152 ms Server Processing 159 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://www.nemocnica-bory.sk/health (HTTP 200)
PASS
Health endpoint at https://www.nemocnica-bory.sk/health (HTTP 200)
Info::
Public health endpoint at https://www.nemocnica-bory.sk/health
Got: https://www.nemocnica-bory.sk/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback