Scan API: checks reference

A call to POST /api/v1/scan runs every check by default. To run only some, send categories (whole categories, by the name in grey) and/or checks (single checks). Nothing else runs; categories left out come back as null. Names match without regard to case, and an unknown name is a 400.

curl -X POST https://linkthreatscan.com/api/v1/scan \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com",
       "categories": ["email"],
       "checks": ["hstsEnforced", "envFileExposed"]}'

Every check is true when the site passes it, false when it fails, and null when it could not be determined (a source was unreachable). The same list is available as JSON at GET /api/v1/scan/checks.

Domain checks domainChecks

Registration and DNS: DNSSEC, CAA, takeover-prone CNAMEs and the domain's WHOIS status flags.

Website security websiteSecurity

Response headers and cookies of the scanned page.

Data leakage dataLeakage

Sensitive files and directories that should never be public, probed by path, plus open cloud buckets.

Encryption websiteEncryption

The TLS certificate, protocol versions, cipher suites, revocation and HTTPS enforcement.

Port scan network

A TCP connect scan of common service ports.

IP / reputation ipDomainReputation

Google Safe Browsing verdicts and AbuseIPDB reports for the host's IPv4 address.

Vulnerability management vulnerabilityManagement

End-of-life server software, certificate weaknesses and known TLS vulnerabilities.

Email email

SPF, DMARC, DKIM, MX and BIMI records of the domain.

Security engines securityEngines

Threat-intelligence blocklists. An engine this deployment has no credentials for is left out of the result.