Is rogo.ai safe to use as a vendor?

rogo.ai scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 10 checks passed, 4 warnings, 1 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does rogo.ai use?

rogo.ai uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does rogo.ai have SPF configured?

Yes. SPF record found: v=spf1 include:_spf.google.com include:_spf.salesforce.com include:_spf.intacct....

Does rogo.ai have security headers configured?

rogo.ai has 1 of 5 recommended security headers. Present: X-Content-Type-Options. Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does rogo.ai use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.

Has rogo.ai been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does rogo.ai have known CVE vulnerabilities?

Detected technologies: Framer/26, Proxy/CDN, Framer/c81289c. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No high or critical CVEs found for detected versions.

Is rogo.ai's SSL certificate valid?

Yes. Strengths: Certificate valid, 149 days remaining; Issued by Amazon.

Does rogo.ai have DNSSEC enabled?

Yes. Strengths: 4 nameservers configured (ns-1073.awsdns-06.org, ns-1833.awsdns-37.co.uk, ns-635.awsdns-15.net, ns-170.awsdns-21.com); NS records span 4 providers (awsdns-06.org, co.uk, awsdns-15.net, awsdns-21.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 5 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 4 A record(s).

rogo.ai Security Report — Grade B- (82/100)

Q: Does rogo.ai have DMARC configured?

Yes. rogo.ai's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Featured in our Forbes AI 50 security study: see how rogo.ai compares with the other 49 →

B-

Trust rating

Good · 82/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

DNS Configuration

TLS Configuration

TLS Protocol Support

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: about 1 day

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned September 28, 2026

Score

100 75 50 25 0

B-

rogo.ai

82/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

5 items need attention

10 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for rogo.ai is partly set up, but there are gaps: your DMARC policy is set to monitor-only, so nothing actually gets blocked yet. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Change your DMARC policy from "none" to "quarantine" in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) — this moves suspicious mail to spam instead of just watching it happen. Your current record with just that change:

v=DMARC1; p=quarantine; rua=mailto:[email protected], mailto:[email protected]

2Double-check it's live: search "dmarc record checker" and enter rogo.ai.

Email authentication guide

Report unlocked.

View all 10 passed checks

MX Records & Mail Provider

DNS Configuration

TLS Configuration

TLS Protocol Support

HSTS Header

Cookie Security

Known Breaches

Subprocessors & Tech Stack

CVE Exposure

Certificate Hygiene

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

791 companies · LynxRadar ranking

Blocking Issues

1/5 present

Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

High Priority

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Warn

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.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆