Is admin.onebox.solutions safe to use as a vendor?

admin.onebox.solutions scored 78/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 8 checks passed, 4 warnings, 3 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does admin.onebox.solutions use?

admin.onebox.solutions 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 admin.onebox.solutions have DMARC configured?

Yes. admin.onebox.solutions'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; SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit). Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Does admin.onebox.solutions have SPF configured?

Yes. SPF record: v=spf1 include:spf.protection.outlook.com -all

Does admin.onebox.solutions have security headers configured?

admin.onebox.solutions has 0 of 5 recommended security headers. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Has admin.onebox.solutions been involved in a data breach?

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

Does admin.onebox.solutions have known CVE vulnerabilities?

Detected technologies: LiteSpeed, CyberPanel-OLS/2.5.1. No high or critical CVEs found for detected versions.

Is admin.onebox.solutions's SSL certificate valid?

Yes. Strengths: Certificate valid, 143 days remaining; Issued by Sectigo Limited. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

admin.onebox.solutions Security Report — Grade C+ (78/100)

Q: Does admin.onebox.solutions 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 admin.onebox.solutions have DNSSEC enabled?

No. Strengths: 5 nameservers configured (ns3.no-ip.com, ns5.no-ip.com, ns1.no-ip.com, ns2.no-ip.com...); 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: All nameservers are from a single provider (no-ip.com) — a provider outage takes down the domain; 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

MX Records & Mail Provider

DMARC / Email Security

TLS Configuration

Known Breaches

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 2–4 days

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

Trust Score Trend

→ No change 1 scan · Last scanned October 13, 2026

Score

100 75 50 25 0

C+

admin.onebox.solutions

78/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

7 items need attention

8 passed

Add missing cookie security settings

Cookie Security

1–2 hours High

This makes it meaningfully easier for an attacker to hijack authenticated customer sessions, increasing account-takeover risk. On admin.onebox.solutions, most cookies are missing key protections: 1 cookie(s) can be sent over an unencrypted connection (missing the "Secure" flag); 1 cookie(s) can be read by page scripts, including malicious ones (missing "HttpOnly"); 1 cookie(s) don't restrict cross-site requests (missing "SameSite").

OWASP ASVS3.4

Session cookies use Secure, HttpOnly, and SameSite attributes

How to fix this

1Add Secure to every cookie your site sets — this is usually one line in your app's session/cookie config, not a DNS or hosting setting.

2Add HttpOnly to login/session cookies — same place as above, in your app's cookie settings.

3Add SameSite=Lax (or Strict for sensitive cookies) to every cookie.

4This needs a developer — it's a one-line change per cookie in your website's code, not something changeable from a hosting dashboard.

5Re-scan afterward to confirm all three flags are now set.

Cookie security guide

Report unlocked.

View all 8 passed checks

MX Records & Mail Provider

DMARC / Email Security

TLS Configuration

Known Breaches

Subprocessors & Tech Stack

TLS Protocol Support

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 C

702 companies · LynxRadar ranking

Blocking Issues

Fail

Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (PHPSESSID); 1/1 cookie(s) missing HttpOnly flag (PHPSESSID); 1/1 cookie(s) missing SameSite attribute (PHPSESSID).

Likelihood: ★★★★☆

Impact: ★★★★☆

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

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: 5 nameservers configured (ns3.no-ip.com, ns5.no-ip.com, ns1.no-ip.com, ns2.no-ip.com...); 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: All nameservers are from a single provider (no-ip.com) — a provider outage takes down the domain; 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: ★☆☆☆☆