Baan · Domain Security

Baan Domain Security

Domain security

Domain security posture for Baan, probed live across 2 host(s) and 2 registrable domain(s). Email/DNS controls: DNSSEC present, SPF present, DMARC present (p=reject).

CompanyEnterprise Resource PlanningERPEnterprise SoftwareManufacturingSupply ChainNetherlandsAcquiredLegacy

Transport & Host Security

baan.com
HTTPS: no · HSTS: no
www.baan.com
HTTPS: no · HSTS: no

Domain (DNS/Email) Security

baan.com
DNSSEC: yes · SPF: yes · DMARC: yes (p=reject) · CAA: yes
baan.nl
DNSSEC: yes · SPF: yes · DMARC: yes (p=reject) · CAA: yes

Source

Domain Security

baan-domain-security.yml Raw ↑ 
generated: '2026-07-20'
method: probed
source: live DNS (dig) and TLS/HTTP probes of the legacy Baan domains
notes: >-
  The Baan domains are still actively held and hygienically managed by Infor (DNSSEC signed, CAA
  pinned, SPF and DMARC p=reject, mail routed through Infor's Cisco IronPort tenant and Microsoft 365),
  but they serve no HTTPS: port 443 does not complete a TLS handshake on either host. Only plaintext
  HTTP is answered, and it returns a blanket 301 to the Infor LN product page. Recorded as https:
  false — this is a parked/redirect estate, not a live API host.
hosts:
- host: baan.com
  https: false
  https_error: TLS handshake failed on port 443
  http: true
  http_status: 301
  redirect_to: https://www.infor.com/product-summary/erp/ln/
  hsts: false
- host: www.baan.com
  https: false
  https_error: TLS handshake failed on port 443
  http: true
  http_status: 301
  redirect_to: https://www.infor.com/product-summary/erp/ln/
  hsts: false
domains:
- domain: baan.com
  dnssec: true
  ds_records: 1
  caa:
  - '0 issue "amazon.com"'
  - '0 issue "digicert.com; cansignhttpexchanges=yes"'
  - '0 issue "letsencrypt.org"'
  - '0 issue "sectigo.com"'
  - '0 issuewild "amazon.com"'
  - '0 issuewild "digicert.com; cansignhttpexchanges=yes"'
  - '0 issuewild "letsencrypt.org"'
  - '0 issuewild "sectigo.com"'
  - '0 iodef "mailto:mad@infor.com"'
  spf: true
  spf_record: v=spf1 exists:%{i}.spf.hc3692-74.iphmx.com include:spf.protection.outlook.com -all
  dmarc: true
  dmarc_policy: reject
  dmarc_record: v=DMARC1; p=reject; rua=mailto:l5hgamx6@ag.dmarcian.com
  mx:
  - mx1.hc3692-74.iphmx.com
  - mx2.hc3692-74.iphmx.com
- domain: baan.nl
  dnssec: true
  ds_records: 1
  caa:
  - '0 issue "amazon.com"'
  - '0 issuewild "amazon.com"'
  - '0 iodef "mailto:mad@infor.com"'
  spf: true
  spf_record: v=spf1 exists:%{i}.spf.hc3692-74.iphmx.com include:spf.protection.outlook.com -all
  dmarc: true
  dmarc_policy: reject
  dmarc_record: v=DMARC1; p=reject; rua=mailto:l5hgamx6@ag.dmarcian.com
  mx:
  - mx1.hc3692-74.iphmx.com
  - mx2.hc3692-74.iphmx.com

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