Skip to content
https://chosun.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
5 PASS 3 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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

74
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, 606 ms lookup
PASS
1 A records, 606 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 3.35.113.248
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-1288.awsdns-33.org, ns-1618.awsdns-10.co.uk, ns-343.awsdns-42.com, ns-542.awsdns-03.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
Warning::
DNS resolution is slow (606 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 606 ms
A3.35.113.248
AAAA
CNAME
NSns-1288.awsdns-33.org, ns-1618.awsdns-10.co.uk, ns-343.awsdns-42.com, ns-542.awsdns-03.net
MX
0 spam.chosun.com
TXT
_acme-challenge.sandbox.chosun.com.=WQZ-txQ8JpD8amqBbabzVkHdqj_f9xJ57ixWAjMOiOw
google-site-verification= eRbXLmOpGthNZDDPjkR584Dnba5E9H P4CCIfk-ey6PM
google-site-verification=1k7vOpZhmuudYQLLT-4boknGOJ87GkhBtDiSkgqr8vU
google-site-verification=2flbaA0RZAndL2uhVra33yiJJD-fIneMDllGeJBNuO8
google-site-verification=57Oi1VCXiWQ_144wCOR7Xc-0I9xtynl6jopj-vbLES4
google-site-verification=6VJaEV0OAIti9MmzT9RcfL1PhmY3BXpSKTIS5x8qIEE
google-site-verification=C3var7laLCc8bcFSmkPcYxgAGkNEkxDhZStOaX3nFHk
google-site-verification=Z-CjAI7VsDgHwqztKJwqZfGtOoexgXQWKLETlGT_Vco
google-site-verification=kZVDofDPASRKM7DbhS7Wl64g0GDt1Wwi5SKJceCBM0o
google-site-verification=oNvCVn8cu479HpwS7Ane21_IkgXU4iCCDWe5wT0D5uU
google-site-verification=odEDnhrGYmtveLUXyMKEJuIbM_ZF_X14BYPPI0YgBiY
include: _acme-challenge.sandbox.chosun.com include:_spf.google.com ~all
include:_spfa.chosun.com include:_spfb.chosun.com include:_spfc.chosun.com inclu...
jsEW-xs_rsVLpUn_295TkakoMiAmU7NRCHly_yYy2R4
SPF v=spf1 ip4:43.202.28.16 ip4:52.78.179.24 ip4:112.175.255.152 ip4:54.180.75.126 i...
CAALookup not available with standard resolver
Resolved in 606 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 657 ms total
PASS
1 redirect(s), 657 ms total
Info::
Single redirect
Got: https://chosun.com → https://www.chosun.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 657 ms total
Got: 657 ms

https://chosun.com

374 ms · HTTP/1.1

301

https://www.chosun.com/

283 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://chosun.com301374 msHTTP/1.1Microsoft-IIS/8.5
2https://www.chosun.com/200283 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 100 URLs
PASS
robots.txt present, sitemap with 100 URLs
Info::
robots.txt is present
Got: 374 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 100 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 374 B Sitemaps referenced 2 User-agents *, GPTBot, DeepSeekBot Blocking No — crawling allowed
User-agent: *
Disallow: /main/bosi*
Disallow: /test*
Disallow: /search
Disallow: /nsearch
Disallow: /earlybird
Disallow: /economy/realty/

User-agent: GPTBot
Disallow: /

User-agent: DeepSeekBot
Disallow: /

Sitemap: https://www.chosun.com/arc/outboundfeeds/news-sitemap/?outputType=xml
Sitemap: https://www.chosun.com/arc/outboundfeeds/sitemap/section/index/?outputType=xml
A+
Domain Intelligence
chosun.com — via Whois Corp., 30 years, 11 months old, hosted on AWS
PASS
chosun.com — via Whois Corp., 30 years, 11 months old, hosted on AWS
Info::
Domain registered until Oct 9, 2026 (5 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: Whois Corp.
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

115 days

October 9, 2026

SSL certificate

74 days

Issued by DigiCert Inc

Domain age

30 years, 11 months

Registered October 10, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.35.113.248

Registrar

Whois Corp.

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 Whois Corp.
Created October 10, 1995 (30 years, 11 months ago)
Expires October 9, 2026 (5 months)
Last Updated August 26, 2025
Name Servers ns-1288.awsdns-33.org, ns-1618.awsdns-10.co.uk, ns-343.awsdns-42.com, ns-542.awsdns-03.net
DNSSEC Not enabled
Hosting
IP Address 3.35.113.248
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.9s)

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

Connection waterfall

DNS Lookup 110 ms TCP Connect 66 ms TLS Handshake 135 ms Server Processing 67 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