Tabby · Domain Security

Tabby Ml Domain Security

Domain security

Domain security posture for Tabby, probed live across 2 host(s) and 1 registrable domain(s). 2 host(s) serve HTTPS; 1 advertise HSTS. Email/DNS controls: DNSSEC absent, SPF present, DMARC absent.

AI Coding AssistantCode CompletionOpen SourceDeveloper ToolsLLMAISelf-HostedCode GenerationCopilot Alternative

Transport & Host Security

www.tabbyml.com
HTTPS: yes · HSTS: yes
tabby.tabbyml.com
HTTPS: yes · HSTS: no

Domain (DNS/Email) Security

tabbyml.com
DNSSEC: no · SPF: yes · DMARC: no · CAA: none

Source

Domain Security

Raw ↑ 
generated: '2026-07-11'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml + website hosts
hosts:
- host: www.tabbyml.com
  https: true
  hsts: true
  hsts_max_age: 31536000
- host: tabby.tabbyml.com
  https: true
  hsts: false
domains:
- domain: tabbyml.com
  dnssec: false
  caa: []
  spf: true
  spf_record: v=spf1 +include:spf.onlarksuite.com -all
  dmarc: false
notes: >-
  Probes captured 2026-07-11. The documented Tabby API is self-hosted, so the
  live API host is your own instance (default http://localhost:8080) rather than
  a TabbyML-operated domain; these probes cover the marketing site
  (www.tabbyml.com) and docs (tabby.tabbyml.com) only. Self-hosted TLS/HSTS is a
  function of how you expose your own deployment.