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).
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 (nataly.ns.cloudflare.com., carl.ns.cloudflare.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Strengths: 2 nameservers configured (nataly.ns.cloudflare.com., carl.ns.cloudflare.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
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.
Certificate Hygiene
Strengths: Certificate valid, 77 days remaining; Issued by Let's Encrypt; 42 certificates logged in CT. Issues: Certificates issued by 4 different CAs (threshold: 3 for 42 logged certs) — possible misconfiguration or shadow IT.
Strengths: Certificate valid, 77 days remaining; Issued by Let's Encrypt; 42 certificates logged in CT. Issues: Certificates issued by 4 different CAs (threshold: 3 for 42 logged certs) — possible misconfiguration or shadow IT.
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.
HSTS Header
Could not fetch https://crdpro.org — connection failed or timed out.
Could not fetch https://crdpro.org — connection failed or timed out.
Security Headers
Could not fetch https://crdpro.org — connection failed or timed out.
Could not fetch https://crdpro.org — connection failed or timed out.
Cookie Security
Could not fetch crdpro.org to analyze cookies: HTTPSConnectionPool(host='crdpro.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<HTTPSConnection(host='crdpro.org', port=443) at 0x71396ec2f610>, 'Connection to crdpro.org timed out. (connect timeout=10)'))
Could not fetch crdpro.org to analyze cookies: HTTPSConnectionPool(host='crdpro.org', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<HTTPSConnection(host='crdpro.org', port=443) at 0x71396ec2f610>, 'Connection to crdpro.org timed out. (connect timeout=10)'))
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.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
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.
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
1+ items
Steps to improve crdpro.org'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 crdpro.org. 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
crdpro.org scored 48/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. Positive signals: MX Records & Mail Provider, Known Breaches, CVE Exposure 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 crdpro.org compares
Grade distribution across 2678 companies we've scanned. crdpro.org scores better than 14% 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
crdpro.org — Grade F (48/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
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://crdpro.org — connection failed or timed out.
SSL Certificate
Issues
Strengths: Certificate valid, 77 days remaining; Issued by Let's Encrypt; 42 certificates logged in CT. Issues: Certificates issued by 4 different CAs (threshold: 3 for 42 logged certs) — possible misconfiguration or shadow IT.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (nataly.ns.cloudflare.com., carl.ns.cloudflare.com.); Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Similar companies
Other domains with comparable security profiles.
