TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
32,435

reverse dns consistency audit derived

api.zfinia.comCommunicationsderived

POST https://api.zfinia.com/x402/v1/reverse-dns-consistency-audit

passabsent from every registry#7 by calls of 15 on this host

0.14 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-04 21:22 UTC · method

Validation state
pass
as of 2026-10-04 13:01 UTC · method · sweep daily-2026-10-04
Uptime, 7 / 30 / 90 days
— / 100% / 100%
as of 2026-10-04 13:01 UTC · method · 0 of 0 in 7d, 2 of 2 in 30d, 2 of 2 in 90d
Calls, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Unique payers, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Last called
2026-10-04 08:43 UTC
as of 2026-10-04 21:22 UTC · method
First observed by TOLLderived
2026-10-04
as of 2026-10-04 12:19 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.14 USDC
as of 2026-10-04 21:22 UTC · method · on eip155:8453
Networks
1
as of 2026-10-04 21:22 UTC · method

Counters

2 observations, 1 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 935 endpoints in Communications that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 456 in the category are counted higher and 478 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 2 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.

In words

Of api.zfinia.com's 15 listings, reverse dns consistency audit ranks tied 7th by calls with 9 others.

Callers of reverse dns consistency audit supply a json body with the fields hosts and expected_domain.

A response from reverse dns consistency audit, as declared, includes hosts, limits, passed, complete, findings, consistent and 2 others.

reverse dns consistency audit drew a single call from a single payer in the trailing 30 days.

The last call to reverse dns consistency audit came 9 days before the snapshot, 2026-10-04.

A call to reverse dns consistency audit costs 0.14 USDC on Base, as declared.

Of the calls counted across api.zfinia.com, reverse dns consistency audit takes 4%.

At api.zfinia.com, reverse dns consistency audit takes POST requests, is listed in neither registry at the last pull, and falls under communications by TOLL's rules.

reverse dns consistency audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.

Closest in price to reverse dns consistency audit within communications: open inbox at ausca.com and profiles email at api.linkedpanda.com.

reverse dns consistency audit is near the top of prices in communications; 97% of comparable listings are cheaper.

The wallet paid by reverse dns consistency audit is the payee of 179 endpoints across 5 hosts.

The seller's tags on reverse dns consistency audit are reverse dns, email deliverability signals, dns and domain trust.

reverse dns consistency audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; that is registry presence, not liveness.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-10-04 21:22 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.14 USDCexact0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-04 13:01 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-04 13:01 UTCpass0daily-2026-10-04
2026-10-04 12:28 UTCpass0new-after-daily-2026-10-04

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:43 UTC · method

The input and output block
{
  "input": {
    "body": {
      "hosts": [
        {
          "ptr": "mx1.example.test",
          "helo": "mx1.example.test",
          "address": "203.0.113.10",
          "forward_addresses": [
            "203.0.113.10"
          ]
        },
        {
          "ptr": "mx2.example.test",
          "helo": "mx2.example.test",
          "address": "203.0.113.11",
          "forward_addresses": [
            "203.0.113.99"
          ]
        },
        {
          "ptr": "198-51-100-7.static.hosting-vendor.test",
          "helo": "mail.example.test",
          "address": "198.51.100.7",
          "forward_addresses": [
            "198.51.100.7"
          ]
        },
        {
          "address": "192.0.2.44"
        }
      ],
      "expected_domain": "example.test"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "hosts": [
        {
          "ptr": "mx1.example.test",
          "helo": "mx1.example.test",
          "address": "203.0.113.10",
          "forward_addresses": [
            "203.0.113.10"
          ],
          "forward_confirmed": true
        },
        {
          "ptr": "mx2.example.test",
          "helo": "mx2.example.test",
          "address": "203.0.113.11",
          "forward_addresses": [
            "203.0.113.99"
          ],
          "forward_confirmed": false
        },
        {
          "ptr": "198-51-100-7.static.hosting-vendor.test",
          "helo": "mail.example.test",
          "address": "198.51.100.7",
          "forward_addresses": [
            "198.51.100.7"
          ],
          "forward_confirmed": true
        }
      ],
      "limits": {
        "maxRecords": 2000,
        "maxFindings": 500,
        "maxHeaderBytes": 131072,
        "maxIncludeTree": 200,
        "spfLookupLimit": 10,
        "maxRecordLength": 4096,
        "spfVoidLookupLimit": 2
      },
      "passed": false,
      "complete": true,
      "findings": [
        {
          "code": "REVERSE_NOT_FORWARD_CONFIRMED",
          "name": "mx2.example.test",
          "detail": "203.0.113.11 resolves to mx2.example.test, and mx2.example.test resolves to 203.0.113.99 rather than back to 203.0.113.11. Forward confirmation fails, which is worse than having no PTR because it look..."
        },
        {
          "code": "REVERSE_NAME_OUTSIDE_EXPECTED_DOMAIN",
          "name": "198-51-100-7.static.hosting-vendor.test",
          "detail": "198.51.100.7 resolves to 198-51-100-7.static.hosting-vendor.test, which is not inside example.test. A reverse name belonging to a hosting provider rather than the sender is what a receiver sees."
        },
        {
          "code": "REVERSE_NAME_LOOKS_GENERIC",
          "name": "198-51-100-7.static.hosting-vendor.test",
          "detail": "198.51.100.7 resolves to 198-51-100-7.static.hosting-vendor.test, which reads as a provider-generated name rather than a mail host. Several receivers score or refuse mail from generically named hosts."
        }
      ],
      "consistent": false,
      "host_count": 4,
      "request_id": "example-request",
      "service_id": "reverse_dns_consistency_audit",
      "assumptions": [
        "Nothing resolves DNS. The caller supplies the address, its reverse name and what that name resolves to, which is the triple a receiver actually evaluates.",
        "Forward confirmation is the check receivers apply, so a reverse name that resolves to a different address is reported as worse than having none: it looks configured and still fails.",
        "A generically named reverse host is reported as a signal rather than a defect, because several receivers score or refuse on it and the name is the only thing they see."
      ],
      "limitations": [
        "The triples supplied. Which receivers apply which rule, and how heavily, is outside this, and so is any prediction about deliverability.",
        "consistent is true only when every host had a reverse name, every one was forward confirmed, and every check the caller asked for was performed."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "not_examined": [],
      "finding_count": 5,
      "expected_domain": "example.test",
      "service_version": "1.0.0",
      "findings_by_code": {
        "NO_REVERSE_NAME": 1,
        "REVERSE_NAME_LOOKS_GENERIC": 1,
        "REVERSE_NOT_FORWARD_CONFIRMED": 1,
        "HELO_DOES_NOT_MATCH_REVERSE_NAME": 1,
        "REVERSE_NAME_OUTSIDE_EXPECTED_DOMAIN": 1
      },
      "forward_confirmed_count": 2,
      "without_reverse_name_count": 1
    }
  }
}
Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "reverse dns consistency audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-reverse-dns-consistency-audit-4bc917. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-reverse-dns-consistency-audit-4bc917-2026-10-13,
  author = {TOLL},
  title = {reverse dns consistency audit on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-reverse-dns-consistency-audit-4bc917}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about reverse dns consistency audit, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 4bc9175495142d392bd38b74963ffe63814faf4d3538ae2e0f75a674788223a7 from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.