Is physicalintelligence.company safe to use as a vendor?

physicalintelligence.company scored 88/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 6 checks passed, 6 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does physicalintelligence.company use?

physicalintelligence.company 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 physicalintelligence.company have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com include:mailgun.org ~all

Does physicalintelligence.company have security headers configured?

physicalintelligence.company has 0 of 0 recommended security headers. All recommended headers present.

Does physicalintelligence.company use HSTS?

No. Could not fetch https://physicalintelligence.company — connection failed or timed out.

Has physicalintelligence.company been involved in a data breach?

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

Does physicalintelligence.company have known CVE vulnerabilities?

No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.

Is physicalintelligence.company's SSL certificate valid?

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

physicalintelligence.company Security Report — Grade B+ (88/100)

Q: Does physicalintelligence.company have DMARC configured?

Yes. physicalintelligence.company's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google, krs). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; DMARC sp=none — subdomains are unprotected even though apex has p=quarantine. Attackers can spoof sub.physicalintelligence.company.

Q: Does physicalintelligence.company have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com); SOA record present and MNAME consistent with NS set; 5 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 (googledomains.com) — a provider outage takes down the domain; DNSSEC partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

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

B+

Trust rating

Good · 88/100

Procurement snapshot

No critical findings. The 5 remaining items are configuration gaps, not architectural problems.

Strengths

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

Known Breaches

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+

physicalintelligence.company

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

6 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 physicalintelligence.company is partly set up, but there are gaps: your DMARC policy is "quarantine", so spoofed mail lands in spam instead of being blocked; subdomains are unprotected (sp=none). 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

1Once your DMARC reports show no legitimate mail failing, change the policy from "quarantine" to "reject" in your DNS settings (you're using Google Workspace — see https://knowledge.workspace.google.com/admin/security/set-up-dkim) so spoofed mail is blocked outright. Your current record with just that change:

v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; ri=86400

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

Email authentication guide

Report unlocked.

View all 6 passed checks

MX Records & Mail Provider

TLS Configuration

TLS Protocol Support

Known Breaches

Certificate Hygiene

CVE Exposure

Couldn't check: Cookie Security, HSTS Header, Security Headers, Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so these aren'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

High Priority

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: google, krs). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; DMARC sp=none — subdomains are unprotected even though apex has p=quarantine. Attackers can spoof sub.physicalintelligence.company.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 4 nameservers configured (ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com); SOA record present and MNAME consistent with NS set; 5 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 (googledomains.com) — a provider outage takes down the domain; DNSSEC partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

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

Warn

Could not load physicalintelligence.company's homepage to detect its e-commerce platform, payment processor, or CDN.