Security checks — sorted by severity
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
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.
MX Records & Mail Provider
Strengths: Mail handled by _dc-mx.efeba0512758.dixrix.net; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
Strengths: Mail handled by _dc-mx.efeba0512758.dixrix.net; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
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 (thaddeus.ns.cloudflare.com., zita.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Strengths: 2 nameservers configured (thaddeus.ns.cloudflare.com., zita.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.
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.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
Security Headers
4/5 security headers present. Missing: CSP.
4/5 security headers present. Missing: CSP.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
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.
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.
Certificate Hygiene
Strengths: Certificate valid, 67 days remaining; Issued by Google Trust Services; 88 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Strengths: Certificate valid, 67 days remaining; Issued by Google Trust Services; 88 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
1+ items
Steps to improve dixrix.net's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on dixrix.net. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://dixrix.net | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all 2 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
dixrix.net scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: TLS Configuration, TLS Protocol Support, Security Headers 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 dixrix.net compares
Grade distribution across 2678 companies we've scanned. dixrix.net scores better than 64% 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
dixrix.net — Grade B- (80/100)
2678 companies scanned
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 +a +mx +ip4:193.111.62.196 ~all
Security Headers
4/5 present
Missing: CSP
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 67 days remaining; Issued by Google Trust Services; 88 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt. 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 (thaddeus.ns.cloudflare.com., zita.ns.cloudflare.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Similar companies
Other domains with comparable security profiles.
