Luxypet.com valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title 하나산주식회사
Description N/A
Keywords N/A
Server Information
WebSite luxypet favicon www.luxypet.com
Host IP 183.111.183.120
Location Geumcheon-gu, Seoul, South Korea
Related Websites
Site Rank
More to Explore
lxxre.wordpress.com
lyndseyingram.com
mac-sothis.com
macvim-dev.github.io
made4filmlocations.com
magur.no
mailforwardeasy.com
makeupkingdom.club
malvernrecycling.com
mamamilla.dk
masshar2000.com
masstamilan.pro
Luxypet.com Valuation
US$4,156
Last updated: Jan 5, 2021

Luxypet.com has global traffic rank of 4,079,562. Luxypet.com has an estimated worth of US$ 4,156, based on its estimated Ads revenue. Luxypet.com receives approximately 759 unique visitors each day. Its web server is located in Geumcheon-gu, Seoul, South Korea, with IP address 183.111.183.120. According to SiteAdvisor, luxypet.com is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$4,156
Daily Ads Revenue US$2
Monthly Ads Revenue US$68
Yearly Ads Revenue US$831
Daily Unique Visitors 759
Note: All traffic and earnings values are estimates.
Traffic Ranks
Global Rank 4,079,562
Delta (90 Days) 0
Most Popular In Country N/A
Country Rank N/A
DNS Records
Host Type TTL Data
luxypet.com A 1799 IP: 183.111.183.120
luxypet.com MX 1799 Priority: 10
Target: mw-002.cafe24.com.
luxypet.com NS 1799 Target: ns2.cafe24.co.kr.
luxypet.com NS 1799 Target: ns2.cafe24.com.
luxypet.com NS 1799 Target: ns1.cafe24.com.
luxypet.com NS 1799 Target: ns1.cafe24.co.kr.
luxypet.com TXT 1799 TXT: v=spf1 ip4:183.111.183.120 ~all
luxypet.com SOA 1799 MNAME: luxypet.com.
RNAME: postmaster.luxypet.com.
Serial: 20141022
Refresh: 10800
Retry: 3600
Expire: 3600000
Minimum TTL: 43200
HTTP Headers
HTTP/1.1 200 OK
Server: nginx
Date: Tue, 05 Jan 2021 07:04:20 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 182
Connection: keep-alive
X-Powered-By: PHP/7.0.0p1

Luxypet.com Whois Information
   Domain Name: LUXYPET.COM
   Registry Domain ID: 1829625564_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.dotname.co.kr
   Registrar URL: http://www.dotname.co.kr
   Updated Date: 2020-10-04T08:25:02Z
   Creation Date: 2013-10-02T10:57:49Z
   Registry Expiry Date: 2021-10-02T10:57:49Z
   Registrar: Dotname Korea Corp.
   Registrar IANA ID: 1132
   Registrar Abuse Contact Email: abuse@dotnamekorea.com
   Registrar Abuse Contact Phone: +82.7070900820
   Domain Status: ok https://icann.org/epp#ok
   Name Server: DNS1.CAFE24.CO.KR
   Name Server: DNS1.CAFE24.COM
   Name Server: DNS2.CAFE24.CO.KR
   Name Server: DNS2.CAFE24.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

   Domain Name: LUXYPET.COM
   Registry Domain ID: 1829625564_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.dotname.co.kr
   Registrar URL: http://www.dotname.co.kr
   Updated Date: 2020-10-04T08:25:02Z
   Creation Date: 2013-10-02T10:57:49Z
   Registry Expiry Date: 2021-10-02T10:57:49Z
   Registrar: Dotname Korea Corp.
   Registrar IANA ID: 1132
   Registrar Abuse Contact Email: abuse@dotnamekorea.com
   Registrar Abuse Contact Phone: +82.7070900820
   Domain Status: ok https://icann.org/epp#ok
   Name Server: DNS1.CAFE24.CO.KR
   Registrant Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=LUXYPET.COM
   Administrative Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=LUXYPET.COM
   Technical Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=LUXYPET.COM
   Name Server: DNS1.CAFE24.COM
   Name Server: DNS2.CAFE24.CO.KR
   Name Server: DNS2.CAFE24.COM

URL of the ICANN Whois Inaccurity Complaint Form: https://www.icann.org/wicf/
-status-codes-2014-06-16-en

Notes: 
IMPORTANT: Port43 will provide the ICANN-required minimum data set 
per ICANN Temporary Specification, adopted 17 May 2018. 
https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#appendixA
2.5.1. Registrar MUST provide an email address or a web form to facilitate 
email communication with the relevant contact, 
but MUST NOT identify the contact email address or the contact itself.