Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
cointent.com scored 68/100, meeting baseline requirements but with 2 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, DNS Configuration, TLS Configuration all passed.
2 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 cointent.com compares
Grade distribution across 2378 companies we've scanned. cointent.com scores better than 38% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
cointent.com — Grade D+ (68/100)
2378 companies scanned
Security checks
Each check inspects a different part of cointent.com'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); DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented.
Certificate Hygiene
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
HSTS Header
Could not fetch https://cointent.com — connection failed or timed out.
Security Headers
Could not fetch https://cointent.com — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 2 nameservers configured (cody.ns.cloudflare.com., lola.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
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.
Recommended actions
2 items
Steps to improve cointent.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for cointent.com 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.
Compliance impact
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.cointent.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for cointent.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
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
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 ip4:54.200.30.235 ip4:54.187.138.80 ip4:54.213.32.130 a:cointent.com a:api.cointent.com a:mai
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://cointent.com — connection failed or timed out.
SSL Certificate
Issues
Strengths: Certificate valid, 64 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (cody.ns.cloudflare.com., lola.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.