whois-parser-next 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 64090073c595bd3cbd6e1a52628cf6d3481de3933b791d9338bf1793922dc6a4
+  data.tar.gz: b15050ea47d7662aedb25a2f0e6e0e8997c7c825b2de70e149dce0f85fd7dd8c
+SHA512:
+  metadata.gz: 8946d38a18bdb012fc79661fc31fcf67f4e63b7cdd728e14dacf48c77a72317322f145544d89b97725f292d4e1860a2aa9ba4842824378745541aea0e9408eee
+  data.tar.gz: 8d10ae4db2cfdf8aee03bc17d4867afd56e03dfa19ddcf4ca31610acbd4957bad49a34a3c6fbbbc2988c77ae42c7f86e1c4ae8e1f2a0bd1342ffe5febd68bbbe

data/CHANGELOG.md

@@ -0,0 +1,80 @@
+# Changelog
+
+This project uses [Semantic Versioning 2.0.0](http://semver.org/).
+
+
+#### Unreleased 0.1.0
+
+- CHANGED: Continued the project as `whois-parser-next`, with the original MIT
+  license, attribution, and Git history preserved.
+- CHANGED: Established Ruby 3.2 as the minimum supported version and refreshed
+  the maintained dependency range.
+- TESTED: Verified CI support through Ruby 4.0.7; Ruby 3.2 remains the minimum
+  supported version.
+- ADDED: Audits and regression fixtures for current registry responses.
+- ADDED: Documented the 2026-09-19 usage-ranked audit through rank 300, using the ICANN DNS
+  Magnitude snapshot dated 2026-09-12 and generated 2026-09-18, retaining
+  source daily-rank positions and classifying `.arpa` outside registrable-domain
+  parser scope.
+- TESTED: The combined audit suite passes 6,640 examples with 0 failures.
+- PACKAGING: The published gem is runtime-only, containing the library and
+  essential documentation while excluding tests, fixtures, and repository
+  automation.
+
+
+#### Release 2.0.0
+
+- CHANGED: Minimum Ruby version 2.6
+
+- FIXED: Addressed security issues with eval and YAML.load. Thanks Francis Beaudoin
+
+
+#### Release 1.2.0
+
+- CHANGED: Updated .ORG parser to the latest response (GH-98, GH-97). [Thanks @talarini]
+- CHANGED: Updated .IO, .AC, .SH, .TM parsers to the latest response.
+- CHANGED: Renamed WhoisDomainKg to WhoisKg (GH-48)
+
+
+#### Release 1.1.0
+
+- NEW: Added .FM parser (GH-74). [Thanks @thomas07vt]
+- NEW: Added .BR parser contacts (GH-31). [Thanks @forain]
+
+- CHANGED: Updated WhoisAi to WhoisNicAi.
+- CHANGED: WhoizBiz to the new response (GH-73). [Thanks @thomas07vt]
+- CHANGED: WhoizNicSt to the new response (GH-72). [Thanks @fturmel]
+- CHANGED: WhoisRegistryNetZa to the new response (GH-43). [Thanks @sheldonh]
+
+- FIXED: Bug where .EU domain property had double .eu suffix (GH-63).
+- FIXED: Fix scanning issue with .ca when keys have no value (GH-36).
+
+
+#### Release 1.0.1
+
+- CHANGED: Updated GoDaddy parser to the new response (GH-60).
+- CHANGED: Updated Donuts parser to the new response. It looks like Donuts is now more compliant with base ICANN parser.
+- CHANGED: Updated Verisign parser to the new response (GH-57). [Thanks @phcyso]
+- CHANGED: Updated .BR parser to the new response (GH-51). [Thanks @otaviojr]
+- CHANGED: Add support for :expires_on to base_nic_fr (GH-54). [Thanks @yastupin]
+
+
+#### Release 1.0
+
+**1.0.0-beta2**
+
+- NEW: Added whois.cdmon.com parser (GH-27). [Thanks @sfumanal]
+
+- FIXED: Fix for Record#respond_to?(:available?) (GH-28, GH-29, GH-30). Thanks [@marcandre]
+
+**1.0.0-beta1**
+
+Initial import from the `whois` library.
+
+- NEW: whois.dk-hostmaster.dk parser now recognizes throttled responses (whois/GH-382). [Thanks @troelskn]
+- NEW: Safer time parsing (GH-18). [Thanks @davidcornu]
+- NEW: Detect reserved .INFO domains (whois/GH-468).
+
+- CHANGED: whois.audns.net.au removed the registrar ID field (GH-20, GH-21). Thanks [@afoster]
+- CHANGED: Updated .JOBS from obswhois.verisign-grs.com to whois.nic.jobs (GH-23).
+- CHANGED: Updated .PRO from whois.dotproregistry.net to whois.afilias.net (GH-24).

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,30 @@
+# Code of Conduct
+
+`whois-parser-next` is a welcoming technical project. We expect contributors,
+maintainers, and users to treat one another with patience, respect, and good
+faith.
+
+## Expected behavior
+
+- Be respectful and constructive.
+- Welcome questions and different levels of experience.
+- Focus criticism on code, evidence, and decisions, not people.
+- Explain disagreements clearly and assume good intentions.
+- Protect private, personal, and security-sensitive information.
+
+## Unacceptable behavior
+
+Harassment, discrimination, personal attacks, intimidation, threats,
+deliberate disruption, unwanted private contact, publishing personal
+information, and any other conduct that would make participation unsafe or
+unwelcoming are not acceptable.
+
+## Enforcement
+
+Maintainers may edit, close, or remove contributions and may restrict
+participation when necessary to protect the project and its community. Serious
+or repeated violations may result in removal from project spaces.
+
+For a conduct concern that cannot be handled publicly, use the private
+reporting path documented in [SECURITY.md](SECURITY.md). Do not publish
+security-sensitive details in a public issue.

data/CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# Contributing to whois-parser-next
+
+Thank you for helping maintain `whois-parser-next`. The project is sponsored
+and supported by [DomScan](https://domscan.net/whois-api), but it is an independent
+community project. Contributions are welcome from everyone who treats
+maintainers, users, and other contributors with respect.
+
+WHOIS behavior changes over time. Reliable evidence and focused pull requests
+help us keep the parser useful.
+
+## Getting started
+
+Fork and clone the repository, then install its dependencies:
+
+```shell
+git clone git@github.com:your-username/whois-parser-next.git
+cd whois-parser-next
+bundle install
+```
+
+Create a focused branch, add fixtures and tests with your change, then run:
+
+```shell
+bundle exec rspec
+```
+
+Open a pull request against
+[`estevecastells/whois-parser-next`](https://github.com/estevecastells/whois-parser-next/compare/).
+
+## Pull request rules
+
+Please follow these rules for every behavior change:
+
+1. Keep one focused registry or server-family change per pull request.
+2. Add exact, current raw-response fixtures for registered and
+   likely-unregistered cases where applicable.
+3. Never include personal registrant data in fixtures. If a current response
+   contains personal data, provide a minimally redacted fixture that preserves
+   the parser-relevant structure and document the redaction.
+4. Never interpret rate limits, blocks, timeouts, malformed responses, or
+   ambiguous responses as either available or absent. Unknown must remain
+   unknown.
+5. Add tests for every behavior change, including successful parsing, expected
+   absence, errors, and important unknown states.
+6. Document the date of live verification and the source or server used.
+7. Do not add paid, private, authenticated, or otherwise inaccessible source
+   dependencies.
+8. Preserve the existing loading path and public API where possible. Discuss
+   proposed breaking changes in an issue before opening the implementation PR.
+9. Run the full test suite before requesting review and report the result in the
+   pull request.
+10. Keep changes understandable and avoid unrelated cleanup in a focused pull
+    request.
+
+A parser result is not an availability guarantee. Registry policy, rate limits,
+server changes, and the distinction between WHOIS and RDAP all matter.
+
+## Fixtures and privacy
+
+Fixtures should represent current server behavior, not invented examples. Do
+not commit names, email addresses, telephone numbers, postal addresses, or
+other personal registrant information. Preserve the fields and response
+structure needed to reproduce the behavior while removing personal data.
+
+Never commit credentials, private endpoints, paid-service responses, or data
+that you are not allowed to redistribute.
+
+## Licensing
+
+Contributions are made under the MIT license. This project does not require a
+Contributor License Agreement. By submitting a contribution, you confirm that
+you have the right to submit it under those terms.
+
+## Review
+
+Maintainers may request narrower scope, stronger evidence, additional fixtures,
+or clearer handling of unknown results. Review is about correctness, evidence,
+privacy, compatibility, and maintainability.
+
+Please follow the project's [Code of Conduct](CODE_OF_CONDUCT.md).

data/GOVERNANCE.md

@@ -0,0 +1,59 @@
+# Governance
+
+## Project status
+
+`whois-parser-next` is an independent, community-maintained successor to
+`weppos/whois-parser`. It is sponsored and supported by
+[DomScan](https://domscan.net/whois-api), which helps fund maintenance and operational
+work.
+
+DomScan sponsorship does not make DomScan the owner of parser truth. It does
+not buy favorable classifications, priority for private requirements, or the
+ability to make the parser report availability or absence when the evidence is
+unknown.
+
+## Maintainer model
+
+The project uses a benevolent-maintainer model. Maintainers are responsible for
+reviewing contributions, protecting compatibility, enforcing project
+standards, and making decisions when consensus is not practical.
+
+Maintainers should explain important decisions in public issues or pull
+requests. Decisions should be based on evidence, correctness, privacy,
+security, compatibility, and the long-term health of the project.
+
+A maintainer may ask for more evidence, narrow a pull request, defer a change,
+or decline it. Substantive decisions should remain visible in the relevant
+issue or pull request whenever doing so does not expose private or
+security-sensitive information.
+
+## Sponsorship boundary
+
+DomScan may propose work, fund maintenance, and contribute code. Sponsorship
+does not permit result manipulation, hidden behavior, preferential parser
+outcomes, or suppression of inconvenient registry evidence.
+
+The same standards apply to contributions from DomScan and from every other
+contributor.
+
+## Security reports
+
+Do not publish suspected vulnerabilities, credentials, private responses, or
+other sensitive security details in public issues or pull requests. Follow the
+private reporting instructions in [SECURITY.md](SECURITY.md).
+
+## Future maintainers
+
+Additional maintainers may be invited based on sustained, high-quality
+contributions, sound technical judgment, respectful collaboration, and
+consistent care for the project's users and evidence standards.
+
+Maintainer status is a responsibility, not a reward. It may be reviewed if a
+maintainer becomes inactive or repeatedly fails to uphold this governance and
+the Code of Conduct.
+
+## Changes to governance
+
+Proposed governance changes should be discussed publicly in an issue or pull
+request. Maintainers may adopt changes after considering community feedback
+and documenting the decision.

data/LICENSE.txt

@@ -0,0 +1,22 @@
+The MIT License (MIT)
+
+Copyright (c) 2009-2022 Simone Carletti
+Copyright (c) 2026 Esteve Castells and whois-parser-next contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/MAINTAINERS.md

@@ -0,0 +1,44 @@
+# Maintainers
+
+## Project owner and lead maintainer
+
+Esteve Castells ([@estevecastells](https://github.com/estevecastells)) is the
+project owner and lead maintainer of `whois-parser-next`.
+
+Responsibilities include:
+
+- Setting project direction and maintaining the public roadmap
+- Reviewing code, fixtures, issues, and pull requests
+- Protecting API compatibility and evidence standards
+- Coordinating releases, security response, and maintainer access
+- Ensuring parser results do not turn uncertain evidence into availability or
+  absence
+- Maintaining clear attribution to the original project and its contributors
+
+The project is sponsored and supported by
+[DomScan](https://domscan.net/whois-api). Sponsorship supports maintenance and
+does not give any sponsor control over parser results or review decisions.
+
+## Contributor to maintainer
+
+Contributors may be invited to become maintainers after sustained,
+high-quality work that demonstrates:
+
+- Reliable registry or server-family contributions
+- Strong tests and current, privacy-safe fixtures
+- Careful treatment of unknown and ambiguous responses
+- Respectful, constructive collaboration
+- Sound judgment during issue and pull request review
+
+There is no fixed contribution count or automatic promotion process. Maintainer
+invitations are based on demonstrated responsibility and project needs.
+
+## Original-project attribution
+
+`whois-parser-next` is an independent, community-maintained successor to
+[`weppos/whois-parser`](https://github.com/weppos/whois-parser).
+
+The original project was created and maintained by Simone Carletti, known as
+`weppos`, together with its contributors. This project preserves the original
+MIT license heritage and attribution. It is not affiliated with or endorsed by
+Simone Carletti or `weppos`.

data/README.md

@@ -0,0 +1,123 @@
+# whois-parser-next
+
+`whois-parser-next` is an independent, community-maintained successor to
+[`weppos/whois-parser`](https://github.com/weppos/whois-parser).
+
+The original project was created and maintained by Simone Carletti, known as
+`weppos`, together with its contributors. We are grateful for that work and
+for the foundation it provides. This project preserves the original MIT
+license heritage, attribution, notices, and Git history while continuing
+development under a new name.
+
+This project is independent and is not affiliated with or endorsed by Simone
+Carletti or `weppos`.
+
+[![Tests](https://github.com/estevecastells/whois-parser-next/actions/workflows/tests.yml/badge.svg)](https://github.com/estevecastells/whois-parser-next/actions/workflows/tests.yml)
+
+## Sponsored and supported by DomScan
+
+`whois-parser-next` is sponsored and supported by
+[DomScan](https://domscan.net/whois-api), which uses domain intelligence in production
+and helps fund maintenance, testing, and registry-format research.
+
+The project remains independent from DomScan and independent from the original
+`weppos/whois-parser` maintainer. DomScan sponsorship does not imply
+endorsement by Simone Carletti or `weppos`, and it does not give any sponsor
+the right to influence parser results.
+
+WHOIS formats drift. Parsers should keep up.
+
+Project owner and lead maintainer:
+[Esteve Castells](https://github.com/estevecastells). See
+[MAINTAINERS.md](MAINTAINERS.md) and [GOVERNANCE.md](GOVERNANCE.md).
+
+## Status
+
+The project is under active development. The initial focus is reliable parsing
+of current WHOIS responses, explicit unknown states, registry-specific
+fixtures, and safe handling of malformed, rate-limited, retired, or changed
+server responses.
+
+The current development gem name is `whois-parser-next`. It has not yet been
+published to RubyGems.
+
+## Compatibility
+
+The compatibility target is the existing `whois-parser` loading path and
+namespace:
+
+```ruby
+require "whois-parser"
+
+Whois::Parser
+```
+
+Existing applications can retain `require "whois-parser"` and their
+`Whois::Parser` integrations while changing the dependency source:
+
+```ruby
+gem "whois-parser-next",
+  github: "estevecastells/whois-parser-next",
+  require: "whois-parser"
+```
+
+## Requirements
+
+- Ruby 3.2 or newer
+
+## Scope
+
+The project parses and normalizes WHOIS responses. It does not guarantee domain
+availability. Registry policies, server responses, rate limits, endpoint
+changes, and the distinction between WHOIS and RDAP can all affect the result.
+
+Unknown, malformed, unsupported, rate-limited, and ambiguous responses must
+remain distinguishable from an authoritative availability result.
+
+## Development
+
+```shell
+bundle install
+bundle exec rspec
+```
+
+## Coverage evidence
+
+The 2026-09-19 live audit covers the ICANN DNS Magnitude ordering through rank
+300. Start with the [Top 20 review](docs/audits/top-20-tlds-2026-09-19.md) and
+[Top 100 audit](docs/audits/top-100-tlds-2026-09-19.md); the same directory
+contains the contiguous 25-TLD reports for ranks 101 through 300. Each report
+separates verified parsing from unavailable, retired, restricted, web-only,
+and unresolved WHOIS paths.
+
+## Join the work
+
+We want this to be useful to people who maintain domain tools, registry
+integrations, security services, and developer libraries. Small, focused
+contributions are welcome. You do not need to be a long-time Ruby contributor
+or a WHOIS expert to help.
+
+Useful contributions include current registry fixtures, parser corrections,
+tests, documentation, and careful reports of changed server behavior. If you
+are unsure whether an observation is a bug, open an issue with the TLD, source,
+date, sanitized response shape, and expected interpretation. We would rather
+help shape an investigation than lose a useful report because it was not
+perfectly packaged.
+
+Please read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.
+The [public roadmap](ROADMAP.md) lists current priorities, non-goals, and the
+evidence gate for any optional Rust work.
+Maintainers should also follow [RELEASING.md](RELEASING.md), including the
+package smoke test and trusted-publishing checks.
+
+## License and attribution
+
+This project continues work derived from the MIT-licensed
+[`weppos/whois-parser`](https://github.com/weppos/whois-parser) project.
+
+Original author: Simone Carletti (`weppos`)
+
+Original project: <https://github.com/weppos/whois-parser>
+
+See [LICENSE.txt](LICENSE.txt) and the retained attribution notices for the
+applicable terms. New contributions remain available under the MIT license.

data/RELEASING.md

@@ -0,0 +1,43 @@
+# Releasing whois-parser-next
+
+Releases are made from a reviewed commit on `main` and published to RubyGems
+through GitHub's trusted-publishing flow. Maintainers must not add a long-lived
+RubyGems API key to the repository or its Actions secrets.
+
+## Before tagging
+
+1. Confirm the version in `lib/whois/parser/version.rb` and prepare a dated
+   changelog entry.
+2. Run the complete test suite with `bundle exec rspec`.
+3. Run `./script/package-smoke` and inspect the built gem's file list.
+4. Confirm the GitHub Actions matrix passes on every supported Ruby version.
+5. Confirm the RubyGems trusted publisher names this repository,
+   `.github/workflows/release.yml`, and the `release` environment.
+6. Review the diff from the previous release for fixtures containing personal
+   data, credentials, or unneeded registry response content.
+
+## Publish
+
+Create and push the annotated release tag only after the checks above pass:
+
+```shell
+git tag -a v0.1.0 -m "whois-parser-next 0.1.0"
+git push origin v0.1.0
+```
+
+The release workflow repeats the full suite and package smoke test before it
+requests a short-lived RubyGems publishing credential through OIDC.
+
+## Verify
+
+After the workflow succeeds:
+
+1. Confirm the version and metadata on RubyGems.
+2. Install the released gem into an empty gem home.
+3. Verify `require "whois-parser"` and `Whois::Parser`.
+4. Parse at least one registered and one available fixture.
+5. Publish release notes that describe only tested behavior.
+
+If a release is wrong, stop downstream upgrades and document the issue before
+yanking. A yank does not remove code already downloaded by users, so follow it
+with a corrected release and a clear changelog entry.

data/ROADMAP.md

@@ -0,0 +1,59 @@
+# Roadmap
+
+This roadmap is a direction, not a promise of dates. Registry behavior changes
+without notice, so correctness and current evidence take priority over a fixed
+feature calendar.
+
+## Current release
+
+- Establish a safe, maintained successor with Ruby 3.2 through Ruby 4 support.
+- Audit the first 300 rows of a dated, reproducible TLD-usage snapshot.
+- Replace unsafe fallback classifications with explicit unknown or unavailable
+  outcomes when a response lacks authoritative evidence.
+- Keep the gem compatible with `require "whois-parser"` and `Whois::Parser`.
+- Publish through short-lived RubyGems trusted-publishing credentials.
+
+## Next priorities
+
+1. Continue evidence-backed TLD coverage in reproducible, non-overlapping
+   batches.
+2. Add regression fixtures when registries change format, server, policy, or
+   availability wording.
+3. Reduce avoidable runtime dependencies without changing public behavior.
+4. Improve contributor tooling for fixture privacy, server-mapping drift, and
+   ambiguous-response safety.
+5. Document parser confidence and provenance without pretending that a parsed
+   WHOIS response is an availability guarantee.
+
+## Performance and Rust
+
+The Ruby parser is already small compared with the network request that
+produces a WHOIS response. We will profile real workloads before adding native
+code or attempting a rewrite.
+
+If parsing becomes a measured bottleneck, the preferred experiment is a small,
+optional Rust-backed parser for one high-volume server family behind the
+existing Ruby API. It must pass the same fixtures and differential tests as the
+Ruby implementation. A full rewrite is not planned without evidence that it
+would improve user-visible performance enough to justify the maintenance,
+packaging, and compatibility cost.
+
+## Non-goals
+
+- Guessing availability from an empty, blocked, throttled, or malformed reply.
+- Hiding registry limitations or converting unknown evidence into certainty.
+- Adding paid, private, or authenticated data sources to the parser.
+- Breaking the established Ruby API merely to modernize internal style.
+- Combining WHOIS transport, RDAP policy, billing, or product-specific routing
+  into this parsing library.
+
+## How to help
+
+Good first contributions include a current sanitized fixture, a focused parser
+regression, a server-mapping correction, or an adversarial unknown-response
+test. Larger proposals should start in a public issue so contributors and
+maintainers can agree on the evidence, compatibility boundary, and test plan
+before implementation.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the rules and
+[GOVERNANCE.md](GOVERNANCE.md) for how decisions are made.

data/SECURITY.md

@@ -0,0 +1,41 @@
+# Security Policy
+
+## Supported versions
+
+Until the first release, only the current main branch is supported.
+
+| Version | Supported |
+|---|---|
+| main | Yes |
+| Released versions | No released versions yet |
+
+## Reporting a vulnerability
+
+Please use [GitHub private vulnerability reporting](https://github.com/estevecastells/whois-parser-next/security/advisories/new).
+
+Do not open a public issue or pull request for a suspected vulnerability.
+
+Please include:
+
+- A clear description of the issue and its impact
+- A minimal reproduction or proof of concept
+- The affected commit, branch, or dependency version
+- The Ruby version and relevant environment details
+- The TLD, WHOIS server, and observed date where relevant
+- Expected behavior and actual behavior
+- Sanitized response examples where needed
+- Any suggested mitigation
+
+Remove credentials, access tokens, private endpoints, personal registrant data,
+and other sensitive information before submitting a report. Do not include
+secrets or private source responses in public fixtures.
+
+## Disclosure
+
+Please do not disclose a vulnerability publicly before the maintainers have had
+an opportunity to investigate, coordinate a fix or mitigation, and agree on
+disclosure timing.
+
+We expect to acknowledge reports after they reach the maintainers and provide
+follow-up after triage. Workload and severity vary, so no exact response or
+remediation timeline is promised.

data/lib/whois/parser/contact.rb

@@ -0,0 +1,56 @@
+require_relative 'super_struct'
+
+
+module Whois
+  class Parser
+
+    # Holds the details of a contact extracted from the WHOIS response.
+    #
+    # A contact is composed by the several attributes,
+    # accessible through corresponding getter / setter methods.
+    #
+    # Please note that a response is not required to provide
+    # all the attributes. When an attribute is not available,
+    # the corresponding value is set to nil.
+    #
+    # @attr [String] id
+    # @attr [String] type
+    # @attr [String] name
+    # @attr [String] organization
+    # @attr [String] address
+    # @attr [String] city
+    # @attr [String] zip
+    # @attr [String] state
+    # @attr [String] country
+    # @attr [String] country_code
+    # @attr [String] phone
+    # @attr [String] fax
+    # @attr [String] email
+    # @attr [String] url - e. g. to the contact form
+    # @attr [Time] created_on
+    # @attr [Time] updated_on
+    #
+    class Contact < SuperStruct.new(:id, :type, :name, :organization,
+                                    :address, :city, :zip, :state, :country, :country_code,
+                                    :phone, :fax, :email, :url,
+                                    :created_on, :updated_on)
+
+      TYPE_REGISTRANT     = 1
+      TYPE_ADMINISTRATIVE = 2
+      TYPE_TECHNICAL      = 3
+
+
+      def self.const_missing(name)
+        case name
+        when :TYPE_ADMIN
+          Whois.deprecate("Whois::Record::Contact::TYPE_ADMIN is now Whois::Record::Contact::TYPE_ADMINISTRATIVE")
+          const_set(name, TYPE_ADMINISTRATIVE)
+        else
+          super
+        end
+      end
+
+    end
+
+  end
+end