Security report for kakaobank.com
카카오뱅크 · Finance · South Korea
Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.
카카오뱅크는 2013년에 설립된 대한민국의 대표적인 디지털 전문은행으로, 모바일 중심의 금융 서비스를 제공하며 입출금통장, 예금, 적금, 대출, 투자, 카드 등 다양한 금융상품을 운영합니다. 사용자 친화적인 UX와 IT 기술을 활용한 보안 및 인증 시스템을 갖추고 있으며, 국내 시장에서 강력한 입지를 확보하고 있습니다. 기술적으로는 Google Analytics, Google Tag Manager, reCAPTCHA, Kakao Maps SDK 등 최신 웹 기술을 활용하여 안정적이고 편리한 서비스를 제공합니다. 보안 측면에서는 HTTPS 적용, CSRF 토큰, 클라이언트 전송 제한 도메인 상태 등 기본적인 보안 조치를 갖추었으나, DNSSEC 미적용 및 명시적 보안 헤더 부재는 개선 여지가 있습니다. 개인정보 처리방침과 이용약관 등 법적 문서가 잘 갖추어져 있으나, 쿠키 동의 메커니즘 부재는 개인정보 보호 측면에서 보완이 필요합니다. 전반적으로 신뢰할 수 있는 대형 금융기관 웹사이트로 평가되며, 보안 및 개인정보 보호 강화를 통해 더욱 견고한 디지털 금융 서비스를 제공할 수 있을 것입니다.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 53/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (j) Multi-factor authentication and secured communications: Not visible from outside
This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
Priority findings
4 findings rated critical or high. Fix these first.
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
Missing Content-Security-Policy header
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
- ASVS V3.4.3
- OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
- High
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- High
No Cookie Policy found
GDPR requires clear information about cookie usage
What to do: Add a dedicated cookie policy explaining cookie usage and purposes
- High
No Cookie Consent Banner found
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
Weak Protocols Supported
Server supports weak protocols: TLSv1.1
What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions
- CWE-327
- OWASP A04:2025
- ASVS V12.1.1
- RFC 8996
- RFC 7568
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching kakaobank.com
This scan found 20 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 67
- Security headers
- 70
- Email security
- 85
- DNS health
- 70
- Network security
- 100
- GDPR outside view
- 53
- Average
- 74
Not counted
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- DNSSEC 활성화를 통해 도메인 네임 시스템 보안을 강화할 것
- Content Security Policy(CSP), Strict-Transport-Security(HSTS), X-Frame-Options 등 보안 헤더를 추가 적용할 것
- 웹사이트에 명확한 보안 사고 대응 연락처 및 정책을 게시할 것
- 쿠키 사용에 대한 명확한 동의 메커니즘을 도입하여 개인정보 보호 규정을 준수할 것
- 정기적인 보안 점검과 취약점 스캐닝을 통해 라이브러리 및 스크립트의 취약성 여부를 관리할 것
Contact details published on the site
- Legal name
- (주)카카오뱅크
- Registration number
- 375-88-00197
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- 카카오뱅크
- Description
- 카카오뱅크는 모바일 기반의 디지털 은행으로, 간편한 계좌개설, 다양한 금융상품(입출금통장, 예금, 적금, 대출, 투자, 카드 등)을 제공하며, 사용자 친화적인 UX와 IT 기술을 활용한 보안 및 인증 서비스를 운영합니다.
- Key services
- 입출금통장, 예금 및 적금, 대출상품, 투자 및 외환 서비스, 체크카드, 사업자 금융 서비스, 인증서 서비스
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- Google Analytics, Google Tag Manager, reCAPTCHA v3, Kakao Maps SDK, Moment.js, ScrollReveal.js, jQuery
- Platforms
- Web
- Performance
- moderate
- Mobile
- excellent
- Accessibility
- excellent
- SEO
- good
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- CSRF token present
- reCAPTCHA v3 integration
- Use of clientTransferProhibited domain status
Analytics and tracking
- Services
- Google Analytics, Google Tag Manager
- Tracking level
- moderate
- Privacy practices
- basic
Advertising
- Transparency
- good
Site quality
- Design
- excellent
- User experience
- excellent
- Content relevance
- excellent
- Navigation
- excellent
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is fully accessible and professionally designed.
- Content is comprehensive and well-structured with clear navigation.
- Strong branding and consistent corporate identity.
- Use of modern web technologies and security best practices.
- No explicit cookie consent mechanism detected, which may affect privacy compliance.
- No explicit security or incident response contact information found.
- WHOIS data supports legitimacy and business consistency.
- Multiple official social media channels linked.
- Certifications for web accessibility and web trust are displayed.
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 79/100Low25 findingsView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with kakaobank.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review kakaobank.com.