DNS Lookup

Look up DNS records for any domain and see how that name resolves on the public internet. DNS records control website routing, email delivery, verification tokens and many security settings.

Uses the MyIPScan /api/dns-lookup route backed by a free DNS-over-HTTPS resolver. Results are a limited resolver view and may differ by network or resolver cache.

When to run a DNS lookup

DNS lookup is useful when a website does not load, email delivery fails, a domain migration is in progress, or you want to confirm which records are visible publicly. Checking A and AAAA records shows where a domain points, while MX and TXT records are commonly used for email routing and verification.

DNS changes can take time to propagate because resolvers cache records according to their TTL. If your result looks old, compare it again later or check from another resolver before assuming the domain is misconfigured.

Use A and AAAA records to inspect website IPv4 and IPv6 targets.
Use MX records to troubleshoot email delivery.
Use TXT records to verify SPF, DKIM, DMARC and ownership tokens.

Complete your privacy check:

- Domain Intelligence Report - combine DNS inventory, RDAP, IP/ASN, PTR, CAA, DNSSEC, TXT, and provider hints
- Website Exposure Scanner - combine DNS, HTTPS, redirects, headers, IPv6, and mixed-content signals
- Email Deliverability Doctor - combine MX, SPF, DMARC, DKIM selector, PTR, and sender-IP signals
- Reverse DNS Lookup - check PTR records for a public IP address
- SSL Certificate Checker - review certificate issuer, expiry, and SAN signals
- DNS Leak Test - review DNS resolver exposure signals
- WebRTC Leak Test - inspect browser WebRTC address candidates
- IP Checker - see your current public IP

B2B diagnostic report model

Domain intelligence diagnostics

Domain checks connect public DNS, RDAP-safe context, reverse DNS, CAA, DNSSEC hints, IP/ASN context, provider hints, and blacklist context.

SummaryStart with a plain-language status for the public target.

Top issuesPrioritize the few findings that need attention first.

What passedShow expected public signals without turning them into a certification.

What needs reviewSeparate limited, unavailable, and review-worthy signals.

Why it mattersExplain the business, delivery, crawl, or implementation impact.

Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.

What this tool cannot checkThis does not enumerate subdomains, scan ports, prove ownership, prove origin IP exposure, or certify infrastructure security.

Client-safe copyClient-safe copy should keep high-level DNS/RDAP/provider findings while suppressing raw payloads and RDAP contact personal data.

Monitoring beta (optional)Optional monitoring beta can compare DNS, RDAP status, expiration windows, provider hints, reverse DNS, and blacklist context for approved public domains.

Client-safe report

Share findings without leaking raw technical material

Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

Review Safe Copy Ask about monitoring beta

Check my website/domain

What this checks

Public DNS, HTTP, HTTPS, certificate, redirect, header, IP/ASN, or domain configuration signals.

Limits

What this cannot check

It cannot perform credentialed vulnerability testing, scan private hosts, bypass access controls, or certify complete security.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.