Skip to content
https://krakow.pl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
3 PASS 4 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 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.krakow.pl/
200https://krakow.pl/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://krakow.pl/

HTTP version does not redirect to HTTPS

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: 36 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 36 B Sitemaps referenced 0 User-agents AhrefsBot Blocking No — crawling allowed
User-agent: AhrefsBot

Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
HTTP Probe Timing
Action
Total 1683 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
173 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
169 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
187 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.68 s
Total Time Total request time from DNS lookup through full response.
1.68 s

Connection waterfall

DNS Lookup 173 ms TCP Connect 169 ms TLS Handshake 187 ms Server Processing 1.15 s Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

75
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, 176 ms lookup
PASS
1 A records, 176 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.156.2.195
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns.fuw.edu.pl, bilbo.nask.org.pl, info.cyf-kr.edu.pl, nms.cyf-kr.edu.pl
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: 176 ms
Got: 176 ms
A149.156.2.195
AAAA—
CNAME—
NSdns.fuw.edu.pl, bilbo.nask.org.pl, info.cyf-kr.edu.pl, nms.cyf-kr.edu.pl
MX
4 srvmx.cyfronet.pl
TXT
SPF v=spf1 ip4:149.156.2.0/24 mx -all
CAALookup not available with standard resolver
Resolved in 176 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://krakow.pl

https://krakow.pl

1654 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://krakow.pl2001654 msHTTP/1.1nginx
A+
Domain Intelligence
krakow.pl — via Akademickie Centrum Komputerowe CYFRONET AGH, 25 years, 8 months old, hosted on CYFRONET-AS Metropolitan Area Network Autonomous System, PL
PASS
krakow.pl — via Akademickie Centrum Komputerowe CYFRONET AGH, 25 years, 8 months old, hosted on CYFRONET-AS Metropolitan Area Network Autonomous System, PL
Info::
Domain registered until Dec 31, 2026 (8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Akademickie Centrum Komputerowe CYFRONET AGH
Info::
Hosting: CYFRONET-AS Metropolitan Area Network Autonomous System, PL
Got: AS8267
Domain expiry

166 days

December 31, 2026

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

25 years, 8 months

Registered January 1, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CYFRONET-AS Metropolitan Area Network Autonomous System, PL

ASN AS8267

149.156.2.195

Registrar

Akademickie Centrum Komputerowe CYFRONET AGH

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Akademickie Centrum Komputerowe CYFRONET AGH
Created January 1, 2001 (25 years, 8 months ago)
Expires December 31, 2026 (8 months)
Last Updated December 18, 2024
Name Servers info.cyf-kr.edu.pl, nms.cyf-kr.edu.pl, bilbo.nask.org.pl, dns.fuw.edu.pl
DNSSEC Not enabled
Registrant Akademickie Centrum Komputerowe CYFRONET AGH
Hosting
IP Address 149.156.2.195
ASN AS8267 (CYFRONET-AS Metropolitan Area Network Autonomous System, PL)
Provider CYFRONET-AS Metropolitan Area Network Autonomous System, PL
Data source: rdap (0.8s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback