Is pay.sifalo.com safe to use as a vendor?

pay.sifalo.com scored 68/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 pay.sifalo.com use?

pay.sifalo.com 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 pay.sifalo.com have SPF configured?

Yes. SPF record: v=spf1 include:spf.protection.outlook.com include:zeptomail.net ~all

Does pay.sifalo.com have security headers configured?

pay.sifalo.com has 3 of 5 recommended security headers. Present: X-Content-Type-Options, X-Frame-Options, Referrer-Policy. Missing: CSP, Permissions-Policy.

Has pay.sifalo.com been involved in a data breach?

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

Does pay.sifalo.com have known CVE vulnerabilities?

Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

Is pay.sifalo.com's SSL certificate valid?

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

pay.sifalo.com Security Report — Grade D+ (68/100)

Q: Does pay.sifalo.com have DMARC configured?

No. pay.sifalo.com's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented.

Q: Does pay.sifalo.com 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 pay.sifalo.com have DNSSEC enabled?

No. Strengths: 3 nameservers configured (ns2.dreamhost.com, ns1.dreamhost.com, ns3.dreamhost.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 (dreamhost.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

D+

Trust rating

Weak · 68/100

Procurement snapshot

1 critical finding identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

Known Breaches

Questions to ask

Confirm email authentication (SPF/DKIM/DMARC) rollout plans

Estimated remediation effort: 2–6 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 15, 2026

Score

100 75 50 25 0

D+

pay.sifalo.com

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

0 of 1 fixed

All 1 critical issue marked as fixed

Re-scan to confirm and update your score.

Turn on email authentication (SPF, DKIM, DMARC)

DMARC / Email Security

1–2 days Critical

This exposes customers, partners, and employees to phishing attacks that impersonate your brand. Right now, anyone can send an email that looks like it came from [email protected] — no password or hack required. This is how the vast majority of phishing scams that impersonate a company work, and it can damage your reputation with customers even though your systems were never touched. Missing: DMARC.

NIST SP 800-177r1§4

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

ISO 27001:2022A.5.14

Information transfer controls cover email

CISA BOD 18-01DMARC

Requires DMARC p=reject on US federal email domains

How to fix this

1Add a DMARC record in your DNS settings (you're using Microsoft 365 — see https://learn.microsoft.com/en-us/defender-office-365/email-authentication-dkim-configure). This tells receiving mail servers what to do with messages that fail SPF and DKIM checks (start on "quarantine" — send to spam — rather than "reject", so nothing legitimate gets blocked while you're testing).

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

2After 2–4 weeks, check the DMARC reports for anything legitimate that got flagged, then tighten the policy from quarantine to reject.

Email authentication guide

Report unlocked.

View all 8 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

Known Breaches

Certificate Hygiene

Cookie Security

Subprocessors & Tech Stack

CVE Exposure

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 D

842 companies · LynxRadar ranking

Blocking Issues

Not configured

Strengths: SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented.

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

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: 3 nameservers configured (ns2.dreamhost.com, ns1.dreamhost.com, ns3.dreamhost.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 (dreamhost.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: ★☆☆☆☆

3/5 present

Missing: CSP, Permissions-Policy

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆