Infrastructure - https://bangkokpost.com BeaverCheck Audit

F

IPv6 Readiness

Action

IPv6 records exist but unreachable

FIX

IPv6 records exist but unreachable

IPv6 DNS records exist but server is not reachable

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Got: 2001:c00:4618:2006::111e, 2001:c00:4618:2006::111d

IPv6 connection error

Got: dial tcp6 [2001:c00:4618:2006::111e]:443: i/o timeout

IPv6 Misconfigured

AAAA Records 2001:c00:4618:2006::111e, 2001:c00:4618:2006::111d Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D

CDN & Delivery

Action

No CDN detected

FIX

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

TLS Certificate Expiry & Recommendations

68 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

68

days left

0d 30d 60d 90d+

Recommended actions

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, 38 ms lookup

PASS

1 A records, 38 ms lookup

Resolves to 1 IPv4 address(es)

Got: 103.253.133.80

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 2 IPv6 (AAAA) record(s)

Got: 2001:c00:4618:2006::111e, 2001:c00:4618:2006::111d

2 nameserver(s) configured

Got: ns2.inet.co.th, ns1.inet.co.th

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 38 ms

Got: 38 ms

A	103.253.133.80
AAAA	2001:c00:4618:2006::111e, 2001:c00:4618:2006::111d
CNAME	—
NS	ns2.inet.co.th, ns1.inet.co.th
MX	10 bangkokpost-com.mail.protection.outlook.com
TXT	tollbit-domain-verification=acd647a382ea4c6192f5d1e0994a09ff5efb89f2a24dd46f0427... _globalsign-domain-verification=PETbRbRl7gzWwpJ77ncdXadO79LXKu-7MH_bVYXOw6 MS=ms45789715 ca3-179aab813cd047aab691fa43ca5d78a9 google-site-verification=-7y38xyTEhjsAQzcYgI7UiIHgbaEA1McTzyBQICBq04 SPF v=spf1 include:spf.protection.outlook.com include:_spf.debutmail.com a:smgw.bang... _globalsign-domain-verification=Emq9bDWymUavaKOR83TGBpXYx_Xqq4k6idJch4YF93 _globalsign-domain-verification=Ygltt7RMHwGKFkppe3BS6QU46V6sraj72ZHcL-vKFg _globalsign-domain-verification=dGrHng7dJ6d54sHpovmVOOczPh1AxbXfw32f1xcHz2
CAA	Lookup not available with standard resolver

Resolved in 38 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

Redirect Chain

1 redirect(s), 53 ms total

PASS

1 redirect(s), 53 ms total

Single redirect

Got: https://bangkokpost.com → https://www.bangkokpost.com/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://bangkokpost.com

https://bangkokpost.com

8 ms · HTTP/1.1

302

https://www.bangkokpost.com/

45 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://bangkokpost.com	302	8 ms	HTTP/1.1	bytex/1.29.5
2	https://www.bangkokpost.com/	200	45 ms	HTTP/1.1	bytex/1.29.5

See the visual redirect chain in the HTTP Probe tab →

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

A+

Crawlability

robots.txt present, sitemap with 12 URLs

PASS

robots.txt present, sitemap with 12 URLs

robots.txt is present

Got: 539 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 12 entries

Sitemap index with 12 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 539 B Sitemaps referenced 2 User-agents *, grapeshot, Googlebot-News Blocking No — crawling allowed

User-agent: Googlebot-News
Disallow:
Sitemap: https://www.bangkokpost.com/sitemap.xml
Sitemap: https://www.bangkokpost.com/sitemap_news.xml

User-agent: *
Disallow: /faq/food.php*
Disallow: /faq/*
Disallow: /faq/
Disallow: /share/*
Disallow: /share/
Disallow: /hits/
Disallow: /hitsplayer/
Disallow: /hits/*?*
Disallow: /frame_map/*
Disallow: /vdo*/embed
Disallow: /*-embed/*
Disallow: /*_info_*.html
Disallow: /member/
Disallow: /member/*
Disallow: /comment/process
Disallow: /ajax/_getLikeUnlike.php


User-agent: grapeshot
Disallow:/

sitemap.xml 200 OK

Type Sitemap Index URLs 12 entries Valid XML Yes

Child Sitemaps:

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.bangkokpost.com/

200https://bangkokpost.com/

HTTP → HTTPS

302http://bangkokpost.com/ → https://www.bangkokpost.com/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

bangkokpost.com — via Name.com, Inc., 29 years, 5 months old

PASS

bangkokpost.com — via Name.com, Inc., 29 years, 5 months old

Domain registered until Mar 27, 2027 (11 months remaining)

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.

Registrar: Name.com, Inc.

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.

Domain expiry

284 days

March 27, 2027

SSL certificate

68 days

Issued by ZeroSSL

Domain age

29 years, 5 months

Registered March 26, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:c00:4618:2006::111d

Registrar

Name.com, Inc.

Unlocked 2 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 Name.com, Inc.

Created March 26, 1997 (29 years, 5 months ago)

Expires March 27, 2027 (11 months)

Last Updated March 10, 2026

Name Servers ns1.inet.co.th, ns2.inet.co.th

DNSSEC Not enabled

Hosting

IP Address 2001:c00:4618:2006::111d

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 39 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

33 ms

TCP Connect

1 ms

TLS Handshake

5 ms

Time to First Byte

39 ms

Total Time

39 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 1 ms Content Transfer 0 ms