Type your domain and click Check
WHOIS records of bukakainti.id
Domain Information
Domain Name
bukakainti.id
Domain Status
servertransferprohibited
clienttransferprohibited
autorenewperiod
Nameservers
c1.hidden-server.net
c2.hidden-server.net
c3.hidden-server.net
c4.hidden-server.net
Response from WHOIS Server
If you don't find any information above, check the original response.
ID ccTLD whois server Please see 'whois -h whois.id help' for usage. Domain ID: PANDI-DO2398591 Domain Name: bukakainti.id Created On: 2020-06-30 01:36:22 Last Updated On: 2024-07-03 00:29:18 Expiration Date: 2025-06-30 23:59:59 Status: serverTransferProhibited Status: clientTransferProhibited Status: autoRenewPeriod ==================================================== Sponsoring Registrar Organization: PT Cloud Hosting Indonesia Sponsoring Registrar URL: https://idcloudhost.co.id Sponsoring Registrar Street: Sentral Senayan 2 lt. 16 Sponsoring Registrar City: Jakarta Pusat Sponsoring Registrar State/Province: DKI Jakarta Sponsoring Registrar Postal Code: 10270 Sponsoring Registrar Country: ID Sponsoring Registrar Phone: 02140000995 Sponsoring Registrar Email: [email protected] Name Server: c1.hidden-server.net Name Server: c2.hidden-server.net Name Server: c3.hidden-server.net Name Server: c4.hidden-server.net DNSSEC: Unsigned Abuse Domain Report https://pandi.id/domain-abuse-form/?lang=en For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
What is Whois?
Accoriding to Wikipedia, "WHOIS (pronounced as the phrase "who is") is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block or an autonomous system, but is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format.[1] The current iteration of the WHOIS protocol was drafted by the Internet Society, and is documented in RFC 3912."