whois.b1s4.xyz

What is whois?

whois is a browser-based lookup tool that combines two related jobs: DNS record queries and RDAP domain lookups.

DNS records show how a domain is configured to work on the internet. The tool queries A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and 30+ more record types, according to its own description. In practice that covers the common questions: which server hosts a site (A/AAAA), where email is routed (MX), which nameservers are authoritative (NS), and verification or policy entries (TXT, CAA).

RDAP is the structured, modern successor to classic WHOIS. It returns registration data such as registrar, creation and expiry dates, and nameservers in a machine-readable format. Where a domain's registry supports RDAP, it is generally more consistent than legacy WHOIS output.

Who it is for

• Developers and sysadmins checking DNS propagation or a misconfigured record.
• Site owners verifying MX, SPF/TXT or CAA settings after a migration.
• Anyone doing light due diligence on when a domain was registered or who the registrar is.

A practical next step

If a site is not loading, start with the A and AAAA records to confirm the IP addresses, then check NS to see which nameservers are answering. If email is failing, check MX and any TXT records used for sender authentication. If you are assessing a domain, use the RDAP lookup for registrar and registration dates.

Trade-offs

A web lookup is quick and needs no terminal, but it is a point-in-time snapshot: it will not show historical record changes, and results depend on the queried nameservers and registry RDAP support. For regular or scripted checks, command-line tools such as dig or whois remain more flexible.

How can I look up DNS records for a domain using whois?

Enter the domain into whois and run a DNS lookup; the tool queries record types such as A, AAAA, MX, NS, TXT, CNAME, SOA and CAA, covering 30+ types in total. Use it when you want to see how a domain is configured without installing command-line tools.

What each record tells you

• A / AAAA – the IPv4 and IPv6 addresses the domain points to; useful for checking whether a site has moved or still resolves to an old host.
• MX – where email for the domain is delivered; a quick way to see whether a domain uses a mail provider or its own server.
• NS – the nameservers authoritative for the zone; if these look unexpected, DNS may be managed somewhere other than you assumed.
• TXT – often holds verification strings (site ownership, email security policies); handy when checking whether a third-party setup was completed.
• CNAME – shows aliases, common when a subdomain is pointed at a hosted service.
• SOA / CAA – zone metadata and which certificate authorities are allowed to issue certificates for the domain.

A practical scenario

Suppose you are taking over a client's website and want a quick picture before touching anything. Look up the apex domain for A/AAAA and NS, then check www for a CNAME. If the CNAME points to a platform you don't recognise, that's your first question for the client. Then check MX to see where their mail actually goes, and TXT for any verification records that would break if you changed DNS.

Next step

Run the lookup, then cross-check anything surprising against the domain's registrar or hosting dashboard before making changes. For a second opinion on the same records, whois can be compared with a general DNS checker such as DNS Checker, though results should match if propagation is complete.

What is the difference between DNS lookup and RDAP domain lookup?

DNS lookup retrieves the technical records that make a domain work — where its website is hosted, where its email goes, which servers are authoritative. RDAP domain lookup retrieves registration data about who owns or manages the domain — registrar, creation and expiry dates, name servers, and status codes.

whois offers both in one place, querying A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and 30+ other record types alongside RDAP domain data.

What each one actually answers

DNS lookup

• "What IP address does example.com point to?" (A / AAAA)
• "Which servers handle email for this domain?" (MX)
• "Which name servers are authoritative?" (NS)
• "What verification or policy records exist?" (TXT, CAA, SOA)

RDAP domain lookup

• "Which registrar manages this domain?"
• "When was it created, last updated, and when does it expire?"
• "What status flags does it carry?" (e.g. clientTransferProhibited)
• "Which contacts or entities are listed for it?"

A practical comparison

Example scenario

You are buying a domain from a stranger. An RDAP lookup confirms the registrar, expiry date and status flags — useful for spotting a domain locked or about to lapse. A DNS lookup then shows whether it currently points anywhere and whether email is configured, which tells you how actively it is used.

The trade-off to remember

DNS answers reflect the current live configuration and can change within minutes. RDAP answers reflect registration records, which change slowly and are often partially redacted for privacy. Neither replaces the other: use RDAP when you care about ownership and lifecycle, DNS when you care about how the domain behaves right now.

Next step: run both queries on the same domain and compare — if the RDAP name servers differ from the live NS records, that usually means a recent nameserver migration or a misconfiguration worth investigating.

Which DNS record types can I query with whois?

You can query more than 30 DNS record types, including the common ones most people need: A, AAAA, MX, NS, TXT, CNAME, SOA and CAA. The tool also performs RDAP domain lookups, so you can check registration data alongside DNS records.

Common uses

• Verify where a domain's mail goes (MX) or which nameservers are authoritative (NS).
• Check IPv4/IPv6 addressing (A/AAAA) or aliases (CNAME).
• Inspect verification and policy records (TXT, CAA) before changing providers.
• Review zone metadata (SOA) when troubleshooting propagation or serial numbers.

Practical next step Pick the record type that matches your question rather than querying everything: use MX for email routing, NS for delegation, TXT for verification strings, and CAA for certificate issuance permissions. If the result looks stale, compare against a second resolver such as whois and a public resolver like Cloudflare or Google Public DNS to confirm.

How can I use whois to check domain registration details?

Use whois to pull two different kinds of information from one page: RDAP registration data for a domain, and live DNS records for that same name. The RDAP side answers "who registered this and when," while the DNS side answers "where does it currently point."

Checking registration details step by step

1. Enter the bare domain (for example, example.com) rather than a full URL or subdomain.
2. Read the RDAP result for the registrar, creation date, expiry date, last-updated date, and name servers.
3. Check the status flags — labels such as client transfer prohibited or redemption period tell you whether the domain is locked, expiring, or already in a deletion cycle.
4. Cross-check the listed name servers against the DNS lookup on the same page. If the registrar lists ns1.provider.com but the live NS records show something else, the domain has been moved or is mid-transfer.

What DNS adds that RDAP alone does not

The tool queries A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and 30+ other record types. That matters when you are judging whether a domain is actually in use:

• MX records show whether email is configured, which is a strong signal a domain is active rather than parked.
• TXT records often reveal verification strings for Google Workspace, Microsoft 365 or a CDN, telling you which services the owner relies on.
• CAA records show which certificate authorities are allowed to issue for the domain.
• SOA records give the authoritative server and zone refresh timings, useful when diagnosing propagation problems.

A practical scenario

Say a client asks whether a lapsed domain is safe to re-register. Registration data shows the expiry date has passed and the status has moved into a redemption or pending-delete period. The DNS lookup shows no MX and no A record, suggesting the previous site and mailbox are gone. Together those two views support a decision; either one alone is weaker.

Where to double-check

RDAP output is authoritative for gTLDs, but some country-code registries publish limited or differently shaped data. For a second opinion on ownership and registrar reputation, compare with ICANN lookup guidance and, for the DNS side, a resolver such as Google Public DNS.

Decision criterion

Trust the registration data for legal and expiry questions, and trust the DNS records for operational questions about where traffic and mail currently flow. When the two disagree, assume a change is in progress and re-check in a few hours.

What are common use cases for whois DNS and RDAP lookups?

Common uses are diagnosing email and web problems, checking domain ownership and registration details, and verifying DNS configuration before or after a change. WHOIS/RDAP lookups answer “who registered this domain and when does it expire,” while DNS lookups answer “where does this domain currently point and what services does it advertise.”

whois is a lookup tool that queries DNS records and RDAP domain data in one place, covering A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and many more record types.

Typical use cases

• Email deliverability troubleshooting. Check MX records to confirm where mail is routed, and TXT records for SPF, DKIM and DMARC entries. A missing or malformed SPF record is a frequent cause of messages landing in spam.
• Domain ownership and expiry checks. RDAP returns registrar, registration and expiry dates, nameservers and status codes. Useful before buying a domain, chasing an abandoned one, or confirming a client actually controls the domain they claim.
• DNS migration verification. After moving hosting or changing providers, query A/AAAA and CNAME records to confirm propagation and that no stale records remain.
• Security and phishing review. Check whether a domain has CAA records restricting certificate issuance, and inspect TXT records for verification tokens or suspicious entries.
• Subdomain and infrastructure mapping. NS and SOA records reveal which provider hosts DNS, which helps when auditing third-party dependencies.
• Certificate and service configuration. CAA records determine which certificate authorities may issue for a domain — a quick check before debugging TLS issuance failures.

A practical scenario

You send a newsletter and bounce rates spike. Query MX to confirm the mail provider is correct, then TXT to check the SPF record includes that provider and the DMARC policy is not set to reject. If the domain was recently transferred, an RDAP lookup confirms nameservers changed and the registrar’s records match what you expect.

Choosing between the two

Start with DNS when the symptom is “something isn’t resolving or delivering,” and with RDAP when the question is about ownership, expiry or registrar status. Running both on the same domain takes seconds and usually removes the guesswork.