Domain Trust Monitor API | SSL + RDAP + DMARC + Headers avatar

Domain Trust Monitor API | SSL + RDAP + DMARC + Headers

Pricing

Pay per usage

Go to Apify Store
Domain Trust Monitor API | SSL + RDAP + DMARC + Headers

Domain Trust Monitor API | SSL + RDAP + DMARC + Headers

Monitor domain trust posture in one run: SSL expiry and issuer drift, registrar and expiry changes, DMARC/SPF/DKIM posture, security headers, and optional Google Web Risk alerts.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

太郎 山田

太郎 山田

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 hours ago

Last modified

Share

Monitor domain trust posture in one recurring run. This actor bundles SSL expiry and issuer drift, RDAP ownership and expiry changes, DMARC/SPF/DKIM posture, security headers, and optional Google Web Risk alerts into one action-needed payload.

Store Quickstart

  • Start with store-input.example.json for a reliable first dataset run across three stable domains.
  • If that matches your workflow, switch to store-input.templates.json and pick one of:
    • Quickstart (Dataset) for first success
    • Portfolio Watch for weekly domain sweeps
    • Action-Needed Webhook for recurring alerts
    • Domain Trust + Web Risk when you need optional reputation checks

The quickstart is tuned for low-maintenance recurring monitoring: direct network checks, no browser automation, no proxies, and no vendor lock-in for the core signals.

What this actor does

For each domain, the actor combines four operationally useful checks into one row:

  • SSL / TLS: expiry windows, issuer drift, fingerprint rotation, certificate trust issues
  • RDAP: registrar, nameserver, DNSSEC, domain expiry, and ownership-related changes
  • DNS / email security: MX, SPF, DKIM, and DMARC posture with a grade and fix-ready warnings
  • Security headers: HSTS, CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy, and more

Optional Google Web Risk lookups can be enabled with your own Google Cloud API key when you want a commercially usable malware / social-engineering reputation signal.

Why this is a better product than separate utilities

Running four separate actors is operationally noisy. domain-trust-monitor is designed as the productized lane:

  • one recurring task
  • one schedule
  • one dataset or webhook payload
  • one trust score per domain
  • one ranked list of action-needed alerts

This is better for MSPs, agencies, portfolio operators, security teams, and SaaS teams who want to know which domains need attention first.

Input example

{
"domains": ["google.com", "github.com", "cloudflare.com"],
"expiryWarningDays": 30,
"followRedirects": true,
"checkDkim": true,
"delivery": "dataset",
"concurrency": 2
}

Output example

{
"domain": "github.com",
"status": "changed",
"severity": "high",
"alertCount": 1,
"brief": "1 alert(s): TLS certificate expires in 12 days",
"trustScore": {
"total": 67,
"grade": "C"
},
"recommendedActions": [
"Schedule certificate renewal before the warning window closes."
]
}

A fuller payload is available in sample-output.example.json. The full actor output also includes flattened alerts[], per-component details, and an executiveSummary for webhook delivery.

Delivery modes

  • dataset: saves one domain row per result to the actor dataset
  • webhook: sends the full action-needed payload (meta, alerts, results) to your webhook URL

The dataset path is the safest first run. The webhook path is the best recurring upsell once the team trusts the signal.

WorkflowWhy
Weekly portfolio sweepCatch SSL, DNS, and header drift across all client or product domains
Renewal watchlistSurface domains or certificates that are close to expiry
Security hardening QAValidate DMARC and browser-facing hardening before launch
MSP / agency reportingExport one ranked list of domains that need work

Cost profile

The core actor uses built-in Node.js networking and public RDAP / DNS / HTTP endpoints. That keeps maintenance and vendor cost low.

Optional Google Web Risk lookups are only used when explicitly enabled and billed through your own Google Cloud account.

Commercial ops

Set up .env first:

$cp -n .env.example .env

Configure the Apify task and schedule:

$npm run apify:cloud:setup

Daily / weekly reliability checks:

npm run canary:check
npm run contract:test:live
  • ssl-certificate-monitor — standalone TLS checks if you only need certificates
  • rdap-domain-monitor — standalone RDAP ownership / expiry checks
  • dns-dmarc-security-checker — standalone email security grading
  • security-headers-checker — standalone browser security header grading