Skip to content
https://singaporeair.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
404 Not Found
Checks
9
4 PASS 5 REVIEW
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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 404 Expected: 301 redirect to HTTPS

www / non-www

404https://www.singaporeair.com/
200https://singaporeair.com/

HTTP → HTTPS

404http://singaporeair.com/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
181 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 27 ms lookup
PASS
2 A records, 27 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 95.100.200.130, 95.100.200.18
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a12-64.akam.net, a7-64.akam.net, a20-67.akam.net, a18-66.akam.net, a13-65.akam.net, a1-247.akam.net
Info::
1 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: 27 ms
Got: 27 ms
A95.100.200.130, 95.100.200.18
AAAA
CNAME
NSa12-64.akam.net, a7-64.akam.net, a20-67.akam.net, a18-66.akam.net, a13-65.akam.net, a1-247.akam.net
MX
0 singaporeair-com.mail.protection.outlook.com
TXT
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all
_hpjlh7dhk9h86x15g9fo4wp0klv406z
globalsign-domain-verification=52784278967930EEB8FF573589B498AC
2155-88D9-EB88-FF14-B8BA-0E27-73EA-9EAE
CAALookup not available with standard resolver
Resolved in 27 ms

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+
Redirect Chain
0 redirect(s), 80 ms total
PASS
0 redirect(s), 80 ms total

https://singaporeair.com

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://singaporeair.com40480 msHTTP/1.1AkamaiGHost
A+
Domain Intelligence
singaporeair.com — via CSC Corporate Domains, Inc., 31 years, 6 months old, hosted on Akamai
PASS
singaporeair.com — via CSC Corporate Domains, Inc., 31 years, 6 months old, hosted on Akamai
Info::
Domain registered until Mar 17, 2027 (11 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: CSC Corporate Domains, Inc.
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: Akamai
Got: AS20940
Domain expiry

247 days

March 17, 2027

SSL certificate

181 days

Issued by DigiCert Inc

Domain age

31 years, 6 months

Registered March 16, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS20940

95.100.200.18

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created March 16, 1995 (31 years, 6 months ago)
Expires March 17, 2027 (11 months)
Last Updated March 13, 2026
Name Servers a1-247.akam.net, a12-64.akam.net, a13-65.akam.net, a18-66.akam.net, a20-67.akam.net, a7-64.akam.net
DNSSEC Not enabled
Hosting
IP Address 95.100.200.18
ASN AS20940 (AKAMAI-ASN1, NL)
Provider Akamai
Data source: rdap (0.3s)

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 419 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
18 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
419 ms
Total Time Total request time from DNS lookup through full response.
419 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 18 ms TLS Handshake 20 ms Server Processing 353 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