Is diligence.ca safe to use as a vendor?

diligence.ca scored 66/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 15 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does diligence.ca use?

diligence.ca 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 diligence.ca have SPF configured?

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

Does diligence.ca have security headers configured?

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

Has diligence.ca been involved in a data breach?

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

Does diligence.ca have known CVE vulnerabilities?

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

Is diligence.ca's SSL certificate valid?

Yes. Strengths: Certificate valid, 80 days remaining; Issued by Let's Encrypt.

diligence.ca Security Report — Grade D (66/100)

Q: Does diligence.ca have DMARC configured?

No. diligence.ca's DMARC policy is set to 'none'. SPF record: yes. Strengths: SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: selector1, selector2). Issues: No DMARC record found — email spoofing is not prevented.

Q: Does diligence.ca use HSTS?

No. Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.

Q: Does diligence.ca have DNSSEC enabled?

No. Strengths: 2 nameservers configured (ns56.domaincontrol.com., ns55.domaincontrol.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Trust rating

Weak · 66/100

Procurement snapshot

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

Strengths

TLS Configuration

MX Records & Mail Provider

Known Breaches

TLS Protocol Support

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 May 02, 2026

Your rating Industry average

Score

100 75 50 25 0

diligence.ca

66/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

PCI-DSS

AOC not on file

3rd party · QSA

DORA

Not on file

EU regulatory

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

TLS Configuration

MX Records & Mail Provider

Known Breaches

TLS Protocol Support

Cookie Security

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies in Financial Services / Banking

Appears in

Financial Services / Banking vendors

44 companies scanned by LynxRadar

Vendors graded D

832 companies · LynxRadar ranking

Blocking Issues

Not configured

Strengths: SPF hard-fail (-all) configured; SPF DNS lookup count: 1/10 (within limit); DKIM configured (selectors: selector1, selector2). 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.

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 that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (ns56.domaincontrol.com., ns55.domaincontrol.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized 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: ★☆☆☆☆