Is prometheus-systems.co.za safe to use as a vendor?

prometheus-systems.co.za scored 78/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 8 checks passed, 5 warnings, 2 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does prometheus-systems.co.za use?

prometheus-systems.co.za uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does prometheus-systems.co.za have DMARC configured?

Yes. prometheus-systems.co.za's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: default).

Does prometheus-systems.co.za have SPF configured?

Yes. SPF record: v=spf1 +ip4:169.239.218.61 +include:_spf.tld-mx.com -all

Does prometheus-systems.co.za have security headers configured?

prometheus-systems.co.za has 0 of 5 recommended security headers. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Has prometheus-systems.co.za been involved in a data breach?

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

Does prometheus-systems.co.za have known CVE vulnerabilities?

Detected technologies: LiteSpeed. No version information exposed — CVE matching not possible (this is good practice).

Is prometheus-systems.co.za's SSL certificate valid?

Yes. Strengths: Certificate valid, 80 days remaining; Issued by Let's Encrypt; 25 certificates logged in CT; Certificates from 2 CAs: Google Trust Services, Let's Encrypt.

prometheus-systems.co.za Security Report — Grade C+ (78/100)

Q: Does prometheus-systems.co.za use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Q: Does prometheus-systems.co.za have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns2.tld-ns.com, ns1.tld-ns.net, ns3.tld-ns.net, ns4.tld-ns.com); NS records span 2 providers (tld-ns.com, tld-ns.net) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

C+

Trust rating

Fair · 78/100

Procurement snapshot

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

Strengths

Cookie Security

Known Breaches

TLS Protocol Support

CVE Exposure

Questions to ask

Confirm backup mail server configuration

Estimated remediation effort: 1–2 days

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

Trust Score Trend

→ No change 1 scan · Last scanned July 19, 2026

Score

100 75 50 25 0

C+

prometheus-systems.co.za

78/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

CCPA

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

7 items need attention

8 passed

Turn on HSTS (forces browsers to always use HTTPS)

HSTS Header

< 1 hour

This puts visitor logins and session data at risk of interception on untrusted networks. prometheus-systems.co.za doesn't send the HSTS header, so a browser can still be tricked into connecting over plain, unencrypted HTTP instead of HTTPS — an attacker on the same network (e.g. public wifi) can exploit that gap to intercept traffic. Turning HSTS on tells every browser "always use HTTPS for this site, no exceptions."

PCI-DSS 4.0Req 6.4.1

Required application security controls

NIST 800-53SC-8

Transmission confidentiality and integrity

How to fix this

1Add this response header to your site. If you manage your own server (nginx, Apache, IIS) or a CDN like Cloudflare, add it in that config. If your site is on a managed platform (Wix, Squarespace, Shopify, WordPress.com), search their help center for "custom headers" or ask their support — most support it, though a few don't.

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Before adding it, make sure every subdomain (not just the main site) also works over HTTPS — HSTS applies site-wide.

3Confirm it's live: search "http header checker" and enter prometheus-systems.co.za.

4Once confirmed, submit the domain at hstspreload.org so browsers enforce HTTPS even on a user's very first visit.

HSTS guide

Report unlocked.

View all 8 passed checks

Cookie Security

Known Breaches

TLS Protocol Support

CVE Exposure

Subprocessors & Tech Stack

TLS Configuration

DMARC / Email Security

Certificate Hygiene

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.prometheus-systems.co.za ↗

Security page

prometheus-systems.co.za/security ↗

prometheus-systems.co.za/privacy ↗

DPA (Data Processing Agreement)

prometheus-systems.co.za/dpa ↗

Updated recently

Subprocessors List

prometheus-systems.co.za/policies/subprocessors ↗

Similar companies

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Blocking Issues

Not enabled

Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.

Likelihood: ★★★☆☆

Impact: ★★★★☆

0/5 present

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

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Strengths: Mail handled by mx1.tld-mx.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

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: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns2.tld-ns.com, ns1.tld-ns.net, ns3.tld-ns.net, ns4.tld-ns.com); NS records span 2 providers (tld-ns.com, tld-ns.net) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

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: ★☆☆☆☆