Security checks — sorted by severity
DMARC / Email Security
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Security Headers
1/5 security headers present. Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
1/5 security headers present. Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have SameSite attribute. Issues: 1/1 cookie(s) missing Secure flag (PHPSESSID); 1/1 cookie(s) missing HttpOnly flag (PHPSESSID).
Strengths: 1 cookie(s) analyzed; All cookies have SameSite attribute. Issues: 1/1 cookie(s) missing Secure flag (PHPSESSID); 1/1 cookie(s) missing HttpOnly flag (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.
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.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
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.
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
CVE Exposure
Detected technologies: nginx, PHP/7.4.33. 1 medium-severity CVE(s) found. Review recommended.
Detected technologies: nginx, PHP/7.4.33. 1 medium-severity CVE(s) found. Review recommended.
MX Records & Mail Provider
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
DNS Configuration
Strengths: 4 nameservers configured (pns103.cloudns.net., pns102.cloudns.net., pns101.cloudns.net., pns104.cloudns.net.); DNSSEC enabled; Zone transfers properly restricted.
Strengths: 4 nameservers configured (pns103.cloudns.net., pns102.cloudns.net., pns101.cloudns.net., pns104.cloudns.net.); DNSSEC enabled; Zone transfers properly restricted.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Certificate Hygiene
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt; 78 certificates logged in CT.
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt; 78 certificates logged in CT.
Recommended actions
1+ items
Steps to improve outdoorporn.one's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF, DKIM)
Without email authentication, anyone can send emails that appear to come from outdoorporn.one. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF, DKIM are not configured.
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 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
outdoorporn.one scored 57/100 and does not meet the minimum security posture threshold. The most critical issue is: Set up email authentication (DMARC, SPF, DKIM). This must be addressed before the vendor can be approved for procurement or data processing activities.
Critical gaps in: DMARC / Email Security, Security Headers, Cookie Security. Positive signals: MX Records & Mail Provider, DNS Configuration, 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 outdoorporn.one compares
Grade distribution across 2678 companies we've scanned. outdoorporn.one scores better than 18% 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
outdoorporn.one — Grade F (57/100)
2678 companies scanned
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
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 68 days remaining; Issued by Let's Encrypt; 78 certificates logged in CT.
DNSSEC
Enabled
Strengths: 4 nameservers configured (pns103.cloudns.net., pns102.cloudns.net., pns101.cloudns.net., pns104.cloudns.net.); DNSSEC enabled; Zone transfers properly restricted.
Similar companies
Other domains with comparable security profiles.
