MollyBox · Domain Security

Mollybox Domain Security

Domain security

Domain security posture for MollyBox, probed live across 1 host(s) and 1 registrable domain(s). Email/DNS controls: DNSSEC absent, SPF absent, DMARC absent.

CompanyConsumerBookmarkingResource CaptureRead It LaterFastAPISelf-Hosted

Transport & Host Security

www.mollybox.cn
HTTPS: no · HSTS: no

Domain (DNS/Email) Security

mollybox.cn
DNSSEC: no · SPF: no · DMARC: no · CAA: none

Source

Domain Security

Raw ↑
generated: '2026-07-20'
method: probed
source: 'dig + curl against www.mollybox.cn / mollybox.cn (2026-07-20)'
hosts:
  - host: www.mollybox.cn
    https: false
    https_note: 'TLS/443 refuses connection (curl exit 7); service is HTTP-only'
    http: true
    http_server: uvicorn
    hsts: false
domains:
  - domain: mollybox.cn
    resolves_to: 101.132.184.190
    dnssec: false
    caa: []
    spf: false
    dmarc: false
findings:
  - No HTTPS/TLS on the web/API host (port 443 refused); API is served over plaintext HTTP.
  - No HSTS header.
  - No DNSSEC on the mollybox.cn zone.
  - No CAA records.
  - No SPF record.
  - No DMARC record.

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