Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status property behaves differently depending on the current parser #5

Closed
weppos opened this issue Feb 3, 2010 · 1 comment
Closed

Comments

@weppos
Copy link
Owner

weppos commented Feb 3, 2010

Migrated from http://code.simonecarletti.com/issues/343

The status property currently return mixed values. Some parsers return a string, others a symbol ad others an array.
Also, the value is not normalized and current implementation makes the property pointless.

>> Whois.query("google.it").status
=> :"grace-period" 

>> Whois.query("google.com").status
=> ["clientDeleteProhibited", "clientTransferProhibited", "clientUpdateProhibited", "serverDeleteProhibited", "serverTransferProhibited", "serverUpdateProhibited"]

>> Whois.query("google.de").status
=> "connect"

Most common status values

  • available - domain not registered and available for registration
  • registered - domain registered and not available for registration
  • unavailable - domain not registered and not available for registration (786a8ec)
  • reserved - the domain is registered and reserved.
  • inactive - domain registered and no active nameservers ref
  • redemption (e2d15a8, 59a0d1c, 891675e, Quarantine status #33)
  • expired - after redemption
  • suspended - the domain was suspended by the registry, normally in response of a violation
  • invalid - (or error?) normally this is the result of an invalid query or request
@weppos
Copy link
Owner Author

weppos commented Oct 19, 2010

See d25e869

@ghost ghost assigned weppos Apr 30, 2011
tpalmer pushed a commit to tpalmer/whois that referenced this issue Oct 10, 2012
Create whois.wildwestdomains.com parser
@weppos weppos closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant