99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
Security
Endpoints
1
Key Features
8
Frequently Asked Questions
4
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
OpenAPI schema
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
domain
Example Response
domaincertificatestotal_certificateshas_valid_cert
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/certificates
domain
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Uptime
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
Free allowance
Sign Up for Free
Start with 10,000 monthly credits and upgrade only when usage grows.
Active
Example Request
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
CT Log Monitoring
Query public Certificate Transparency logs for any domain.
Certificate History
View historical certificates issued for a domain.
Issuer Tracking
Track which Certificate Authorities have issued certs for your domain.
Expiration Alerts
Identify expiring certificates before they cause outages.
SAN Coverage
See all Subject Alternative Names covered by each certificate.
Security Detection
Detect unauthorized or suspicious certificate issuance.
Fingerprint Verification
Verify certificate authenticity using SHA-256 fingerprints.
Compliance Monitoring
Ensure certificates meet security policy requirements.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/certificates?domain=example.com"Example Response
{
"domain": "example.com",
"certificates": [
{
"issuer": "Let's Encrypt",
"serial": "0a:1b:2c:3d:4e:5f",
"not_before": "2024-01-01T00:00:00Z",
"not_after": "2024-04-01T00:00:00Z",
"san": ["example.com", "www.example.com"],
"fingerprint_sha256": "AB:CD:EF..."
}
],
"total_certificates": 1,
"has_valid_cert": true
}Frequently Asked Questions
What is Certificate Transparency?
Certificate Transparency (CT) is a system where Certificate Authorities publicly log all SSL/TLS certificates they issue. This allows domain owners and security researchers to monitor for unauthorized certificates.
Why monitor certificates?
Monitoring helps detect: unauthorized certificates (potential MitM attacks), certificate expiration before it causes outages, compliance with security policies, and historical certificate changes.
How fresh is the data?
We query live CT logs, so data is typically current within hours of certificate issuance.
Can I detect phishing certificates?
Yes! You can monitor for certificates issued to domains similar to your brand, which could indicate phishing attempts.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Server Error
500
Internal error
Bad Gateway
502
Upstream RDAP error
Service Unavailable
503
Upstream service unavailable or temporarily rate limited.
Gateway Timeout
504
Upstream lookup timed out.
Monitor SSL Certificates