Skip to content
https://admin.ch

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 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
2 redirect(s), 378 ms total
REVIEW
2 redirect(s), 378 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.admin.ch/

https://admin.ch

99 ms · HTTP/1.1

301

https://www.admin.ch/

176 ms · HTTP/1.1

302

https://www.admin.ch/de

103 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://admin.ch30199 msHTTP/1.1
2https://www.admin.ch/302176 msHTTP/1.1
3https://www.admin.ch/de200103 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

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
TLS Certificate Expiry & Recommendations
183 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 53 ms lookup
PASS
1 A records, 53 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.223.22.200
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: ins1.admin.ch, ins2.admin.ch, ins4.admin.ch, ins5.admin.ch, ins3.admin.ch
Info::
4 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: 53 ms
Got: 53 ms
A193.223.22.200
AAAA—
CNAME—
NSins1.admin.ch, ins2.admin.ch, ins4.admin.ch, ins5.admin.ch, ins3.admin.ch
MX
10 mx04.mail.admin.ch
10 mx02.mail.admin.ch
10 mx03.mail.admin.ch
10 mx01.mail.admin.ch
TXT
_arjwx46j10cgbyi2npdklf0me4hqfoj
_8sd6ecniglp3wvamk0u116n0ztbv9ad
SPF v=spf1 redirect=_spfgroupa.admin.ch
cisco-ci-domain verification=27ef6be0682bd1449e9a754a29ee4531b654161aa2067287c0c...
_neikxrgab5747znfr0vof9iy4a3rmll
MS=ms59193443
_2leh2ye2o7d3sp08vugmfpjocxzr17x
_rlpir8gl6ea277e39l94jce2e6xm7ot
_63nce9t273ayzl8sua5ivux7yiza6sz
swisssign-check=XIfM82TEBBySziaEPmG1SS0Xl7M
CAALookup not available with standard resolver
Resolved in 53 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 183 URLs
PASS
robots.txt present, sitemap with 183 URLs
Info::
robots.txt is present
Got: 65 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 183 entries
Info::
Sitemap index with 183 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 65 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
Sitemap: https://www.admin.ch/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 183 entries Valid XML Yes
Child Sitemaps:
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.admin.ch/
200https://admin.ch/

Preferred variant: non-www

HTTP → HTTPS

301http://admin.ch/ → https://admin.ch/

Consistent

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

Connection waterfall

DNS Lookup 62 ms TCP Connect 27 ms TLS Handshake 36 ms Server Processing 37 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback