Skip to content
https://helsinki.fi

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1930 ms total
FIX
2 redirect(s), 1930 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.helsinki.fi/
Warning::
Redirect overhead: 1930 ms total
Got: 1930 ms

https://helsinki.fi

679 ms · HTTP/1.1

301

https://www.helsinki.fi/

1069 ms · HTTP/1.1

302

https://www.helsinki.fi/en

182 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://helsinki.fi301679 msHTTP/1.1nginx/1.24.0
2https://www.helsinki.fi/3021069 msHTTP/1.1Varnish
3https://www.helsinki.fi/en200182 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

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

C
Crawlability
Action
robots.txt present, sitemap with 25 URLs
REVIEW
robots.txt present, sitemap with 25 URLs
Info::
robots.txt is present
Got: 72 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 25 entries
Info::
Sitemap index with 25 child sitemaps
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 72 B Sitemaps referenced 1 User-agents * Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /

Sitemap: https://www.helsinki.fi/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 25 entries Valid XML Yes
Child Sitemaps:
B
TLS Certificate Expiry & Recommendations
50 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

50
days left
0d 30d 60d 90d+

Recommended actions

  • 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, 350 ms lookup
PASS
1 A records, 350 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.214.222.50
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: hydra.helsinki.fi, serifos.helsinki.fi, ns1.d-zone.ca, ns-secondary.funet.fi, ns2.d-zone.ca
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
Warning::
DNS resolution is slow (350 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 350 ms
A128.214.222.50
AAAA—
CNAME—
NShydra.helsinki.fi, serifos.helsinki.fi, ns1.d-zone.ca, ns-secondary.funet.fi, ns2.d-zone.ca
MX
20 mail.it.helsinki.fi
20 send2.it.helsinki.fi
20 post2.it.helsinki.fi
TXT
mailerlite-domain-verification=d9824a74f72da008fbf88f4c7b68da3dffd26d97
successfactors-site-verification=YzRkZTcxN2FkODQyNzY0YzE5NDRiNTEyZmY3YjdhN2EwOTU...
google-site-verification=rypf2QYN_ZbnYzvOKHMIfPVOMDKah4lt1oHRA2-IDeg
MS=ms58429958
88OZmIN4CYvAzj9lQlCwmmYL8zg3/phA773NrDk+UqgdlDFTUXpuPtUTgt/6GR04c9eK08jk48J3CzTa...
HARICA-BSfga1wN5jEwEixod2y
SPF v=spf1 ip4:104.130.122.0/23 ip4:104.130.96.0/28 ip4:104.47.0.0/17 ip4:128.214.0....
apple-domain-verification=979tVg9sxlkBnndP
google-site-verification=U29I6jVnO9eoTu9tOxs-CT12TQW-7QlML3v_UmKUqYQ
CAALookup not available with standard resolver
Resolved in 350 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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.helsinki.fi/
200https://helsinki.fi/

Preferred variant: non-www

HTTP → HTTPS

301http://helsinki.fi/ → https://helsinki.fi/

Consistent

A+
Domain Intelligence
helsinki.fi — 35 years, 9 months old, hosted on FUNETAS, FI
PASS
helsinki.fi — 35 years, 9 months old, hosted on FUNETAS, FI
Info::
Hosting: FUNETAS, FI
Got: AS1741
Domain expiry

Unknown

SSL certificate

50 days

Issued by Let's Encrypt

Domain age

35 years, 9 months

Registered January 1, 1991

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

FUNETAS, FI

ASN AS1741

128.214.222.50

Registrar

Registrar unknown

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Created January 1, 1991 (35 years, 9 months ago)
Name Servers serifos.helsinki.fi [128.214.4.64] [ok], hydra.helsinki.fi [128.214.4.29] [ok], ns1.d-zone.ca [ok], ns2.d-zone.ca [ok], ns-secondary.funet.fi [128.214.248.132] [2001:708:10:55::53] [ok]
Registrant Helsingin yliopisto
Hosting
IP Address 128.214.222.50
ASN AS1741 (FUNETAS, FI)
Provider FUNETAS, FI
Data source: rdap (0.9s)
A
HTTP Probe Timing
Total 715 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
181 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
177 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
180 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
715 ms
Total Time Total request time from DNS lookup through full response.
715 ms

Connection waterfall

DNS Lookup 181 ms TCP Connect 177 ms TLS Handshake 180 ms Server Processing 177 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