Overview
Findings
Actions
Details
Related
B-
82 / 100

beneficios.interbank.pe

Security report · Scanned March 09, 2026

Checks
14
Passed
9
Warnings
4
Critical
1
AI-Generated Summary
What this means

beneficios.interbank.pe scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.

Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.

2 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

How beneficios.interbank.pe compares

Grade distribution across 2378 companies we've scanned. beneficios.interbank.pe scores better than 72% of them.

72th percentile
0 Percentile rank 100
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
beneficios.interbank.pe — Grade B- (82/100) 2378 companies scanned
Security checks

Each check inspects a different part of beneficios.interbank.pe's public security setup. Green means healthy, yellow needs attention, red is a problem.

DMARC / Email Security
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Problem
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
Needs work
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
Needs work
DNS Configuration
Strengths: DNSSEC enabled. Issues: No NS records found (unusual).
Needs work
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
Needs work
MX Records & Mail Provider
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Healthy
HSTS Header
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. Missing preload directive.
Healthy
Security Headers
4/5 security headers present. Missing: CSP.
Healthy
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Healthy
Certificate Hygiene
Strengths: Certificate valid, 158 days remaining; Issued by DigiCert Inc; 8 certificates logged in CT; Certificates from 2 CAs: DigiCert Inc, Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Healthy
Recommended actions
2 items

Steps to improve beneficios.interbank.pe's security grade, ranked by impact.

1
Set up email authentication (DMARC, SPF, DKIM)
Impact: 1–2 Days
CRITICAL
Without email authentication, anyone can send emails that appear to come from beneficios.interbank.pe. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
2
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for beneficios.interbank.pe can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .pe TLD
4
Verify: dig +dnssec beneficios.interbank.pe
At a glance

Key data points from the scan.

TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 158 days remaining; Issued by DigiCert Inc; 8 certificates logged in CT; Certificates from 2 CAs: DigiCert Inc, Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: DNSSEC enabled. Issues: No NS records found (unusual).