Skip to content
https://swiss.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 4 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), 283 ms total
REVIEW
2 redirect(s), 283 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.swiss.com/

https://swiss.com

104 ms · HTTP/1.0

301

https://www.swiss.com/

106 ms · HTTP/1.1

302

https://www.swiss.com/nl/en/homepage

73 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://swiss.com301104 msHTTP/1.0BigIP
2https://www.swiss.com/302106 msHTTP/1.1cloudflare
3https://www.swiss.com/nl/en/homepage20073 msHTTP/1.1cloudflare

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
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 231 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 231 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# robots.txt https://www.swiss.com/

User-agent: *
Allow: /
Disallow: /service/secured/
Disallow: /deeplink

Sitemap: https://www.swiss.com/sitemap/sitemap_lx.xml.gz
Sitemap: https://www.swiss.com/aircore/sitemaps/sitemap-index.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
230 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
A+
DNS Records
1 A records, 60 ms lookup
PASS
1 A records, 60 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 146.216.3.74
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: ns1.swiss.com, ns2.swiss.com
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
Info::
DNS resolution time: 60 ms
Got: 60 ms
A146.216.3.74
AAAA
CNAME
NSns1.swiss.com, ns2.swiss.com
MX
10 mxa-005f4701.gslb.pphosted.com
10 mxb-005f4701.gslb.pphosted.com
TXT
Swiss International Air Lines Ltd.
MS=ms22036800
MS=ms63767859
srCJ4MBw9gDMxmkCEesKKOZRT9AOjO5+0hrINzmlHTZ6CarX9P8AHOAL4JBU/6iCUm0XhAWtJ9vQ6X7w...
bd456010d4c949c593fc8d2ff4e27e12
-ufTy8erjEl-0ydL-NsxuyyVsmY
_hwm6nuzaryk0jgh9n372i2x93ocw4z3
docusign=242343fb-e93a-4244-8cca-03a92815d53d
docusign=83275cf5-4060-47eb-82f6-f149e9583823
paloaltonetworks-site-verification=9e8169c2cdbbff044e03d85112732a615c674ab42c74b...
d365mktkey=2hk1kvrk9ywnotubx24denb3l
d365mktkey=dxhjw10iotviyxizm55bhjjf
d365mktkey=2i066srp88myi3mpdu1mumilk
hk56nnl5941fwh3f0phdhqg2np427cm1
d7cp9ws5gq8c0kypy42bwqcxdnyblz0p
google-site-verification=nJ7AalaXuwZQeNfgv-sSKaqJ1zujGJtFzzhfmZ1cJZ0
SPF v=spf1 mx ip4:80.77.214.0/26 ip4:80.77.221.241 include:spf-005f4701.pphosted.com...
CsohU7sumBiIUGz5WJfAVmqTLZCdKkT5cnFWR7nJX9uJQUy//hlHUU+E7/dTc22YMjeupH8uY7Drpiy2...
797hc5ywgvjdz05bq0g8bmgbt8grrrwp
41stf5rh38h699gy4rwhb0c886c83s9r
swisssign-check=EW8dgdUW7syett91SpeoY__sOl8
swisssign-check=JoN4YgjXD-UuaUbqZLxDkljdmH8
swisssign-check=hYACSYJUisltvY7yv2w7Pm7bgaY
swisssign-check=RcTyEcVq-xw35jD9LzNHnam0FmM
swisssign-check=UCVu2z5Uh2Rmm19egu1gEvPrY6M
_wepn7f976bx5jwdd8aayhiwaxgta2gu
apple-domain-verification=nIH5NaTHSU6O7GKG
miro-verification=79bfaffd957eeb04175988f4b27bed0f30709882
CAALookup not available with standard resolver
Resolved in 60 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+
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.swiss.com/
200https://swiss.com/

Preferred variant: non-www

HTTP → HTTPS

301http://swiss.com/ https://www.swiss.com/

Consistent

A+
Domain Intelligence
swiss.com — via Abion AB, 28 years, 1 months old, hosted on SWISS-AS, CH
PASS
swiss.com — via Abion AB, 28 years, 1 months old, hosted on SWISS-AS, CH
Info::
Domain registered until Aug 6, 2026 (3 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: Abion AB
Warning::
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.
Info::
Hosting: SWISS-AS, CH
Got: AS204590
Domain expiry

51 days

August 6, 2026

SSL certificate

230 days

Issued by SwissSign AG

Domain age

28 years, 1 months

Registered August 7, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SWISS-AS, CH

ASN AS204590

146.216.3.74

Registrar

Abion AB

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Abion AB
Created August 7, 1998 (28 years, 1 months ago)
Expires August 6, 2026 (3 months)
Last Updated October 17, 2025
Name Servers ns1.swiss.com, ns2.swiss.com
DNSSEC Not enabled
Hosting
IP Address 146.216.3.74
ASN AS204590 (SWISS-AS, CH)
Provider SWISS-AS, CH
Data source: rdap (0.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

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

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

Connection waterfall

DNS Lookup 39 ms TCP Connect 16 ms TLS Handshake 44 ms Server Processing 20 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