DNS Lookup API, BIN Lookup & Tech Stack

BIN lookup for card issuers, DNS resolution over DNS-over-HTTPS, and technology profiling for any domain.

3 endpoints · 1 credit = $0.001. Each endpoint has its own credit cost, listed below. Calls that fail because of a service error are refunded.

Get 200 free credits View endpoints

AxioAPI Studio · Utility

Free Trial: 10 of 10 left

Utilities

Quick presets:

Bank Identification Card Info —

—

Card Scheme

—

Card Type

—

Brand Tier

—

Prepaid

—

Issuing Bank

—

Web: —

Hotline: —

Trụ sở: —

Country & Currency

—

ISO Code: —

Currency: —

Length & Luhn: —

Ready ?

No request yet. Run a test to see the actual response.

What you can build with the DNS lookup API

The DNS lookup API resolves A, AAAA, MX, TXT, NS, CNAME and SOA records, and sits next to two other small lookups that developers need all the time: card BIN issuer data and the technologies a website uses. Run them in the tool above or call the REST endpoints from code.

Look up a card BIN

Send the first 6 to 8 digits of a card to see issuer details, for example to add context to a checkout or a fraud review. Never send a full card number.

GET /api/v1/bin/{bin}

Check DNS records

Resolve A, AAAA, MX, TXT, NS, CNAME or SOA records, or ANY, to debug email setup, domain moves or verification records.

GET /api/v1/dns/{domain}

See what a website is built with

Profile a domain to detect its technologies for lead research or competitor analysis.

GET /api/v1/tech/{domain}

Try it free, no account needed: BIN checker · DNS lookup

How the DNS lookup API works

1
Pick the lookup

BIN takes 6 to 8 digits, DNS takes a hostname and a record type, tech profile takes a domain.
2
Call the endpoint

For example GET /api/v1/dns/{domain}?type=MX returns the MX records for that domain.
3
Read what is returned

DNS results include the record type, value and TTL. If nothing is found you get an empty result, not an invented one.

Try the Utility API with your own account

New accounts receive 200 credits after verification, enough for about 400 calls to "BIN lookup".

Get 200 free credits Read the docs

Using Utility

DNS lookup accepts a hostname and record type; inspect the returned type, value and TTL.

BIN lookup expects the supported number of leading digits. Do not enter a full card number.

Tech stack lookup reports detected technologies. An absent result is not replaced by a sample IP or technology.

DNS lookup API endpoints and pricing

OpenAPI 3.1 JSON

Select an operation above and open API & Docs for parameters and cURL, JavaScript, Python or PHP examples. The web tool uses your signed-in session; external integrations use a Bearer API key.

Method	Endpoint	Cost
GET	BIN lookup `/api/v1/bin/{bin}` Helpful?	0.5 credit / request≈ $0.0005
GET	DNS resolve `/api/v1/dns/{domain}` Helpful?	0.5 credit / request≈ $0.0005
GET	Technology profile `/api/v1/tech/{domain}` Helpful?	1 credit / request≈ $0.001

DNS lookup API: frequently asked questions

What is the DNS lookup API?

It resolves DNS records for a domain, and the same group offers a BIN lookup API, a BIN checker for card issuer data and a tech stack profile of a website.

What is a BIN lookup?

The BIN is the first digits of a payment card. A lookup returns issuer information for that BIN. It does not need, and must not be given, the full card number.

Which DNS record types are supported?

A, AAAA, MX, TXT, NS, CNAME, SOA and ANY.

Is the technology list complete?

It reports the technologies that could be detected. A technology that is not listed may still be in use.

How is it billed?

Per request, as shown in the endpoint table below. New accounts receive 200 credits after verification.

Before integrating

Live and example data

Check the Live or Sandbox label before running. Examples demonstrate the response structure and do not guarantee live service status.

Credits and limits

Pricing depends on the endpoint and billable units. Failed live requests are not replaced with billable examples. Check your account limits before running repeated requests.

View pricing

Handling errors

Keep the request ID for troubleshooting. For 429, respect Retry-After when provided. If a create or delete request loses its connection, check the resource state before retrying.

Related APIs

All APIs

Often used together: SEO API · Email Validation API · Proxy API

Ready to integrate the Utility API? Create an account and get your API key in minutes.

Get 200 free credits View pricing

DNS Lookup API, BIN Lookup & Tech Stack

—

—

🎉 You have completed your 10 free trial runs!