Infrastructure - https://kakao.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 3460 ms total

FIX

2 redirect(s), 3460 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://kakao.com

Redirect overhead: 3460 ms total

Got: 3460 ms

Cross-domain redirect detected

https://kakao.com

860 ms · HTTP/1.1

302

https://www.kakaocorp.com

1660 ms · HTTP/1.1

301

https://www.kakaocorp.com/page/

940 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol
1	https://kakao.com	302	860 ms	HTTP/1.1
2	https://www.kakaocorp.com	301	1660 ms	HTTP/1.1
3	https://www.kakaocorp.com/page/	200	940 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

D

Crawlability

Action

robots.txt present, no sitemap

FIX

robots.txt present, no sitemap

robots.txt is present

Got: 147 bytes

robots.txt blocks all crawlers

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 147 B Sitemaps referenced 0 User-agents GoogleOther, * Blocking Yes — all crawlers blocked

User-agent: GoogleOther
Disallow: /
Allow :  /.well-known/privacy-sandbox-attestations.json

User-agent: *
Disallow: /
Allow : /$
Allow : /ads.txt

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.

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

B

URL Variants

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

REVIEW

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP version does not redirect to HTTPS

Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

302https://www.kakao.com/

200https://kakao.com/

Preferred variant: non-www

HTTP → HTTPS

302http://kakao.com/ → //www.kakaocorp.com

HTTP version does not redirect to HTTPS

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

22 ms

TCP Connect

276 ms

TLS Handshake

280 ms

Time to First Byte

857 ms

Total Time

858 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 276 ms TLS Handshake 280 ms Server Processing 280 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

161 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

161

days left

0d 30d 60d 90d+

Recommended actions

Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

3 A records, 289 ms lookup

PASS

3 A records, 289 ms lookup

Resolves to 3 IPv4 address(es)

Got: 121.53.93.60, 211.242.11.41, 211.249.251.46

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns1.kakao.com, ns2.kakao.com

4 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 (289 ms)

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

Got: 289 ms

A	121.53.93.60, 211.242.11.41, 211.249.251.46
AAAA	—
CNAME	—
NS	ns1.kakao.com, ns2.kakao.com
MX	10 mx1.kakao.com 10 mx3.kakao.com 10 mx2.kakao.com 10 mx4.kakao.com
TXT	google-site-verification=puTbVVviI88yMTQf88LO_8L9y2pdlP6bI98p3qO0XdA rovag_verification_token=D6FFB92C646749648E94FA00D3D0584D google-site-verification=Qljvs5WkxGiGJL4EzIB-BmmzJ9aOivVkrm0PrmWSZss google-site-verification=WO3BhsNNCPrfc_jvi4eOZoqNPaY2rw1o95tmtXUXXG8 google-site-verification=rk_MxsjBvzXTt_F1ZI6877Z3V2dAH3B1BMc7bmdcWng google-site-verification=OVqf3b_fME-xxHijfDRV8CIZmbAbauZlS97ScYKYy7I SPF v=spf1 ip4:103.246.58.76 ip4:103.246.58.77 ip4:103.246.58.78 ip4:103.246.58.79 i...
CAA	Lookup not available with standard resolver

Resolved in 289 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.

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+

Domain Intelligence

kakao.com — via Megazone Corp., dba HOSTING.KR, 29 years, 8 months old, hosted on AS18160-AS-KR Kakao Corp, KR

PASS

kakao.com — via Megazone Corp., dba HOSTING.KR, 29 years, 8 months old, hosted on AS18160-AS-KR Kakao Corp, KR

Domain registered until Dec 28, 2026 (8 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: Megazone Corp., dba HOSTING.KR

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: AS18160-AS-KR Kakao Corp, KR

Got: AS18160

Domain expiry

195 days

December 28, 2026

SSL certificate

161 days

Issued by DigiCert Inc

Domain age

29 years, 8 months

Registered December 29, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AS18160-AS-KR Kakao Corp, KR

ASN AS18160

121.53.93.60

Registrar

Megazone Corp., dba HOSTING.KR

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 Megazone Corp., dba HOSTING.KR

Created December 29, 1996 (29 years, 8 months ago)

Expires December 28, 2026 (8 months)

Last Updated December 17, 2025

Name Servers ns1.kakao.com, ns2.kakao.com

DNSSEC Not enabled

Hosting

IP Address 121.53.93.60

ASN AS18160 (AS18160-AS-KR Kakao Corp, KR)

Provider AS18160-AS-KR Kakao Corp, KR

Data source: rdap (0.5s)

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