Skip to main content

Security report for yesbank.in

YES BANK · Finance · India

Medium risk. 6 critical or high findings in GDPR outside view and SSL/TLS.

Security score

53/100

Risk levelMedium

0–100, higher is better. How it is calculated

YES BANK is a major Indian financial institution providing a range of banking services including retail, corporate, and investment banking. The website content analyzed is minimal and primarily technical, with no visible privacy or cookie policies, contact information, or user-facing content. The domain and DNS data confirm the legitimacy of the bank's online presence. Technically, the site uses Oracle Cloud infrastructure and Akamai CDN, with multiple third-party analytics and advertising integrations. However, the absence of a valid SSL certificate is a critical security flaw, severely impacting the site's security posture and user trust. Security headers are well configured but cannot compensate for the lack of HTTPS. Privacy compliance is poor due to missing policies and consent mechanisms. Overall, the site requires urgent remediation of SSL issues and improved transparency in privacy and contact information to meet industry standards.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

6 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

  2. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

Need hands-on remediation? Email guard@offseq.com

Keep watching yesbank.in

This scan found 14 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
0
Security headers
80
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
53

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention yesbank.in, from OffSeq Breach.

Total records
8,644
Employees
373
Customers
7,774
Third parties
497
Weak passwords
30%

Latest record dated 2026-06-15 · 157 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for yesbank.in.

Select it in the checkout above.

Masked preview

  • –yesbank.in2026-06-15
  • –yesbank.in2026-06-14
  • –sts.yesbank.in2026-06-14
  • –sts.yesbank.in2026-06-14
  • –sts.yesbank.in2026-06-13

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

YES BANK operates in the competitive Indian banking sector with a focus on digital banking services. The business model centers on providing comprehensive financial products to retail and corporate customers. The website's technical infrastructure leverages cloud and CDN technologies to support scalability and performance, though performance data is unavailable. The extensive use of advertising and analytics tools indicates a focus on marketing and customer insights. The lack of visible contact or policy pages online suggests potential gaps in customer engagement and regulatory compliance. The domain registration data aligns well with the bank's identity, supporting trustworthiness. Strategic partnerships or subsidiaries are not evident from the data provided.

Security posture

The security posture of the website is currently weak due to the absence of a valid SSL/TLS certificate, which is a fundamental requirement for any banking website. While security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options are implemented, the disabled TLS protocols and lack of strong cipher suites expose the site to potential risks. The X-XSS-Protection header is disabled, reducing protection against cross-site scripting attacks. No incident response or vulnerability disclosure information is found, indicating limited transparency in security management. The site also lacks cookie consent mechanisms and privacy policies, which are critical for GDPR and other regulatory compliance. Immediate action is needed to install valid SSL certificates and enhance privacy and security policies.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS and secure user data.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites to improve encryption strength.
  3. Implement and publicly display comprehensive privacy and cookie policies with consent mechanisms.
  4. Add clear contact information including emails and phone numbers for customer support and security incident reporting.
  5. Enable security headers fully, including X-XSS-Protection or modern CSP rules, and improve HSTS settings with includeSubDomains and preload.
  6. Establish a vulnerability disclosure policy and incident response contact channels to enhance security transparency.
  7. Improve website content quality and navigation to enhance user experience and trust.
Technical notes

Notes

The website is hosted on Oracle Cloud infrastructure with Akamai CDN integration, indicating a robust hosting environment. The tech stack includes JavaScript and Oracle Cloud delivery scripts. However, the absence of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risk. The site lacks visible CMS or frameworks, suggesting a custom or proprietary platform. Performance metrics are unavailable, but the presence of multiple third-party analytics and advertising scripts may impact load times. Mobile optimization and accessibility are basic, with minimal content and no visible forms or interactive elements. SEO optimization is limited due to missing meta tags and structured data. Overall, modernization efforts should focus on security, content enrichment, and compliance.
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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with yesbank.in. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review yesbank.in.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.