Core10 · Domain Security

Core10 Domain Security

Domain security

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

CompanyFintechFinancial-ServicesBankingAPI IntegrationSoftware DevelopmentDigital LendingAccount OpeningSalesforceConsultingProfessional ServicesPrivate CapitalTennessee

Transport & Host Security

monarchfts.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 6 14:14:37 2026 GMT
core10.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: no · cert expires: Nov 5 23:39:55 2026 GMT
blog.core10.io
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Sep 20 21:47:03 2026 GMT
getaccrue.com
HTTPS: yes · TLS: TLSv1.3 · HSTS: yes · cert expires: Oct 19 07:44:59 2026 GMT
api.getaccrue.com
HTTPS: yes · TLS: TLSv1.2 · HSTS: no · cert expires: Oct 13 23:59:59 2026 GMT

Domain (DNS/Email) Security

monarchfts.com
DNSSEC: no · SPF: yes · DMARC: yes (p=none) · CAA: none
core10.io
DNSSEC: no · SPF: yes · DMARC: yes (p=quarantine) · CAA: yes
getaccrue.com
DNSSEC: no · SPF: yes · DMARC: yes (p=none) · CAA: none

Source

Domain Security

core10-domain-security.yml Raw ↑
generated: '2026-08-11'
method: probed
source: live DNS/TLS/HTTP probes of every Core10-lineage host
note: >-
  Core10's own domain, core10.io, still holds a valid certificate and 301-redirects to
  monarchfts.com. api.getaccrue.com is the only live API host in the lineage; it is the
  weakest posture here — TLSv1.2 and no HSTS header at all — and it serves a bare nginx 404
  on every path, so nothing about the contract behind it is public.
hosts:
- host: monarchfts.com
  role: primary website (Core10 successor brand)
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  6 14:14:37 2026 GMT
  hsts: false
- host: core10.io
  role: retired Core10 domain, 301 to monarchfts.com
  https: true
  tls_version: TLSv1.3
  cert_expires: Nov  5 23:39:55 2026 GMT
  hsts: false
- host: blog.core10.io
  role: Core10 Insights blog
  https: true
  tls_version: TLSv1.3
  cert_expires: Sep 20 21:47:03 2026 GMT
  hsts: true
  hsts_max_age: 31536000
- host: getaccrue.com
  role: Accrue product site
  https: true
  tls_version: TLSv1.3
  cert_expires: Oct 19 07:44:59 2026 GMT
  hsts: true
  hsts_max_age: 63072000
- host: api.getaccrue.com
  role: Accrue API host (live nginx, no public contract)
  https: true
  tls_version: TLSv1.2
  cert_expires: Oct 13 23:59:59 2026 GMT
  hsts: false
domains:
- domain: monarchfts.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: none
- domain: core10.io
  dnssec: false
  caa:
  - 0 issuewild "comodoca.com"
  - 0 issuewild "digicert.com; cansignhttpexchanges=yes"
  - 0 issuewild "letsencrypt.org"
  - 0 issuewild "pki.goog; cansignhttpexchanges=yes"
  - 0 issuewild "ssl.com"
  - 0 issue "comodoca.com"
  spf: true
  dmarc: true
  dmarc_policy: quarantine
- domain: getaccrue.com
  dnssec: false
  caa: []
  spf: true
  dmarc: true
  dmarc_policy: none
x-evidence:
  fetched: '2026-08-11'
  hosts_probed: 5
  domains_probed: 3

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