Lev · Domain Security

Lev Domain Security

Domain security

Domain security posture for Lev, probed live across 3 host(s) and 1 registrable domain(s). 3 host(s) serve HTTPS (up to TLSv1.3); 1 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC present (p=reject).

CompanyCommercial Real EstateReal-EstatePropTechCRE FinancingLendingCRMArtificial IntelligenceAI AgentsDeal ManagementMarket DataDocuments

Transport & Host Security

www.lev.com

HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Aug 28 12:15:05 2026 GMT

api.lev.com

HTTPS: yes · TLS: TLSv1.2 · HSTS: no · cert expires: Dec 3 23:59:59 2026 GMT

mcp.lev.com

HTTPS: yes · HSTS: no

Domain (DNS/Email) Security

lev.com

DNSSEC: no · SPF: yes · DMARC: yes (p=reject) · CAA: none

Source

Domain Security

generated: '2026-07-19'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: www.lev.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Aug 28 12:15:05 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: api.lev.com
  https: true
  tls_version: TLSv1.2
  cert_expires: Dec  3 23:59:59 2026 GMT
  hsts: false
  note: No Strict-Transport-Security header observed on the API host, though the
    marketing/docs host sets one with a one-year max-age. The Lev security docs
    state HSTS is enforced.
- host: mcp.lev.com
  https: true
  hsts: false
  role: hosted MCP server
domains:
- domain: lev.com
  dnssec: false
  caa: []
  caa_note: Re-queried against 8.8.8.8 on 2026-07-19 — the zone genuinely publishes
    no CAA records. (An earlier probe pass recorded a resolver timeout here; that
    was a lookup artifact, not a record.)
  spf: true
  dmarc: true
  dmarc_policy: reject
findings:
- severity: info
  finding: Strong email posture — SPF present and DMARC at policy `reject`.
- severity: low
  finding: No DNSSEC on lev.com.
- severity: low
  finding: No CAA records, so certificate issuance is not restricted to named CAs.
- severity: low
  finding: HSTS is set on www.lev.com but not observed on api.lev.com or
    mcp.lev.com — the two hosts that carry bearer tokens.
- severity: info
  finding: api.lev.com negotiated TLSv1.2 while www.lev.com negotiated TLSv1.3.
    Both meet the documented TLS 1.2+ floor.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/lev-domain-security"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.