Skip to content
https://taipeitimes.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 5 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
1 redirect(s), 2158 ms total
REVIEW
1 redirect(s), 2158 ms total
Info::
Single redirect
Got: https://taipeitimes.com → https://www.taipeitimes.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2158 ms total
Got: 2158 ms

https://taipeitimes.com

1187 ms · HTTP/1.1

301

https://www.taipeitimes.com/

971 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://taipeitimes.com3011187 msHTTP/1.1nginx
2https://www.taipeitimes.com/200971 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.taipeitimes.com/
200https://taipeitimes.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://taipeitimes.com/ → https://www.taipeitimes.com/

Consistent

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

Connection waterfall

DNS Lookup 44 ms TCP Connect 293 ms TLS Handshake 590 ms Server Processing 301 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
312 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

312
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, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 203.69.75.164
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-424.awsdns-53.com, ns-941.awsdns-53.net, ns-1846.awsdns-38.co.uk, ns-1034.awsdns-01.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: 45 ms
Got: 45 ms
A203.69.75.164
AAAA—
CNAME—
NSns-424.awsdns-53.com, ns-941.awsdns-53.net, ns-1846.awsdns-38.co.uk, ns-1034.awsdns-01.org
MX
5 home.taipeitimes.com
TXT
SPF v=spf1 ip4:218.211.33.64/27 ip4:61.218.68.176/28 ip4:61.216.26.1/24 mx:home.taip...
CAALookup not available with standard resolver
Resolved in 45 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 1391 URLs
PASS
robots.txt present, sitemap with 1391 URLs
Info::
robots.txt is present
Got: 411 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1391 entries
Info::
Sitemap index with 1391 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 411 B Sitemaps referenced 2 User-agents Meta-ExternalAgent, Meta-ExternalFetcher, Google-Extended, GoogleOther-Image, FacebookBot, facebookexternalhit, GoogleOther, GoogleOther-Video, * Blocking No — crawling allowed
# Bots
User-agent: Meta-ExternalAgent
User-agent: Meta-ExternalFetcher
User-agent: FacebookBot
User-agent: facebookexternalhit
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
Allow: /
Disallow: /log/tt

User-agent: *
Disallow: /log/tt

Sitemap: https://www.taipeitimes.com/sitemapIndex.xml
Sitemap: https://www.taipeitimes.com/sitemap/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1391 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
taipeitimes.com — via Domain.com - Network Solutions, LLC, 27 years, 9 months old, hosted on HINET Data Communication Business Group, TW
PASS
taipeitimes.com — via Domain.com - Network Solutions, LLC, 27 years, 9 months old, hosted on HINET Data Communication Business Group, TW
Info::
Domain registered until Nov 11, 2027 (1 years, 6 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: Domain.com - Network Solutions, LLC
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: HINET Data Communication Business Group, TW
Got: AS3462
Domain expiry

485 days

November 11, 2027

SSL certificate

312 days

Issued by Sectigo Limited

Domain age

27 years, 9 months

Registered December 6, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

HINET Data Communication Business Group, TW

ASN AS3462

203.69.75.164

Registrar

Domain.com - Network Solutions, LLC

Unlocked 4 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 Domain.com - Network Solutions, LLC
Created December 6, 1998 (27 years, 9 months ago)
Expires November 11, 2027 (1 years, 6 months)
Last Updated August 17, 2022
Name Servers ns-1034.awsdns-01.org, ns-1846.awsdns-38.co.uk, ns-424.awsdns-53.com, ns-941.awsdns-53.net
DNSSEC Not enabled
Hosting
IP Address 203.69.75.164
ASN AS3462 (HINET Data Communication Business Group, TW)
Provider HINET Data Communication Business Group, TW
Data source: rdap (0.4s)

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

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

Send Feedback