soona · Domain Security

Soona Domain Security

Domain security

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

CompanyCommerceE-CommerceContentPhotographyVideoCreativeDigital Asset ManagementArtificial IntelligenceMarketing

Transport & Host Security

soona.co
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 3 02:31:29 2026 GMT
book.soona.co
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes
mokker.ai
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes
app.mokker.ai
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes
api.mokker.ai
HTTPS: no · HSTS: no

Domain (DNS/Email) Security

soona.co
DNSSEC: no · SPF: yes · DMARC: yes (p=none) · CAA: none
mokker.ai
DNSSEC: no · SPF: no · DMARC: no · CAA: none

Source

Domain Security

soona-domain-security.yml Raw ↑
generated: '2026-08-13'
method: probed
source: live DNS/TLS/HTTP probes of apis.yml hosts plus the soona-controlled application and mokker.ai hosts
note: >-
  The soona.co row was written by 0-working/probe-domain-security.py; the book.soona.co,
  mokker.ai, app.mokker.ai and api.mokker.ai rows were probed by hand in the same pass
  (curl HEAD + openssl s_client + dig), because the script only reads hosts named in
  apis.yml and soona names no APIs. mokker.ai is a soona property, acquired with Zerolens
  GmbH in March 2024.
hosts:
- host: soona.co
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct  3 02:31:29 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: book.soona.co
  https: true
  tls_version: TLSv1.3
  hsts: true
  hsts_max_age: 63072000
  hsts_include_subdomains: true
  server: Heroku
- host: mokker.ai
  https: true
  tls_version: TLSv1.3
  hsts: true
  hsts_max_age: 31536000
  hsts_include_subdomains: false
  server: Framer
- host: app.mokker.ai
  https: true
  tls_version: TLSv1.3
  hsts: true
  hsts_max_age: 63072000
  hsts_include_subdomains: false
  server: Vercel
  http_status: 307
- host: api.mokker.ai
  https: null
  resolves: false
  finding: dangling-cname
  detail: >-
    api.mokker.ai is a CNAME to
    dualstack.mokker-us-west-2-prod-api-lb-1256808001.us-west-2.elb.amazonaws.com, which
    answers NXDOMAIN — the AWS load balancer it points at no longer exists. This is the
    exact host advertised as the API base on https://mokker.ai/api. A CNAME left pointing
    at a deleted cloud resource is a standing subdomain-takeover exposure as well as a dead
    API endpoint.
domains:
- domain: soona.co
  dnssec: false
  caa: []
  spf: true
  spf_record: v=spf1 a mx include:_spf.google.com include:sendgrid.net include:23618366.spf03.hubspotemail.net -all
  dmarc: true
  dmarc_policy: none
- domain: mokker.ai
  dnssec: false
  caa: []
  spf: false
  dmarc: false
  mx: true
  finding: >-
    mokker.ai accepts mail (Google Workspace MX) but publishes neither an SPF record nor a
    DMARC record, so the domain is unprotected against spoofing. soona.co by contrast
    publishes SPF with a -all hard fail, though its DMARC policy is p=none (monitor only,
    no enforcement).

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/soona-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.

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