Contact

Tools  /  Security  /  WHOIS Data Parser

SECURITY

WHOIS Data Parser

Parse a raw WHOIS response into normalized fields across registry label variants, with computed domain age/expiry countdown, EPP status code decoding, privacy-proxy detection, and a raw/unmatched fallback view.

More Security tools

Basic Auth Generator Bearer Token Builder Password Strength Checker Passphrase Generator Certificate / DER Structure Viewer PEM Formatter

What this tool does

Parses a raw WHOIS response -- the plain-text record returned by a domain registry -- into normalized, labeled fields, with computed insights the raw text doesn't spell out directly: domain age, days until expiry, and plain-English explanations of the cryptic EPP status codes every WHOIS record carries.

Normalizing label variants

Different registries and registrars format the same field differently -- a creation date might be labeled Creation Date, Created On, Created Date, or Domain Registration Date depending on who's answering the query. This tool recognizes the common variants for each field and normalizes them, rather than only matching one exact label and silently missing the rest.

Computed insights

The raw dates alone don't tell you how old a domain is or how soon it expires -- both computed directly from the parsed creation and expiry dates, with the expiry countdown color-coded by urgency (a domain expiring within 30 days is flagged differently than one with years left).

EPP status codes, decoded

Every WHOIS record includes one or more EPP status codes (clientTransferProhibited, redemptionPeriod, pendingDelete, and about 20 others) that are standard but genuinely cryptic to anyone who hasn't memorized the ICANN spec. Each recognized code is decoded into a plain-English explanation of what it actually means for that domain right now.

Privacy-proxy detection

Since GDPR took effect in 2018, most registrars redact registrant contact details by default -- a WHOIS record showing REDACTED FOR PRIVACY or similar isn't broken or incomplete, it's the expected, compliant result. This tool recognizes that pattern and explains it rather than leaving it looking like missing data.

Nothing silently dropped

Any line that doesn't match a recognized field (or an EPP status code) is shown in a separate raw/unmatched section -- useful for registry-specific fields this tool doesn't have a normalized slot for, so nothing just disappears.

Export

Download the parsed result as structured JSON for use elsewhere -- a script, a report, a ticket.

Privacy

Everything is parsed entirely in your browser. Nothing is uploaded -- this tool only parses WHOIS text you already have, it doesn't perform a live lookup itself.

FAQ

Frequently asked questions

Does this tool perform a live WHOIS lookup?
No -- it parses WHOIS text you already have (from a terminal's whois command, a registrar's lookup page, or an API response) rather than querying a registry itself. Paste the raw response you already retrieved.
Why does it recognize so many different field label variants?
Because different registries and registrars genuinely format the same field differently -- a creation date alone might appear as "Creation Date," "Created On," "Created Date" or "Domain Registration Date" depending on the source. Matching only one exact label would silently miss the others.
What do the EPP status codes actually mean?
They're standardized codes every domain carries describing its current state -- clientTransferProhibited means the registrar has blocked transfers, redemptionPeriod means an expired domain is in its 30-day grace period before deletion, and so on. Each recognized code is decoded into plain English rather than left as cryptic jargon.
Why does my WHOIS result show "REDACTED FOR PRIVACY"?
Since GDPR took effect in 2018, most registrars redact registrant contact details by default for domains with an individual (not organizational) registrant -- that's the expected, compliant result, not missing or broken data. This tool recognizes the pattern and explains it.
What happens to lines this tool doesn't recognize?
They're shown separately in a raw/unmatched section rather than silently dropped -- useful for registry-specific fields that don't map to one of the normalized fields this tool tracks.
How is "days until expiry" calculated?
Directly from the parsed expiry date against the current date/time, with the result color-coded -- red inside 30 days, amber inside 90 days, green otherwise -- so an urgent renewal doesn't get buried in plain text.
Can I export the parsed result?
Yes -- download it as structured JSON for use in a script, a report, or a ticket.
Is anything I paste sent anywhere?
No. Parsing happens entirely in your browser -- this tool has no server component and performs no live lookup of its own.
Theme Accent