Skip to content
https://poznan.pl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
302 Found
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.

B
Redirect Chain
1 redirect(s), 1026 ms total
REVIEW
1 redirect(s), 1026 ms total
Info::
Single redirect
Got: https://poznan.pl → https://www.poznan.pl/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://poznan.pl
Warning::
Redirect overhead: 1026 ms total
Got: 1026 ms

https://poznan.pl

233 ms · HTTP/1.1

302

https://www.poznan.pl/

794 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://poznan.pl302233 msHTTP/1.1Varnish
2https://www.poznan.pl/200794 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.poznan.pl/
200https://poznan.pl/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://poznan.pl/ https://www.poznan.pl/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

37
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: 150.254.186.176
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: dns3.amu.edu.pl, bilbo.nask.org.pl, dns.amu.edu.pl, kirdan.nask.net.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: 51 ms
Got: 51 ms
A150.254.186.176
AAAA
CNAME
NSdns3.amu.edu.pl, bilbo.nask.org.pl, dns.amu.edu.pl, kirdan.nask.net.pl
MX
1 aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com ~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+
Crawlability
robots.txt present, sitemap with 546 URLs
PASS
robots.txt present, sitemap with 546 URLs
Info::
robots.txt is present
Got: 1009 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 546 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1009 B Sitemaps referenced 1 User-agents SemrushBot-BA, dotbot, 008, sentibot, SentiBot, Yandex, *, Amazonbot, DataForSeoBot, AhrefsBot, SemrushBot, SiteAuditBot Blocking No — crawling allowed
User-Agent: *
Disallow: /mim/wspolne
Disallow: /mim/public/socialnet/
Disallow: /mim/socialnet/
Disallow: /mim/print-view/
Disallow: /mim/qrcode/
Disallow: /mim/zipfile/
Disallow: /zipfile/
Disallow: /tilecache/
Disallow: /leading/
Disallow: /mapa_geopoz/
Disallow: /mim/plan/map.html
Disallow: /mim/plan/plan.html
Disallow: /mim/plan/map_service.html
Disallow: /mim/public/szukaj/
Disallow: /print-view/bip/
Disallow: /api-xml/bip/
Disallow: /api-json/bip/
Disallow: /bip/admin/
Disallow: /bip/rejestr-zmian/
Disallow: /socialnet/
Disallow: /plan/
Crawl-delay: 10

User-agent: 008
Disallow: /

User-agent: Amazonbot
Disallow: /

# www.sentibot.eu
User-agent: sentibot
Disallow: /
User-agent: SentiBot
Disallow: /

User-agent: DataForSeoBot
Disallow: /

User-agent: Yandex
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: SiteAuditBot
Disallow: /

User-agent: SemrushBot-BA
Disallow: /

User-agent: dotbot
Disallow: /

Sitemap: https://www.poznan.pl/sitemap.xml

A+
Domain Intelligence
poznan.pl — via home.pl sp. z o.o., 31 years, 9 months old, hosted on POZMAN POZMAN-EDU, PL
PASS
poznan.pl — via home.pl sp. z o.o., 31 years, 9 months old, hosted on POZMAN POZMAN-EDU, PL
Info::
Domain registered until Dec 31, 2028 (2 years, 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: home.pl sp. z o.o.
Info::
Hosting: POZMAN POZMAN-EDU, PL
Got: AS9112
Domain expiry

932 days

December 31, 2028

SSL certificate

37 days

Issued by DigiCert Inc

Domain age

31 years, 9 months

Registered January 1, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

POZMAN POZMAN-EDU, PL

ASN AS9112

150.254.186.176

Registrar

home.pl sp. z o.o.

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 home.pl sp. z o.o.
Created January 1, 1995 (31 years, 9 months ago)
Expires December 31, 2028 (2 years, 8 months)
Last Updated December 15, 2025
Name Servers kirdan.nask.net.pl, dns.amu.edu.pl, bilbo.nask.org.pl, dns3.amu.edu.pl
DNSSEC Not enabled
Hosting
IP Address 150.254.186.176
ASN AS9112 (POZMAN POZMAN-EDU, PL)
Provider POZMAN POZMAN-EDU, PL
Data source: rdap (0.5s)

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

A+
HTTP Probe Timing
Total 301 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
68 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
49 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
132 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
302 ms
Total Time Total request time from DNS lookup through full response.
302 ms

Connection waterfall

DNS Lookup 68 ms TCP Connect 49 ms TLS Handshake 132 ms Server Processing 53 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