Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
enmax.com scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: TLS Protocol Support, TLS Configuration, DNS CAA Records all passed.
2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How enmax.com compares
Grade distribution across 2612 companies we've scanned. enmax.com scores better than 81% of them.
85
A+
25
A
189
A-
197
B+
75
B
362
B-
132
C+
114
C
333
C-
121
D+
95
D
256
D-
628
F
enmax.com — Grade B+ (88/100)
2612 companies scanned
Security checks
Each check inspects a different part of enmax.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
2/5 security headers present. Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
MX Records & Mail Provider
Strengths: Mail handled by Microsoft 365; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
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.
DNS Configuration
Strengths: 2 nameservers configured (clay.ns.cloudflare.com., sofia.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
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.
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.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS CAA Records
Strengths: CAA records configured (13 record(s)); Authorized CAs: comodoca.com, digicert.com; cansignhttpexchanges=yes, entrust.net, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com; Violation reporting (iodef) configured.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: selector1, s1, s2).
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
CVE Exposure
Detected technologies: cloudflare, Next.js. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 47 days remaining; Issued by Google Trust Services. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
2 items
Steps to improve enmax.com's security grade, ranked by impact.
1
Add missing security headers (X-Frame-Options, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on enmax.com: X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://enmax.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for enmax.com 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 .com TLD
4
Verify: dig +dnssec enmax.com
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
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: selector1, s1, s2).
SPF Record
Present
v=spf1 include:enmax.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
Security Headers
2/5 present
Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. preload present.
SSL Certificate
Valid
Strengths: Certificate valid, 47 days remaining; Issued by 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: 2 nameservers configured (clay.ns.cloudflare.com., sofia.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.