Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
onegraph.com scored 40/100 and does not meet the minimum security posture threshold. The most critical issue is: Set up email authentication (DMARC, SPF). This must be addressed before the vendor can be approved for procurement or data processing activities.
Critical gaps in: DMARC / Email Security, TLS Configuration. Positive signals: Known Breaches, DNS Configuration, CVE Exposure all passed.
3 action items identified, including 2 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How onegraph.com compares
Grade distribution across 2378 companies we've scanned. onegraph.com scores better than 11% 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
onegraph.com — Grade F (40/100)
2378 companies scanned
Security checks
Each check inspects a different part of onegraph.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DKIM configured (selectors: k1). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
TLS Configuration
TLS certificate verification failed on www.onegraph.com: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'www.onegraph.com'. (_ssl.c:1081)
Certificate Hygiene
Issues: Could not retrieve certificate details.
HSTS Header
Could not fetch https://www.onegraph.com — connection failed or timed out.
Security Headers
Could not fetch https://www.onegraph.com — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-a3.googledomains.com., ns-cloud-a4.googledomains.com., ns-cloud-a2.googledomains.com., ns-cloud-a1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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
3 items
Steps to improve onegraph.com's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF)
Without email authentication, anyone can send emails that appear to come from onegraph.com. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF are 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
Upgrade TLS — deprecated protocol in use
onegraph.com is using unknown, which is deprecated and has known vulnerabilities. This is a compliance failure under PCI-DSS, HIPAA, and NIST guidelines. Immediate upgrade to TLS 1.2 minimum (TLS 1.3 preferred) is required.
Compliance impact
PCI-DSS 4.0Req 4.2.1
Strong cryptography for transmission
NIST 800-52r2§3.4
TLS 1.0/1.1 must not be used
HIPAA§164.312(e)
Transmission security
How to fix this
1
Disable TLS 1.0 and 1.1 in your web server configuration
2
Enable TLS 1.2 and 1.3: ssl_protocols TLSv1.2 TLSv1.3
3
Remove weak ciphers: ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:...'
4
Verify: openssl s_client -connect onegraph.com:443 -tls1_2
3
Review certificate configuration
Certificate issues found for onegraph.com: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
Issues detected
TLS certificate verification failed on www.onegraph.com: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'www.onegraph.com'. (_ssl.c:1081)
DMARC Policy
Not configured
Strengths: DKIM configured (selectors: k1). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://www.onegraph.com — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-a3.googledomains.com., ns-cloud-a4.googledomains.com., ns-cloud-a2.googledomains.com., ns-cloud-a1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.