Free Email Spam Tester Free DNS tools API

The Free DNS tools API from Free Email Spam Tester — 15 operation(s) for free dns tools.

Operations 15

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/email-spam-tester-com:email-spam-tester-com-free-dns-tools-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Email Spam Tester Free DNS tools API
  description: 'Test an email before you send it to anybody.


    The loop is three calls. Ask for an address, send the message you were about to

    send your list to that address, then read the report. No key, no account, no

    limit per person on the first 100,000 reports.


    curl -X POST https://email-spam-tester.com/api/v1/inbox

    # send your message to the address it returns, then:

    curl https://email-spam-tester.com/api/v1/tests/


    The address accepts exactly one message and expires after an hour. The report

    link is permanent and carries `report_url` inside the JSON, so a forwarded

    report still says where it came from.


    **Poll `/status`, not `/`.** The full report is several thousand lines of JSON

    and the analysis takes a few seconds; the status endpoint is the cheap way to

    find out whether it is worth fetching yet. `analysis_status` reaches

    `checks_ready` first and the AI plan lands a minute or so later under

    `ai_status`, so a caller that only wants the checks does not have to wait for

    the plan.


    **Agents:** there is an MCP server at `/mcp` with the same capability and a

    blocking wait, which is a better fit than polling from a model.


    Every finding carries `citations`: the section of the RFC it comes from, quoted,

    and the page where Google states its own requirement. Those are curated by hand

    rather than generated, so they can be relied on.'
  contact:
    name: Email Spam Tester
    url: https://email-spam-tester.com/
  version: 1.0.0
tags:


# --- truncated at 32 KB (69 KB total) ---
# Full source: https://artifacts.apis.io/email-spam-tester-com/openapi/email-spam-tester-com-free-dns-tools-api-openapi.yml