Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | |
Description | N/A |
Keywords | N/A |
WebSite | www.s-bluevery.com |
Host IP | 112.106.7.48 |
Location | South Korea |
Site | Rank |
US$946,217
Last updated: Sep 14, 2021
S-bluevery.com has global traffic rank of 127,128 and ranks the 2,290th in South Korea. Its global rank has gone up by 70,194 positions since 3 months ago. S-bluevery.com has an estimated worth of US$ 946,217, based on its estimated Ads revenue. S-bluevery.com receives approximately 25,047 unique visitors each day. Its web server is located in South Korea, with IP address 112.106.7.48. According to SiteAdvisor, s-bluevery.com is safe to visit. |
Purchase/Sale Value | US$946,217 |
Daily Ads Revenue | US$518 |
Monthly Ads Revenue | US$15,554 |
Yearly Ads Revenue | US$189,243 |
Daily Unique Visitors | 25,047 |
Note: All traffic and earnings values are estimates. |
Global Rank | 127,128 |
Delta (90 Days) | ⬆️ 70,194 |
Most Popular In Country | South Korea |
Country Rank | 2,290 |
Host | Type | TTL | Data |
s-bluevery.com | A | 300 | IP: 112.106.7.48 |
s-bluevery.com | NS | 300 | Target: auth02.nhn.ic. |
s-bluevery.com | NS | 300 | Target: green.samsung.co.kr. |
s-bluevery.com | NS | 300 | Target: auth01.sam.ic. |
s-bluevery.com | NS | 300 | Target: red.samsung.co.kr. |
s-bluevery.com | NS | 300 | Target: auth02.sam.ic. |
s-bluevery.com | NS | 300 | Target: auth01.nhn.ic. |
s-bluevery.com | SOA | 300 | MNAME: auth01.sam.ic. RNAME: root.s-bluevery.com. Serial: 2020073059 Refresh: 10800 Retry: 3600 Expire: 2419200 Minimum TTL: 300 |
HTTP/1.0 302 Found Location: https://s-bluevery.com/ Server: BigIP Connection: Keep-Alive Content-Length: 0 HTTP/1.1 200 OK Date: Tue, 14 Sep 2021 04:37:23 GMT Server: Apache Last-Modified: Mon, 15 Jan 2018 05:03:53 GMT Accept-Ranges: bytes Content-Length: 316 Pragma: no-cache Expires: Thu, 30 Jun 2012 20:00:00 GMT Cache-Control: max-age=64000,no-store,no-cache,must-revalidate Connection: close Content-Type: text/html; charset=EUC-KR |
Domain Name: S-BLUEVERY.COM Registry Domain ID: 1659442816_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.dotname.co.kr Registrar URL: http://www.dotname.co.kr Updated Date: 2021-05-31T08:12:46Z Creation Date: 2011-06-02T07:50:42Z Registry Expiry Date: 2022-06-02T07:50:42Z Registrar: Dotname Korea Corp. Registrar IANA ID: 1132 Registrar Abuse Contact Email: abuse@dotnamekorea.com Registrar Abuse Contact Phone: +82.7070900820 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: NS.ADOPTEE.COM Name Server: RED.SAMSUNG.CO.KR DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ Domain Name: S-BLUEVERY.COM Registry Domain ID: 1659442816_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.dotname.co.kr Registrar URL: http://www.dotname.co.kr Updated Date: 2021-05-31T08:12:46Z Creation Date: 2011-06-02T07:50:42Z Registry Expiry Date: 2022-06-02T07:50:42Z Registrar: Dotname Korea Corp. Registrar IANA ID: 1132 Registrar Abuse Contact Email: abuse@dotnamekorea.com Registrar Abuse Contact Phone: +82.7070900820 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: NS.ADOPTEE.COM Registrant Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=S-BLUEVERY.COM Administrative Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=S-BLUEVERY.COM Technical Email : dotname.co.kr/domain/whois/domain_search?mode=doit&domain=S-BLUEVERY.COM Name Server: RED.SAMSUNG.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. |