Infrastructure - https://kth.se BeaverCheck Audit

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.

B

Redirect Chain

1 redirect(s), 2185 ms total

REVIEW

1 redirect(s), 2185 ms total

Single redirect

Got: https://kth.se → https://www.kth.se/ (301)

WWW normalization redirect

Redirect overhead: 2185 ms total

Got: 2185 ms

https://kth.se

1111 ms · HTTP/1.1

301

https://www.kth.se/

1074 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://kth.se	301	1111 ms	HTTP/1.1
2	https://www.kth.se/	200	1074 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

B

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.kth.se/

200https://kth.se/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://kth.se/ → https://kth.se/

Consistent

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

183 ms

TCP Connect

187 ms

TLS Handshake

380 ms

Time to First Byte

937 ms

Total Time

938 ms

Connection waterfall

DNS Lookup 183 ms TCP Connect 187 ms TLS Handshake 380 ms Server Processing 187 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

120 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

120

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, 543 ms lookup

PASS

1 A records, 543 ms lookup

Resolves to 1 IPv4 address(es)

Got: 130.237.28.40

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2001:6b0:1:11c2::82ed:1c28

5 nameserver(s) configured

Got: a.ns.kth.se, b.ns.kth.se, e.ns.kth.se, ns2.chalmers.se, sunic.sunet.se

4 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 is slow (543 ms)

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

Got: 543 ms

A	130.237.28.40
AAAA	2001:6b0:1:11c2::82ed:1c28
CNAME	—
NS	a.ns.kth.se, b.ns.kth.se, e.ns.kth.se, ns2.chalmers.se, sunic.sunet.se
MX	10 mailfilter-ng-4.sunet.se 10 mailfilter-ng-1.sunet.se 10 mailfilter-ng-3.sunet.se 20 mailfilter-ng-2.sunet.se
TXT	MS=ms86914267 HARICA-2QmDZC3DyhpI9p6wUi3 include:_spf.eu.messagegears.net KTH Royal Institute of Technology, SWEDEN apple-domain-verification=yiK5a1btuIncRk6Q mentimeter-22c50963-9801-4565-a424-07d4a1e2c1c9 facebook-domain-verification=ybxcywd9y5omfyzv9a4hi1122pxhys google-site-verification=6B_ijtuPLs8QEQOrY6CA9KNR6x_Tlq9h87fvzbQcTGk SPF v=spf1 include:_spf.kth.se include:customers.clickdimensions.com ~all adobe-idp-site-verification=9cb3a0e2a6197322d0dd6d29de0e1ac1ce9f990e3d5bd864aa4c... atlassian-domain-verification=bdViuC6aa8uovu2aPgsZjA4zglkgbkqx7eCtfJtIXi6uWFglmI...
CAA	Lookup not available with standard resolver

Resolved in 543 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+

IPv6 Readiness

IPv6 reachable (180 ms)

PASS

IPv6 reachable (180 ms)

IPv6 is configured and reachable at 2001:6b0:1:11c2::82ed:1c28

Got: 180 ms connect

IPv6 Ready

AAAA Records 2001:6b0:1:11c2::82ed:1c28 Connection Reachable (180 ms)

A+

Crawlability

robots.txt present, sitemap with 78 URLs

PASS

robots.txt present, sitemap with 78 URLs

robots.txt is present

Got: 980 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 78 entries

robots.txt references sitemap

robots.txt 200 OK

Size 980 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

#
# well-known resource robots.txt from 17.392
#
User-agent: *

Disallow: /lediga-jobb/language_redirect/

Disallow: /lediga-jobb/interna/

Disallow: /form/

Disallow: /public/

Disallow: /cm/

Disallow: /info/

Disallow: /work/

Disallow: /xyz/

Disallow: /xyz

Disallow: /en/xyz/

Disallow: /en/xyz

Disallow: /2.994/

Disallow: /2.9631/

Disallow: /2.1019/

Disallow: /2.1166/

Disallow: /2.1218/

Disallow: /2.1219/

Disallow: /2.36446/

Disallow: /2.14566/

Disallow: /2.28744/

Disallow: /2.98714/

Disallow: /en/2.28744/

Disallow: /2.9631/

Disallow: /en/2.9631/

Disallow: /search

Disallow: /social/user/_report_/abuse/

Disallow: /gemensamt/kategorier-1.31190

Disallow: /en/gemensamt/kategorier-1.31190

Disallow: /social/api/profile/1.1/

Disallow: /test/

Disallow: /blogs/tags

Disallow: /es/

Disallow: /*?rss=*

Disallow: /*?iCal=*

Disallow: /api/icalendar/

Disallow: /start/

Disallow: /intranat

Disallow: /sci/2.840


Sitemap: https://www.kth.se/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 78 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

kth.se — via Loopia AB, 41 years, 2 months old

PASS

kth.se — via Loopia AB, 41 years, 2 months old

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

Registrar: Loopia AB

Registrar lock is NOT enabled

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Domain expiry

172 days

December 31, 2026

SSL certificate

120 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

41 years, 2 months

Registered August 28, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2001:6b0:1:11c2::82ed:1c28

Registrar

Loopia AB

Unlocked 5 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Loopia AB

Created August 28, 1985 (41 years, 2 months ago)

Expires December 31, 2026 (8 months)

Last Updated March 31, 2026

Name Servers a.ns.kth.se, b.ns.kth.se, ns2.chalmers.se, sunic.sunet.se, e.ns.kth.se

Registrant ahikun3996-00001

Hosting

IP Address 2001:6b0:1:11c2::82ed:1c28

Data source: whois (1.1s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice