Infrastructure - https://donga.com BeaverCheck Audit

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

Redirect Chain

1 redirect(s), 2615 ms total

REVIEW

1 redirect(s), 2615 ms total

Single redirect

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

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://donga.com

Redirect overhead: 2615 ms total

Got: 2615 ms

https://donga.com

1124 ms · HTTP/1.0

302

https://www.donga.com/

1491 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://donga.com	302	1124 ms	HTTP/1.0	BigIP
2	https://www.donga.com/	200	1491 ms	HTTP/1.1	Apache

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

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

C

URL Variants

Action

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.donga.com/

200https://donga.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

B

HTTP Probe Timing

Total 1439 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

319 ms

TCP Connect

280 ms

TLS Handshake

561 ms

Time to First Byte

1.44 s

Total Time

1.44 s

Connection waterfall

DNS Lookup 319 ms TCP Connect 280 ms TLS Handshake 561 ms Server Processing 280 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

205 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

205

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

PASS

1 A records, 319 ms lookup

Resolves to 1 IPv4 address(es)

Got: 210.115.155.100

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns.dongailbo.co.kr, ns0.donga.com

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 is slow (319 ms)

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

Got: 319 ms

A	210.115.155.100
AAAA	—
CNAME	—
NS	ns.dongailbo.co.kr, ns0.donga.com
MX	0 wmail.donga.com
TXT	SPF v=spf1 ip4:210.115.128.35 ip4:210.115.128.85 ip4:210.115.150.52 ip4:210.115.150.... MS=5DB54DF3B67BAD22F367C3319E358584FDC91BE8 MS=ms68197774
CAA	Lookup not available with standard resolver

Resolved in 319 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+

Crawlability

robots.txt present, sitemap with 658 URLs

PASS

robots.txt present, sitemap with 658 URLs

robots.txt is present

Got: 688 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 658 entries

robots.txt references sitemap

robots.txt 200 OK

Size 688 B Sitemaps referenced 4 User-agents * Blocking No — crawling allowed

User-agent: *

Allow: /news/Sports/article/

Disallow: /search

Disallow: /news/search

Disallow: /news/View

Disallow: /news/dongaars

Disallow: /NEWS

Disallow: /HUB

Disallow: /VOICE

Disallow: /ISSUE

Disallow: /BIZN

Disallow: /STUDIO

Disallow: /SPORTS

Disallow: /VODA

Disallow: /WEEKLY

Disallow: /WOMAN

Disallow: /SHINDONGA


#DaumWebMasterTool:6af926b3c34377464b5bd427ad530c7c714d0d5950fa49080ae66373d9c6e7cb:xUUuR78FZ7e9iXukGuOVLQ==


Sitemap: https://www.donga.com/sitemap/donga-newsmap.xml

Sitemap: https://image.donga.com/sitemap/donga-sitemap.xml

Sitemap: https://www.donga.com/sitemap/foreign-newsmap.xml

Sitemap: https://image.donga.com/sitemap/foreign-sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 658 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

donga.com — via Gabia, Inc., 30 years, 6 months old, hosted on KIXS-AS-KR Korea Telecom, KR

PASS

donga.com — via Gabia, Inc., 30 years, 6 months old, hosted on KIXS-AS-KR Korea Telecom, KR

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: Gabia, 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.

Hosting: KIXS-AS-KR Korea Telecom, KR

Got: AS4766

Domain expiry

284 days

March 27, 2027

SSL certificate

205 days

Issued by GlobalSign nv-sa

Domain age

30 years, 6 months

Registered March 26, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

KIXS-AS-KR Korea Telecom, KR

ASN AS4766

210.115.155.100

Registrar

Gabia, 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 Gabia, Inc.

Created March 26, 1996 (30 years, 6 months ago)

Expires March 27, 2027 (11 months)

Last Updated January 16, 2026

Name Servers ns.donga.com, ns0.donga.com

DNSSEC Not enabled

Hosting

IP Address 210.115.155.100

ASN AS4766 (KIXS-AS-KR Korea Telecom, KR)

Provider KIXS-AS-KR Korea Telecom, KR

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