Skip to content
https://wp.pl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
2 PASS 6 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), 2217 ms total
REVIEW
1 redirect(s), 2217 ms total
Info::
Single redirect
Got: https://wp.pl → https://www.wp.pl/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2217 ms total
Got: 2217 ms

https://wp.pl

834 ms · HTTP/1.1

301

https://www.wp.pl/

1382 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://wp.pl301834 msHTTP/1.1nginx
2https://www.wp.pl/2001382 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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: 491 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 491 B Sitemaps referenced 0 User-agents Perplexity-User, OAI-SearchBot, ChatGPT-User, *, GPTBot, CCBot, PerplexityBot Blocking No — crawling allowed
User-agent: *
Disallow: /kodyrabatowe/*?category=
Disallow: /kodyrabatowe/*?s=
Disallow: /kodyrabatowe/*?letter=
Disallow: /trendy/*
Disallow: /?s=*
Disallow: /auth/v1/sso/*
Disallow: /mini.html?*
Disallow: /*?*proxied=*
Disallow: /getfrontendparts

Noindex: /trendy/*
Noindex: /?s=*

User-agent: GPTBot
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /
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.wp.pl/
200https://wp.pl/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://wp.pl/ https://www.wp.pl/

Consistent

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

Connection waterfall

DNS Lookup 220 ms TCP Connect 205 ms TLS Handshake 207 ms Server Processing 205 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
154 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

154
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, 232 ms lookup
PASS
1 A records, 232 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 212.77.98.9
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: ns2.wp.pl, ns1.wp.pl
Info::
2 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
Warning::
DNS resolution is slow (232 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 232 ms
A212.77.98.9
AAAA
CNAME
NSns2.wp.pl, ns1.wp.pl
MX
0 mx.wp.pl
5 mx5.wp.pl
TXT
SPF v=spf1 ip4:193.17.41.0/24 ip4:193.222.135.0/24 ip4:212.77.96.0/19 ip4:212.126.20...
google-site-verification=DS__k01aJWrM8aRxwqJitv9WOnXvpf5pNhhwZTtSY8A
facebook-domain-verification=tw97u44442qrak4gikf7poieuv027j
google-site-verification=7Cqr3Ga39QoHRVorGJsrwdtujXbeTox51oJEN21lndI
CAALookup not available with standard resolver
Resolved in 232 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Domain Intelligence
wp.pl — via AZ.pl Sp. z o.o., 28 years, 4 months old, hosted on WIRTUALNAPOLSKA GDANSK, Poland, PL
PASS
wp.pl — via AZ.pl Sp. z o.o., 28 years, 4 months old, hosted on WIRTUALNAPOLSKA GDANSK, Poland, PL
Info::
Domain registered until Apr 27, 2027 (1 years 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: AZ.pl Sp. z o.o.
Info::
Hosting: WIRTUALNAPOLSKA GDANSK, Poland, PL
Got: AS12827
Domain expiry

287 days

April 27, 2027

SSL certificate

154 days

Issued by DigiCert Inc

Domain age

28 years, 4 months

Registered April 28, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WIRTUALNAPOLSKA GDANSK, Poland, PL

ASN AS12827

212.77.98.9

Registrar

AZ.pl Sp. z o.o.

Lock status unknown 2 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 AZ.pl Sp. z o.o.
Created April 28, 1998 (28 years, 4 months ago)
Expires April 27, 2027 (1 years)
Last Updated February 18, 2026
Name Servers ns1.wp.pl, ns2.wp.pl
DNSSEC Not enabled
Hosting
IP Address 212.77.98.9
ASN AS12827 (WIRTUALNAPOLSKA GDANSK, Poland, PL)
Provider WIRTUALNAPOLSKA GDANSK, Poland, PL
Data source: rdap (1.2s)

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