Skip to content
https://phoca.cz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1143 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 1143 B Sitemaps referenced 0 User-agents AhrefsBot, MJ12bot, JCE, *, Googlebot Blocking No — crawling allowed
# If the Joomla site is installed within a folder such as at
# e.g. www.example.com/joomla/ the robots.txt file MUST be
# moved to the site root at e.g. www.example.com/robots.txt
# AND the joomla folder name MUST be prefixed to the disallowed
# path, e.g. the Disallow rule for the /administrator/ folder
# MUST be changed to read Disallow: /joomla/administrator/
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/orig.html
#
# For syntax checking, see:
# http://www.sxw.org.uk/computing/robots/check.html



User-agent: AhrefsBot 
Crawl-Delay: 3000

User-agent: MJ12bot 
Crawl-Delay: 3000

User-agent: JCE 
Disallow: /


User-agent: *
Disallow: /administrator/
Disallow: /bin/			   
Disallow: /cache/
Disallow: /cli/
Disallow: /components/
# Disallow: /images/
Disallow: /includes/
Disallow: /installation/
Disallow: /language/
Disallow: /layouts/				   
Disallow: /libraries/
Disallow: /logs/
# Disallow: /media/
Disallow: /modules/
Disallow: /plugins/
# Disallow: /templates/
Disallow: /tmp/
Disallow: /translation/

#Googlebot
User-agent: Googlebot
#Allow: *.css
#Allow: *.js
Allow: *.js
Allow: *.css
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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 301-redirects to HTTPS

www / non-www

200https://www.phoca.cz/
200https://phoca.cz/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://phoca.cz/ https://phoca.cz/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
A+
DNS Records
1 A records, 51 ms lookup
PASS
1 A records, 51 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 213.211.34.110
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.videon-znojmo.cz, ns2.videon-znojmo.cz
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 51 ms
Got: 51 ms
A213.211.34.110
AAAA
CNAME
NSns1.videon-znojmo.cz, ns2.videon-znojmo.cz
MX
10 mail.videon-znojmo.cz
TXT
SPF v=spf1 include:ns1.videon-znojmo.cz ip4:212.96.164.158 ip4:213.211.35.38 ~all
CAALookup not available with standard resolver
Resolved in 51 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 420 ms total
PASS
1 redirect(s), 420 ms total
Info::
Single redirect
Got: https://phoca.cz → https://www.phoca.cz/ (301)
Info::
WWW normalization redirect

https://phoca.cz

129 ms · HTTP/1.1

301

https://www.phoca.cz/

291 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://phoca.cz301129 msHTTP/1.1Apache/2.4.65 (FreeBSD) OpenSSL/1.1.1w-freebsd mod_fcgid/2.3.9 PHP/8.4.15
2https://www.phoca.cz/200291 msHTTP/1.1Apache/2.4.65 (FreeBSD) OpenSSL/1.1.1w-freebsd mod_fcgid/2.3.9 PHP/8.4.15

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
phoca.cz — via REG-ZONER, 18 years, 11 months old, hosted on ITSELF Network and internet service provider., CZ
PASS
phoca.cz — via REG-ZONER, 18 years, 11 months old, hosted on ITSELF Network and internet service provider., CZ
Info::
Domain registered until Aug 7, 2026 (3 months remaining)
Info::
Registrar: REG-ZONER
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: ITSELF Network and internet service provider., CZ
Got: AS12570
Domain expiry

55 days

August 7, 2026

SSL certificate

78 days

Issued by Let's Encrypt

Domain age

18 years, 11 months

Registered August 8, 2007

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

ITSELF Network and internet service provider., CZ

ASN AS12570

213.211.34.110

Registrar

REG-ZONER

Unlocked 2 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 REG-ZONER
Created August 8, 2007 (18 years, 11 months ago)
Expires August 7, 2026 (3 months)
Last Updated July 27, 2020
Name Servers ns1.videon-znojmo.cz, ns2.videon-znojmo.cz
Hosting
IP Address 213.211.34.110
ASN AS12570 (ITSELF Network and internet service provider., CZ)
Provider ITSELF Network and internet service provider., 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 178 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
41 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
43 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
178 ms
Total Time Total request time from DNS lookup through full response.
178 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 41 ms TLS Handshake 43 ms Server Processing 43 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