Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
x-zell.com scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, DNS Configuration, Certificate Hygiene 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 x-zell.com compares
Grade distribution across 2378 companies we've scanned. x-zell.com scores better than 72% of them.
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
x-zell.com — Grade B- (82/100)
2378 companies scanned
Security checks
Each check inspects a different part of x-zell.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-b4.googledomains.com., ns-cloud-b2.googledomains.com., ns-cloud-b1.googledomains.com., ns-cloud-b3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Certificate Hygiene
Strengths: Certificate valid, 52 days remaining; Issued by Let's Encrypt.
HSTS Header
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
CVE Exposure
Detected technologies: openresty. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
2 items
Steps to improve x-zell.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for x-zell.com but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.x-zell.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Upgrade to TLS 1.3
x-zell.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect x-zell.com:443 -tls1_3
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 52 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-b4.googledomains.com., ns-cloud-b2.googledomains.com., ns-cloud-b1.googledomains.com., ns-cloud-b3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.