Skip to content
https://www.nspvk.sk

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
12
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 12 REVIEW
B
DNS Records
1 A records, 70 ms lookup
REVIEW
1 A records, 70 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 195.28.64.102
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: web-new.slovanet.net
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: 70 ms
Got: 70 ms
A195.28.64.102
AAAA—
CNAMEweb-new.slovanet.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 70 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 CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 195.28.64.102 does not match any cert SAN: web-new.slovanet.net
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 107ms across 3 resolvers (spread 106ms)
REVIEW
Mean 107ms across 3 resolvers (spread 106ms)
Info::
Google: 41ms
Got: 41ms via 8.8.8.8:53
Info::
Cloudflare: 134ms
Got: 134ms via 1.1.1.1:53
Info::
Quad9: 147ms
Got: 147ms via 9.9.9.9:53
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.nspvk.sk/
200https://nspvk.sk/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.nspvk.sk/ → https://www.nspvk.sk/

Consistent

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

Certificate validity

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

Recommended actions

  • Renew certificate — 30 days remaining
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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.datatables.net, 3 assets); document served directly from origin
REVIEW
Assets on Cloudflare (host cdn.datatables.net, 3 assets); document served directly from origin
Warning::
Document not behind existing CDN (Cloudflare serves the assets)
The page's subresources are delivered by Cloudflare (cdn.datatables.net, 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: a4e97ffc5f80522d-CDG
Info::
Assets on Cloudflare: cdn.datatables.net (assets: 3), cache HIT
Got: cf-ray: a4e97ffc5f80522d-CDG
Warning: Assets on a CDN, document is not: Cloudflare
Document origin not attributed

Asset hosts on a CDN

  • cdn.datatables.net — Cloudflare · assets: 3 · Cache Status: HIT

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.
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.nspvk.sk

https://www.nspvk.sk

274 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.nspvk.sk200274 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 60 URLs
PASS
robots.txt present, sitemap with 60 URLs
Info::
robots.txt is present
Got: 109 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 60 entries
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 109 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Disallow: /cgi-bin/
Disallow: /tmp/
Disallow: /gener.tmp.exec.x/
Crawl-delay: 1

Crawl-delay: 1
sitemap.xml 200 OK
Type URL Set URLs 60 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
nspvk.sk — via Slovanet, a. s., 21 years, 9 months old, hosted on SLOVANET - Slovanet a.s., SK
PASS
nspvk.sk — via Slovanet, a. s., 21 years, 9 months old, hosted on SLOVANET - Slovanet a.s., SK
Info::
Domain registered until Apr 18, 2027 (5 months remaining)
Info::
Registrar: Slovanet, 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: SLOVANET - Slovanet a.s., SK
Got: AS8778
Domain expiry

177 days

April 18, 2027

SSL certificate

30 days

Issued by Let's Encrypt

Domain age

21 years, 9 months

Registered April 18, 2005

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

SLOVANET - Slovanet a.s., SK

ASN AS8778

195.28.64.102

Registrar

Slovanet, a. s.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Slovanet, a. s.
Created April 18, 2005 (21 years, 9 months ago)
Expires April 18, 2027 (5 months)
Last Updated April 13, 2026
Name Servers ns.slovanet.net, ns1.slovanet.net
Hosting
IP Address 195.28.64.102
ASN AS8778 (SLOVANET - Slovanet a.s., SK)
Provider SLOVANET - Slovanet a.s., SK
Data source: whois (0.9s)

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

Connection waterfall

DNS Lookup 168 ms TCP Connect 39 ms TLS Handshake 87 ms Server Processing 156 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