Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
dayz-servers.org scored 75/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security, Security Headers, Cookie Security. Positive signals: MX Records & Mail Provider, TLS Configuration, DNS Configuration all passed.
2 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 dayz-servers.org compares
Grade distribution across 2445 companies we've scanned. dayz-servers.org scores better than 55% of them.
75
A+
24
A
180
A-
187
B+
71
B
342
B-
118
C+
112
C
308
C-
114
D+
93
D
226
D-
595
F
dayz-servers.org — Grade C (75/100)
2445 companies scanned
Security checks
Each check inspects a different part of dayz-servers.org's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Security Headers
2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Cookie Security
Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (PHPSESSID); 1/1 cookie(s) missing HttpOnly flag (PHPSESSID); 1/1 cookie(s) missing SameSite attribute (PHPSESSID).
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 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.
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.
MX Records & Mail Provider
Strengths: Mail handled by spool.mail.gandi.net; 2 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DNS Configuration
Strengths: 2 nameservers configured (gina.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. Missing preload directive.
CVE Exposure
Detected technologies: cloudflare, PleskLin. (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, 33 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 dayz-servers.org's security grade, ranked by impact.
1
Set up email authentication (DKIM)
Without email authentication, anyone can send emails that appear to come from dayz-servers.org. This is the most common vector for phishing attacks targeting employees and customers. DKIM is not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on dayz-servers.org: CSP, 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 a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://dayz-servers.org | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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). Issues: DMARC policy is 'none' (monitoring only, no enforcement); No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 ip4:141.94.167.11 include:_mailcust.gandi.net include:amazonses.com ~all
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=15552000s (180 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 33 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
Enabled
Strengths: 2 nameservers configured (gina.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.