What is the Dns Lookup API designed for?

It is designed for production diagnostics and automation workflows where teams need deterministic JSON output for monitoring, deployment checks, and incident triage.

What input formats are accepted for the domain parameter?

You can submit a plain domain, http URL, or https URL. The endpoint normalizes input to a hostname before lookup so integrations can pass user-entered values safely.

Is this endpoint stateless?

Yes. Requests are processed live and returned immediately. Submitted values are not persisted as long-term records by default.

How should teams handle rate limits?

Use retries with exponential backoff and queue burst traffic in workers. Avoid high-concurrency spikes from parallel CI jobs.

Can this endpoint be used in CI/CD and scheduled checks?

Yes. Responses are machine-readable and suitable for deployment gates, synthetic checks, and recurring monitoring tasks.

How should errors be handled in production?

Check HTTP status codes first, then parse structured JSON errors. Treat 4xx as input/config issues and 5xx as transient service failures requiring retry logic.

Is the API safe for compliance-sensitive workflows?

The endpoints are designed for stateless request/response diagnostics. For regulated environments, keep your own request logs and retention policies in your infrastructure.

Does this API guarantee rankings, indexing, or business outcomes?

No. It provides technical signals only. Outcomes depend on your implementation quality, infrastructure state, and external platform behavior.

DNS Lookup API

Run live DNS lookups and retrieve mail-auth and deliverability signals with one endpoint.

Live diagnostics • Stateless processing • API-ready output

Last Updated: 01 April 2026

The Velohost DNS Lookup API provides a single endpoint for retrieving core DNS records, SRV records, and email-authentication checks.

It is designed for technical SEO workflows, mail-deliverability checks, deployment diagnostics, and automated infrastructure health scripts.

Base API URL

All endpoints listed below are relative to this base URL.

Base API URL https://api.velohost.co.uk/dns-lookup/

Rate Limiting

This API is protected by a global rate limit to ensure fair usage and platform stability.

Limit: 30 requests per 10 seconds per IP address
Burst traffic is allowed
No authentication required
Requests exceeding the limit return HTTP 429

This limit applies across all Velohost public APIs.

Error Responses

The API uses standard HTTP status codes to indicate errors.

429 Too Many Requests

Returned when the global rate limit is exceeded.

400 Bad Request

Returned when the domain parameter is missing or cannot be normalised into a valid hostname.

Endpoint

Generate DNS report

Accepts domains with or without protocol (example.com, https://example.com, http://example.com) and returns DNS plus deliverability diagnostics.

Request

GET /report?domain=example.com

Response

{
  "domain": "example.com",
  "summary": {
    "headline": "DNS is configured and resolvable",
    "next_best_action": "Review DMARC policy for enforcement"
  },
  "dns": {
    "a": ["93.184.216.34"],
    "aaaa": [],
    "mx": [{ "host": "mx.example.com", "priority": 10 }],
    "ns": ["ns1.example.net", "ns2.example.net"],
    "txt": ["v=spf1 include:_spf.example.net ~all"],
    "soa": {
      "mname": "ns1.example.net",
      "rname": "hostmaster.example.net"
    }
  },
  "srv": {
    "email": {},
    "voip": {}
  },
  "deliverability": {
    "overall": { "score": 87 },
    "explanation": "SPF and DKIM detected. DMARC is present in monitor mode."
  }
}

Implementation Guidance

For production use, validate input before sending requests, implement retry with exponential backoff on 429 or transient failures, and log normalized responses for trend monitoring.

Learn more

Explore the tool, documentation, and guides.

Use the DNS Lookup Tool DNS Lookup FAQs