Security checks — sorted by severity
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.
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 (chin.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Strengths: 2 nameservers configured (chin.ns.cloudflare.com., hugh.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: DKIM configured (selectors: mail). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement.
Strengths: DKIM configured (selectors: mail). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement.
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.
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.
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have SameSite attribute. Issues: 2/2 cookie(s) missing HttpOnly flag (PHPSESSID, kt_ips).
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have SameSite attribute. Issues: 2/2 cookie(s) missing HttpOnly flag (PHPSESSID, kt_ips).
Certificate Hygiene
Strengths: Certificate valid, 209 days remaining; Issued by Sectigo Limited; 180 certificates logged in CT. Issues: Certificates issued by 6 different CAs (threshold: 5 for 180 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Strengths: Certificate valid, 209 days remaining; Issued by Sectigo Limited; 180 certificates logged in CT. Issues: Certificates issued by 6 different CAs (threshold: 5 for 180 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
MX Records & Mail Provider
Strengths: Mail handled by mail.pornid.xxx; 2 MX record(s) configured; Multiple MX records provide redundancy.
Strengths: Mail handled by mail.pornid.xxx; 2 MX record(s) configured; Multiple MX records provide redundancy.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
1+ items
Steps to improve pornid.xxx's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for pornid.xxx 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.
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.pornid.xxx
See all 4 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
pornid.xxx scored 65/100, meeting baseline requirements but with 9 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: MX Records & Mail Provider, Known Breaches, HSTS Header all passed.
5 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 pornid.xxx compares
Grade distribution across 2678 companies we've scanned. pornid.xxx scores better than 33% 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
pornid.xxx — Grade D (65/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
p=none
Strengths: DKIM configured (selectors: mail). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua); SPF record uses neutral (?all) — no real enforcement.
SPF Record
Present
v=spf1 a mx include:_spf.smtp.advancedhosters.com ?all
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 209 days remaining; Issued by Sectigo Limited; 180 certificates logged in CT. Issues: Certificates issued by 6 different CAs (threshold: 5 for 180 logged certs) — possible misconfiguration or shadow IT. 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 (chin.ns.cloudflare.com., hugh.ns.cloudflare.com.); 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.
