Security checks — sorted by severity
TLS Configuration
TLS certificate verification failed on joefortunepokies.win: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'joefortunepokies.win'. (_ssl.c:1081)
TLS certificate verification failed on joefortunepokies.win: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'joefortunepokies.win'. (_ssl.c:1081)
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.
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 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.
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.
DNS Configuration
Strengths: 2 nameservers configured (ns1.cdnetdns.net., ns2.cdnetdns.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Strengths: 2 nameservers configured (ns1.cdnetdns.net., ns2.cdnetdns.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: DMARC has no aggregate report URI (rua); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: DMARC has no aggregate report URI (rua); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
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.
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.
Certificate Hygiene
Issues: Could not retrieve certificate details.
Issues: Could not retrieve certificate details.
HSTS Header
Could not fetch https://joefortunepokies.win — connection failed or timed out.
Could not fetch https://joefortunepokies.win — connection failed or timed out.
Security Headers
Could not fetch https://joefortunepokies.win — connection failed or timed out.
Could not fetch https://joefortunepokies.win — connection failed or timed out.
Cookie Security
Could not fetch joefortunepokies.win to analyze cookies: HTTPSConnectionPool(host='joefortunepokies.win', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'joefortunepokies.win'. (_ssl.c:1081)")))
Could not fetch joefortunepokies.win to analyze cookies: HTTPSConnectionPool(host='joefortunepokies.win', port=443): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'joefortunepokies.win'. (_ssl.c:1081)")))
MX Records & Mail Provider
Strengths: Mail handled by Mimecast; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Mimecast.
Strengths: Mail handled by Mimecast; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Mimecast.
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.
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.
Known Breaches
No known breaches found in public disclosure databases.
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.
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
1+ items
Steps to improve joefortunepokies.win's security grade, ranked by impact.
1
Upgrade TLS — deprecated protocol in use
joefortunepokies.win is using unknown, which is deprecated and has known vulnerabilities. This is a compliance failure under PCI-DSS, HIPAA, and NIST guidelines. Immediate upgrade to TLS 1.2 minimum (TLS 1.3 preferred) is required.
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
How to fix this
1
Disable TLS 1.0 and 1.1 in your web server configuration
2
Enable TLS 1.2 and 1.3: ssl_protocols TLSv1.2 TLSv1.3
3
Remove weak ciphers: ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:...'
4
Verify: openssl s_client -connect joefortunepokies.win:443 -tls1_2
See all 3 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
joefortunepokies.win scored 45/100 and does not meet the minimum security posture threshold. The most critical issue is: Upgrade TLS — deprecated protocol in use. This must be addressed before the vendor can be approved for procurement or data processing activities.
Critical gaps in: TLS Configuration. Positive signals: MX Records & Mail Provider, TLS Protocol Support, Known Breaches all passed.
4 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 joefortunepokies.win compares
Grade distribution across 2678 companies we've scanned. joefortunepokies.win scores better than 11% of them.
88
A+
28
A
194
A-
200
B+
75
B
376
B-
137
C+
117
C
347
C-
123
D+
96
D
265
D-
632
F
joefortunepokies.win — Grade F (45/100)
2678 companies scanned
At a glance
Key data points from the scan.
TLS Version
Issues detected
TLS certificate verification failed on joefortunepokies.win: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'joefortunepokies.win'. (_ssl.c:1081)
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: DMARC has no aggregate report URI (rua); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 mx a include:de._netblocks.mimecast.com ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://joefortunepokies.win — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns1.cdnetdns.net., ns2.cdnetdns.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Similar companies
Other domains with comparable security profiles.
