DNS Lookup

A validated DNS A lookup request for example.com.

How it works

• Reject URLs, paths, ports, internal names and private address ranges.
• Normalize the hostname (lower-case, trailing dot removed).
• Ask the platform API, which forwards the query to the configured resolver provider.
• Return the resolver's A/AAAA/CNAME/MX/TXT/NS records with TTLs.

• The live records depend on the resolver's current state, so the result is fetched at request time.

Methodology

1. Validate the hostname against RFC 1123 label rules and reject private, loopback and internal targets.
2. Forward only the validated hostname and the selected record type to the configured resolver provider.
3. Normalize the provider response into records (name, TTL, class, type, value, MX priority).

Time model

• Time source: UTC.
• Timezone: Live records are fetched at request time; TTLs are relative to the resolver response instant, never to a baked build time.
• Locale: Record values are ASCII tokens; no locale-specific formatting is applied.
• Daylight saving: The query instant is absolute; daylight-saving transitions do not affect it.
• Reference date: There is no reference-date input; the result reflects the resolver state when the request is served.

Usage

1. Enter a public hostname (for example example.com).
2. Choose a record type: A, AAAA, CNAME, MX, TXT or NS.
3. Run the lookup and read the normalized records and TTLs.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

A record

{
  "target": "example.com",
  "type": "A"
}

MX records

{
  "target": "example.com",
  "type": "MX"
}

TXT records

{
  "target": "example.com",
  "type": "TXT"
}

NS records

{
  "target": "example.com",
  "type": "NS"
}

Limitations

Server processing and data flow

This tool performs its lookup on the Gampangin API. Your hostname and the selected record type are sent to our server, which forwards them to the deployment's configured DNS resolver provider and returns the records.

The query is stateless: it is not stored, not written to logs, and not used for analytics. Responses are marked no-store and set no cookie. When no resolver provider is configured the request fails closed with a clear message rather than returning a fabricated record.

Record types

A and AAAA return IPv4 and IPv6 addresses. CNAME returns the canonical name alias. MX returns mail exchangers with preference numbers. TXT returns text records such as SPF and verification values. NS returns the authoritative name servers.