HTTP/1.1 200 OK Server: nginx Date: Tue, 24 Sep 2019 06:21:05 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Link: <https://www.healthy-recipes.net/wp-json/>; rel="https://api.w.org/" Vary: Accept-Encoding,User-Agent
| Host | Type | Class | TTL | Extra |
|---|---|---|---|---|
| healthy-recipes.net | SOA | IN | 86400 | mname: ns1.fastsmsshop.com rname: sanjeevadvocateid.gmail.com serial: 2019072704 refresh: 3600 retry: 1800 expire: 1209600 minimum-ttl: 86400 |
| healthy-recipes.net | MX | IN | 14400 | pri: 0 target: healthy-recipes.net |
| healthy-recipes.net | A | IN | 14400 | ip: 209.133.206.18 |
| healthy-recipes.net | TXT | IN | 14400 | txt: v=spf1 ip4:209.133.206.18 +a +mx +ip4:5.254.76.162 ~all entries: Array |
| healthy-recipes.net | NS | IN | 86400 | target: ns4.fastsmsshop.com |
| healthy-recipes.net | NS | IN | 86400 | target: ns1.fastsmsshop.com |
| healthy-recipes.net | NS | IN | 86400 | target: ns2.fastsmsshop.com |
| healthy-recipes.net | NS | IN | 86400 | target: ns3.fastsmsshop.com |
Domain Name: HEALTHY-RECIPES.NET Registry Domain ID: 2413717534_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.dynadot.com Registrar URL: http://www.dynadot.com Updated Date: 2019-07-17T08:19:41Z Creation Date: 2019-07-17T07:30:03Z Registry Expiry Date: 2020-07-17T07:30:03Z Registrar: DYNADOT, LLC Registrar IANA ID: 472 Registrar Abuse Contact Email: abuse@dynadot.com Registrar Abuse Contact Phone: +16502620100 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: NS1.HEALTHY-RECIPES.NET Name Server: NS2.HEALTHY-RECIPES.NET Name Server: NS3.HEALTHY-RECIPES.NET Name Server: NS4.HEALTHY-RECIPES.NET DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of whois database: 2019-09-24T06:20:44Z <<< For more information on Whois status codes, please visit https://icann.org/epp NOTICE: The expiration date displayed in this record is the date the registrar's sponsorship of the domain name registration in the registry is currently set to expire. This date does not necessarily reflect the expiration date of the domain name registrant's agreement with the sponsoring registrar. Users may consult the sponsoring registrar's Whois database to view the registrar's reported date of expiration for this registration. You have exceeded your access quota. Please try again later.
