Infrastructure - https://lodz.pl BeaverCheck Audit

F

HTTP Probe Timing

Action

Total 8733 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

FIX

DNS Lookup

174 ms

TCP Connect

165 ms

TLS Handshake

167 ms

Time to First Byte

8.57 s

Total Time

8.73 s

Connection waterfall

DNS Lookup 174 ms TCP Connect 165 ms TLS Handshake 167 ms Server Processing 8.06 s Content Transfer 165 ms

D

CDN & Delivery

Action

No CDN detected

FIX

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

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, sitemap with 17666 URLs

REVIEW

robots.txt present, sitemap with 17666 URLs

robots.txt is present

Got: 22 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml contains 17666 entries

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

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 22 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /

sitemap.xml 200 OK

Type URL Set URLs 17666 entries Valid XML No

Sample URLs:

B

TLS Certificate Expiry & Recommendations

65 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

65

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add includeSubDomains to the HSTS directive
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

A+

DNS Records

1 A records, 175 ms lookup

PASS

1 A records, 175 ms lookup

Resolves to 1 IPv4 address(es)

Got: 65.21.171.62

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns1.tpnet.pl, dns.man.lodz.pl, dns2.man.lodz.pl, ns1.task.gda.pl

1 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution time: 175 ms

Got: 175 ms

A	65.21.171.62
AAAA	—
CNAME	—
NS	ns1.tpnet.pl, dns.man.lodz.pl, dns2.man.lodz.pl, ns1.task.gda.pl
MX	0 mazurek.man.lodz.pl
TXT	SPF v=spf1 redirect=_spf006.man.lodz.pl google-site-verification=MYElsp52eObDZLH_2Cn03AWEyo_XBUuvhb_b4o54CGc
CAA	Lookup not available with standard resolver

Resolved in 175 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

Got: https://lodz.pl

https://lodz.pl

650 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://lodz.pl	200	650 ms	HTTP/1.1	lodzidea

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.lodz.pl/

200https://lodz.pl/

Preferred variant: non-www

HTTP → HTTPS

301http://lodz.pl/ → https://lodz.pl/

Consistent

A+

Domain Intelligence

lodz.pl — via OVH SAS, 31 years, 9 months old, hosted on Hetzner

PASS

lodz.pl — via OVH SAS, 31 years, 9 months old, hosted on Hetzner

Domain registered until Dec 31, 2026 (8 months remaining)

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.

Registrar: OVH SAS

Hosting: Hetzner

Got: AS24940

Domain expiry

172 days

December 31, 2026

SSL certificate

65 days

Issued by Let's Encrypt

Domain age

31 years, 9 months

Registered January 1, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Hetzner

ASN AS24940

65.21.171.62

Registrar

OVH SAS

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 OVH SAS

Created January 1, 1995 (31 years, 9 months ago)

Expires December 31, 2026 (8 months)

Last Updated October 31, 2023

Name Servers dns2.man.lodz.pl, dns.man.lodz.pl, ns1.tpnet.pl, ns1.task.gda.pl

DNSSEC Not enabled

Hosting

IP Address 65.21.171.62

ASN AS24940 (HETZNER-AS, DE)

Provider Hetzner

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