Public Email Auth DNS Readiness Agent avatar

Public Email Auth DNS Readiness Agent

Pricing

Pay per event

Go to Apify Store
Public Email Auth DNS Readiness Agent

Public Email Auth DNS Readiness Agent

Check public email authentication DNS readiness for domains: MX, SPF, DMARC, DKIM selectors, BIMI, MTA-STS, TLS-RPT, risk labels, stable hashes, and useful-result pricing.

Pricing

Pay per event

Rating

0.0

(0)

Developer

jack su

jack su

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Categories

Share

Check whether public domains have useful email authentication DNS evidence.

This Actor reads public DNS only:

  • MX records
  • SPF TXT records
  • DMARC TXT records
  • optional DKIM selectors
  • BIMI, MTA-STS, and TLS-RPT TXT records

It is not an inbox deliverability monitor, spam-score tool, phishing detector, mailbox verifier, email sender, or security compliance certification product.

What It Extracts

  • email-auth readiness type
  • MX routing evidence
  • SPF records and conflict risk
  • DMARC policy, subdomain policy, reporting domains, and alignment tags
  • DKIM selector evidence without exposing long public-key values
  • BIMI, MTA-STS, and TLS-RPT presence
  • risk labels, diagnostics, scores, and recommended next action
  • stable emailAuthDnsHash for unchanged-result suppression

Input

{
"domains": ["openai.com"],
"dkimSelectors": [],
"previousEmailAuthDnsRecords": [],
"dnsTimeoutSecs": 10
}

Domains, root URLs, and email-domain inputs are accepted. Paths, query strings, fragments, credentials, IP addresses, localhost, and internal/private TLDs are rejected.

Pricing Behavior

This Actor is intended for pay-per-event pricing:

  • apify-actor-start: charged once per run.
  • useful-email-auth-dns-result: charged only for useful, new or changed public email-auth DNS readiness records.

Default dataset item charging is intentionally not configured. Missing DNS evidence, invalid inputs, duplicate domains, unchanged records, and lookup failures are written without the useful event.

Safety

  • public DNS only
  • no browser, cookies, login, mailbox access, or email sending
  • no private-network probing
  • DKIM public-key material is redacted in output previews
  • DMARC report addresses are reduced to reporting domains
  • linked reporting, BIMI, MTA-STS, or policy URLs are not fetched