Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | 메고지고 |
Description | 전국여행지검색,맛집검색,숙박검색,여행지추천,국내여행정보최다보유 |
Keywords | N/A |
WebSite | www.megojigo.com |
Host IP | 220.122.127.167 |
Location | Sangju, Gyeongsangbuk-do, South Korea |
Site | Rank |
US$3,528
Last updated: Mar 12, 2023
Megojigo.com has global traffic rank of 23,689,857. Megojigo.com has an estimated worth of US$ 3,528, based on its estimated Ads revenue. Megojigo.com receives approximately 128 unique visitors each day. Its web server is located in Sangju, Gyeongsangbuk-do, South Korea, with IP address 220.122.127.167. According to SiteAdvisor, megojigo.com is safe to visit. |
Purchase/Sale Value | US$3,528 |
Daily Ads Revenue | US$1 |
Monthly Ads Revenue | US$58 |
Yearly Ads Revenue | US$705 |
Daily Unique Visitors | 128 |
Note: All traffic and earnings values are estimates. |
Global Rank | 23,689,857 |
Delta (90 Days) | 0 |
Most Popular In Country | N/A |
Country Rank | N/A |
Host | Type | TTL | Data |
megojigo.com | A | 3600 | IP: 220.122.127.167 |
megojigo.com | MX | 3600 | Priority: 10 Target: ASPMX.daum.net. |
megojigo.com | MX | 3600 | Priority: 20 Target: ALT.ASPMX.daum.net. |
megojigo.com | NS | 3600 | Target: ns3.dothome.co.kr. |
megojigo.com | NS | 3600 | Target: ns2.dothome.co.kr. |
megojigo.com | NS | 3600 | Target: ns1.dothome.co.kr. |
megojigo.com | SOA | 3600 | MNAME: ns1.dothome.co.kr. RNAME: abuse.anysecure.com. Serial: 1479616719 Refresh: 10800 Retry: 3600 Expire: 604800 Minimum TTL: 3600 |
HTTP/1.1 200 OK Date: Sun, 12 Mar 2023 14:57:58 GMT Server: Apache/2.4.6 (CentOS) PHP/5.4.16 X-Powered-By: PHP/5.4.16 P3P: CP="ALL CURa ADMa DEVa TAIa OUR BUS IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE LOC OTC" Set-Cookie: PHPSESSID=goffpnbpq4q7ol3rm7hiv096m2; path=/ Set-Cookie: 2a0d2363701f23f8a75028924a3af643=MTk4Ljc0LjU4LjExOA%3D%3D; expires=Mon, 13-Mar-2023 14:57:58 GMT; path=/ Expires: 0 Last-Modified: Sun, 12 Mar 2023 14:57:58 GMT Cache-Control: pre-check=0, post-check=0, max-age=0 Pragma: no-cache Transfer-Encoding: chunked Content-Type: text/html; charset=utf-8 |
Domain Name: MEGOJIGO.COM Registry Domain ID: 1842799478_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.dotname.co.kr Registrar URL: http://www.dotname.co.kr Updated Date: 2023-01-18T05:35:30Z Creation Date: 2014-01-14T15:49:38Z Registry Expiry Date: 2024-01-14T15:49:38Z 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: NS1.DOTHOME.CO.KR Name Server: NS2.DOTHOME.CO.KR DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ Domain Name: MEGOJIGO.COM Registry Domain ID: 1842799478_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.dotname.co.kr Registrar URL: http://www.dotname.co.kr Updated Date: 2023-01-18T05:35:30Z Creation Date: 2014-01-14T15:49:38Z Registry Expiry Date: 2024-01-14T15:49:38Z 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: NS1.DOTHOME.CO.KR Registrant Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=MEGOJIGO.COM Administrative Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=MEGOJIGO.COM Technical Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=MEGOJIGO.COM Name Server: NS2.DOTHOME.CO.KR DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ 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. |