Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
edyst.com scored 45/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Positive signals: Known Breaches, CVE Exposure all passed.
3 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 edyst.com compares
Grade distribution across 2378 companies we've scanned. edyst.com scores better than 12% 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
edyst.com — Grade F (45/100)
2378 companies scanned
Security checks
Each check inspects a different part of edyst.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (neil.ns.cloudflare.com., demi.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2, k1). Issues: No DMARC record found — email spoofing is not prevented.
Certificate Hygiene
Issues: Could not retrieve certificate details.
TLS Configuration
Could not complete TLS handshake with edyst.com:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
HSTS Header
Could not fetch https://edyst.com — connection failed or timed out.
Security Headers
Could not fetch https://edyst.com — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
3 items
Steps to improve edyst.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for edyst.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.edyst.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for edyst.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 edyst.com
3
Review certificate configuration
Certificate issues found for edyst.com: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
Issues detected
Could not complete TLS handshake with edyst.com:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
DMARC Policy
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2, k1). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:mailgun.org ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://edyst.com — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (neil.ns.cloudflare.com., demi.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.