Skip to content
https://uw.edu.pl

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
6
PASS
3
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
3 PASS 6 REVIEW
B
Redirect Chain
1 redirect(s), 2277 ms total
REVIEW
1 redirect(s), 2277 ms total
Info::
Single redirect
Got: https://uw.edu.pl → https://www.uw.edu.pl/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2277 ms total
Got: 2277 ms

https://uw.edu.pl

952 ms · HTTP/1.1

301

https://www.uw.edu.pl/

1326 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uw.edu.pl301952 msHTTP/1.1Apache/2.4.62 (Debian)
2https://www.uw.edu.pl/2001326 msHTTP/1.1Apache/2.4.62 (Debian)

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

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.uw.edu.pl/
200https://uw.edu.pl/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://uw.edu.pl/ https://uw.edu.pl/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 174 ms TCP Connect 154 ms TLS Handshake 469 ms Server Processing 203 ms Content Transfer 0 ms
C
TLS Certificate Expiry & Recommendations
Action
20 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

20
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 20 days remaining
  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
B
CDN & Delivery
Varnish
REVIEW
Varnish
Info::
Site is served via Varnish CDN
Got: via: 1.1 varnish (Varnish/5.0)
CDN Detected: Varnish
Provider Varnish Evidence via: 1.1 varnish (Varnish/5.0)
A+
DNS Records
1 A records, 168 ms lookup
PASS
1 A records, 168 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.0.115.152
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns2.net.icm.edu.pl, ns2.uw.edu.pl, ns1.uw.edu.pl, arwena.nask.waw.pl, wask.wask.wroc.pl, ns1.net.icm.edu.pl
Info::
3 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: 168 ms
Got: 168 ms
A193.0.115.152
AAAA
CNAME
NSns2.net.icm.edu.pl, ns2.uw.edu.pl, ns1.uw.edu.pl, arwena.nask.waw.pl, wask.wask.wroc.pl, ns1.net.icm.edu.pl
MX
1 ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
TXT
ZOOM_verify_FPq5Vq6mA5vDC7Xr14n5W6
SPF v=spf1 ip4:193.0.65.128/27 ip4:193.0.72.2 ip4:193.0.72.144 include:_spf.google.c...
mojecertpl-site-verification-SHTg1QJlG3L1OfActZVGYVwLbZyydQN1
google-site-verification=9bxiqefMY9pOwsk0p9aTflYRgk2BpB-Rmh35GjlL3sc
google-site-verification=emEHyVA9-mgt7vuyQxn9pPuyUHJ-Y3O_eC0v9db_8RI
HARICA-aqRkL4h1GFy3qBuPdXP
MS=9B6B4F4D1E13DCD9C42DA37212BC9C7CDBBD9E40
google-site-verification=BxTj-GBfIWLtL_SxtzjTowFvVJjGl9Yu9VDvLlqvdJ8
google-site-verification=zj1ZJZ-lHoMsuNDCOmyfKcVRY8DkWZKukZWx4v1n1M0
google-site-verification=bqgMVFeuUu77cbQfjeOTda3O7CBEvMf0s-jP1gcKLz8
CAALookup not available with standard resolver
Resolved in 168 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 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 206 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 206 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /?s=
Disallow: /&s=
Disallow: /search/
Disallow: /readme.html
Disallow: /license.txt

Sitemap: https://www.uw.edu.pl/sitemap.xml

A+
Domain Intelligence
uw.edu.pl — via Domena.pl sp. z o.o., 31 years, 9 months old, hosted on UW-AS, PL
PASS
uw.edu.pl — via Domena.pl sp. z o.o., 31 years, 9 months old, hosted on UW-AS, PL
Info::
Domain registered until Dec 31, 2031 (5 years, 9 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: Domena.pl sp. z o.o.
Info::
Hosting: UW-AS, PL
Got: AS8890
Domain expiry

2027 days

December 31, 2031

SSL certificate

20 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

31 years, 9 months

Registered January 1, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

UW-AS, PL

ASN AS8890

193.0.115.152

Registrar

Domena.pl sp. z o.o.

Lock status unknown 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Domena.pl sp. z o.o.
Created January 1, 1995 (31 years, 9 months ago)
Expires December 31, 2031 (5 years, 9 months)
Last Updated December 16, 2021
Name Servers wask.wask.wroc.pl, ns2.net.icm.edu.pl, ns1.net.icm.edu.pl, ns1.uw.edu.pl, arwena.nask.waw.pl, ns2.uw.edu.pl
DNSSEC Not enabled
Hosting
IP Address 193.0.115.152
ASN AS8890 (UW-AS, PL)
Provider UW-AS, 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