Qlty · Domain Security

Qlty Domain Security

Domain security

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

Code QualityCode CoverageStatic AnalysisLintingDeveloper Tools

Transport & Host Security

qlty.sh
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Nov 4 23:59:59 2026 GMT
docs.qlty.sh
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Aug 17 00:09:49 2026 GMT

Domain (DNS/Email) Security

qlty.sh
DNSSEC: no · SPF: yes · DMARC: yes (p=none) · CAA: none

Source

Domain Security

Raw ↑ 
generated: '2026-07-11'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + OpenAPI hosts
hosts:
- host: qlty.sh
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  4 23:59:59 2026 GMT
  hsts: true
  hsts_max_age: 63072000
- host: docs.qlty.sh
  https: true
  tls_version: TLSv1.3
  cert_expires: Aug 17 00:09:49 2026 GMT
  hsts: true
  hsts_max_age: 63072000
domains:
- domain: qlty.sh
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: none

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/qlty-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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