Skip to content
https://businesstimes.com.sg

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.businesstimes.com.sg/
200https://businesstimes.com.sg/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://businesstimes.com.sg/ https://businesstimes.com.sg/

Consistent

B
Domain Intelligence
businesstimes.com.sg — via CSC Corporate Domains Inc, 29 years, 4 months old, hosted on AWS
REVIEW
businesstimes.com.sg — via CSC Corporate Domains Inc, 29 years, 4 months old, hosted on AWS
Critical::
Domain expires in 26 days
This domain expires on May 19, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 19, 2026
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: AWS
Got: AS16509
Domain expiry

EXPIRED

May 19, 2026

SSL certificate

192 days

Issued by Amazon

Domain age

29 years, 4 months

Registered May 19, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.249.228.34

Registrar

CSC Corporate Domains Inc

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains Inc
Created May 19, 1997 (29 years, 4 months ago)
Expires May 19, 2026 (26 days)
Last Updated May 9, 2025
Name Servers ns-1208.awsdns-23.org, ns-1993.awsdns-57.co.uk, ns-364.awsdns-45.com, ns-621.awsdns-13.net
DNSSEC Not enabled
Registrant SPH MEDIA LIMITED
Hosting
IP Address 13.249.228.34
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.3s)

This domain expires on May 19, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

192
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
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG50-P6)
Got: x-amz-cf-id: FaL1EVul-nwtJNtBJNcFsr0uH0dC0XH9TmcrDym4SkzU6UKundDbsQ==
Info::
CDN cache status: LambdaGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: FaL1EVul-nwtJNtBJNcFsr0uH0dC0XH9TmcrDym4SkzU6UKundDbsQ==
A+
DNS Records
4 A records, 60 ms lookup
PASS
4 A records, 60 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.249.228.19, 13.249.228.99, 13.249.228.34, 13.249.228.48
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-621.awsdns-13.net, ns-1993.awsdns-57.co.uk, ns-364.awsdns-45.com, ns-1208.awsdns-23.org
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: 60 ms
Got: 60 ms
A13.249.228.19, 13.249.228.99, 13.249.228.34, 13.249.228.48
AAAA
CNAME
NSns-621.awsdns-13.net, ns-1993.awsdns-57.co.uk, ns-364.awsdns-45.com, ns-1208.awsdns-23.org
MX
10 vw.asia1.com.sg
TXT
SPF v=spf1 include: ip4:10/8 ip4:192.168/16 ip4:172.16/12 ip4:202.27.16.0/20 ip4:203...
HFNL75JA5T6HRR59M1BPUTPG98
kc587k37xjbgn0wqq60nkpbd788sfgpb
google-site-verification=An4vX2YG7G5A7ChCgM-Rkz8PQ69AAofrxvtNVHd0Tt0
rmv5khtqdb590d6s27z8n7gwh26tyl9m
pbtvjqpfnf1vj2h5ocbja1em08
tsr8n85m1b283f6yzrx39bbyl0brklb6
84x9jk6y13f1g5klgl12cqlxpscyd5l7
_hcvzpaljomai9woz8e8bf3lop0br5zo
9vx7fm49pj8tpjwvn5kwblfd23hqhw13
8w3ygjt8xrrjw6k2zbfj07znm66cwy8m
CAALookup not available with standard resolver
Resolved in 60 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
1 redirect(s), 591 ms total
PASS
1 redirect(s), 591 ms total
Info::
Single redirect
Got: https://businesstimes.com.sg → https://www.businesstimes.com.sg (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 591 ms total
Got: 591 ms

https://businesstimes.com.sg

195 ms · HTTP/1.1

301

https://www.businesstimes.com.sg

396 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://businesstimes.com.sg301195 msHTTP/1.1CloudFront
2https://www.businesstimes.com.sg200396 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 187 URLs
PASS
robots.txt present, sitemap with 187 URLs
Info::
robots.txt is present
Got: 1414 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 187 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1414 B Sitemaps referenced 2 User-agents Google-Extended, Google-Read-Aloud, ChatGPT-User, claude-web, *, Google-CloudVertexBot, ChatGPT-OpenAI, GPTBot, ClaudeBot, Perplexity-User, DeepseekBot, OAI-SearchBot, anthropic-ai, Claude-SearchBot, Claude-User, Bingbot, Deepseek, PerplexityBot Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
#
# For syntax checking, see:
# http://www.frobee.com/robots-txt-check

User-agent: *
Crawl-delay: 10
Disallow:

# Allow specific AI crawlers
User-agent: Google-Extended
Allow: /

User-agent: Google-CloudVertexBot
Allow: /

User-agent: Google-Read-Aloud
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ChatGPT-OpenAI
Allow: /

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: claude-web
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: Bingbot
Allow: /

# Optional for Zaobao exploration
User-agent: DeepseekBot
Allow: /

User-agent: Deepseek
Allow: /

Sitemap: https://www.businesstimes.com.sg/googlenews.xml
Sitemap: https://www.businesstimes.com.sg/sitemap.xml

A+
HTTP Probe Timing
Total 233 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
57 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.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
233 ms
Total Time Total request time from DNS lookup through full response.
233 ms

Connection waterfall

DNS Lookup 57 ms TCP Connect 16 ms TLS Handshake 18 ms Server Processing 142 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