7mscore.Co.Kr - Info 7mscore.co.kr

7mscore.co.kr receives about 454 unique visitors and 454 (1.00 per visitor) page views per day which should earn about $1.85/day from advertising revenue. Estimated site value is $1,351.08. According to Alexa Traffic Rank 7mscore.co.kr is ranked number 3,125,494 in the world and 1.0E-5% of global Internet users visit it. Site is hosted in South Korea and links to network IP address 121.78.236.96. This server doesn't support HTTPS and doesn't support HTTP/2.

About - 7mscore.co.kr


Technologies used on Website

Web Servers
Apache
Programming Languages
PHP

7mscore.co.kr Profile

Title: 7M스코어 - 7M라이브스코어 7M스포츠 7msports 7m데이터센터
Last update was 7 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with 7mscore.co.kr in any way. Only publicly available statistics data are displayed.

How popular is 7mscore.co.kr?

454 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
454
Monthly Unique Visitors:
10,896
Pages per Visit:
1.00
Daily Pageviews:
454
Alexa Rank:
3,125,494 visit alexa
Alexa Reach:
1.0E-5%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  7mscore.co.kr
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is 7mscore.co.kr?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
7mscore.co.kr
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
7mscore.co.kr
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much 7mscore.co.kr can earn?

Daily Revenue:
$1.85
Monthly Revenue:
$55.50
Yearly Revenue:
$675.25
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do 7mscore.co.kr lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is 7mscore.co.kr worth?

Website Value:
$1,351.08

+ Where is 7mscore.co.kr hosted?

Server IP:
121.78.236.96
ASN:
AS9286 
ISP:
KINX 
Server Location:

South Korea, KR
 

Other sites hosted on 121.78.236.96

+ How fast does 7mscore.co.kr load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 39 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/
1 KB
http://7mscore.co.kr/?ckattempt=2
1 KB
http://7mscore.co.kr/?ckattempt=1
1 KB
http://7mscore.co.kr/?ckattempt=3
1 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
34 ms
Script Evaluation
31 ms
Style & Layout
18 ms
Script Parsing & Compilation
9 ms
Parse HTML & CSS
4 ms
Rendering
3 ms
Avoids an excessive DOM size - 8 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
8
Maximum DOM Depth
5
Maximum Child Elements
3
Preload key requests - Potential savings of 170 ms
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

URL
Potential Savings
http://7mscore.co.kr/cupid.js
170
http://7mscore.co.kr/cupid.js
100
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://7mscore.co.kr/cupid.js
8 KB3 KB
Keep request counts low and transfer sizes small - 8 requests • 39 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
839 KB
Script
434 KB
Document
45 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://7mscore.co.kr/
0 ms202 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
214 ms416 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/?ckattempt=1
428 ms634 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/?ckattempt=2
655 ms862 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
645 ms645 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/?ckattempt=3
882 ms1089 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
873 ms873 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/cupid.js
1099 ms1099 ms8 KB30 KB200application/x-javascriptScript
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
224 ms
7 ms
437 ms
9 ms
656 ms
7 ms
664 ms
9 ms
884 ms
7 ms
892 ms
9 ms
1111 ms
7 ms
1118 ms
9 ms
1127 ms
19 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
68 ms5 ms4 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 200 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)959ms 0% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 76% 22% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 22% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)1.5s 68% of loads for this page have a fast (<100ms) First Input Delay (FID) 68% 15% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 15% 15% of loads for this page have a slow (>300ms) First Input Delay (FID) 15%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)906ms 79% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 79% 20% of loads for this page have an average (1s ~ 3s) First Contentful Paint (FCP) 20% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)915ms 0% of loads for this page have a fast (<100ms) First Input Delay (FID) 43% 44% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 44% 11% of loads for this page have a slow (>300ms) First Input Delay (FID) 11%

Lab Data

Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 3495 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 39 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/cupid.js
8 KB
http://7mscore.co.kr/?ckattempt=1
1 KB
http://7mscore.co.kr/
1 KB
http://7mscore.co.kr/?ckattempt=2
1 KB
http://7mscore.co.kr/?ckattempt=3
1 KB
Minimizes main-thread work - 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Other
190 ms
Style & Layout
156 ms
Script Evaluation
144 ms
Script Parsing & Compilation
44 ms
Parse HTML & CSS
20 ms
Rendering
19 ms
Avoids an excessive DOM size - 8 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
8
Maximum DOM Depth
5
Maximum Child Elements
3
Preload key requests - Potential savings of 690 ms
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

URL
Potential Savings
http://7mscore.co.kr/cupid.js
690
http://7mscore.co.kr/cupid.js
510
http://7mscore.co.kr/?ckattempt=2
330
http://7mscore.co.kr/cupid.js
180
Minify JavaScript - Potential savings of 3 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://7mscore.co.kr/cupid.js
8 KB3 KB
Keep request counts low and transfer sizes small - 8 requests • 39 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
839 KB
Script
434 KB
Document
45 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Other
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://7mscore.co.kr/
0 ms202 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
217 ms458 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/?ckattempt=1
474 ms681 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/?ckattempt=2
706 ms914 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
693 ms693 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/?ckattempt=3
938 ms1147 ms1 KB2 KB200text/htmlDocument
http://7mscore.co.kr/cupid.js
927 ms928 ms8 KB30 KB200application/x-javascriptScript
http://7mscore.co.kr/cupid.js
1167 ms1167 ms8 KB30 KB200application/x-javascriptScript
Serve static assets with an efficient cache policy - 4 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
http://7mscore.co.kr/cupid.js
0 ms8 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
230 ms
9 ms
484 ms
9 ms
707 ms
8 ms
716 ms
13 ms
941 ms
9 ms
951 ms
10 ms
1174 ms
14 ms
1190 ms
10 ms
1200 ms
40 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
425 ms22 ms18 ms
Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests - 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 200 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Currently Not Available

+ Does 7mscore.co.kr use compression?

7mscore.co.kr use gzip compression.
Original size: 25.12 KB
Compressed size: 1 KB
File reduced by: 24.11 KB (96%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

7mscore.co.kr does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

7mscore.co.kr does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Tue, 24 Mar 2020 12:05:03 GMT
Server: httpd-2.4.3
X-Powered-By: PHP/5.3.28
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=ls52jcg42roq6jj3ncdtjecko4; path=/
Set-Cookie: 2a0d2363701f23f8a75028924a3af643=NjcuMjEyLjE4Ny4xMDY%3D; expires=Wed, 25-Mar-2020 12:05:03 GMT; path=/
Expires: 0
Last-Modified: Tue, 24 Mar 2020 12:05:03 GMT
Cache-Control: pre-check=0, post-check=0, max-age=0
Pragma: no-cache
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8

+ DNS Lookup

Type Ip Target TTL
SOA 1600
Mname ns1.hubweb.net
Rname webmaster.hubweb.net
Serial Number 2019122622
Refresh 10800
Retry 900
Expire 604800
Minimum TTL 0
A 121.78.236.96 1460
NS ns2.hubweb.net 1600
NS ns1.hubweb.net 1600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.kr...
query : 7mscore.co.kr


# KOREAN(UTF8)

도메인이름 : 7mscore.co.kr
등록인 : 김은희
책임자 : 김은희
책임자 전자우편 : email
등록일 : 2018. 11. 07.
최근 정보 변경일 : 2018. 11. 07.
사용 종료일 : 2020. 11. 07.
정보공개여부 : N
등록대행자 : 메가존(주)(http://HOSTING.KR)
DNSSEC : 미서명
등록정보 보호 : clientTransferProhibited

1차 네임서버 정보
호스트이름 : ns1.cafe24.com

2차 네임서버 정보
호스트이름 : ns1.cafe24.co.kr
IP 주소 : 112.175.246.232
호스트이름 : ns2.cafe24.com
호스트이름 : ns2.cafe24.co.kr
IP 주소 : 112.175.247.232

네임서버 이름이 .kr이 아닌 경우는 IP주소가 보이지 않습니다.


# ENGLISH

Domain Name : 7mscore.co.kr
Registrant : eunhee kim
Administrative Contact(AC) : eunhee kim
AC E-Mail : email
Registered Date : 2018. 11. 07.
Last Updated Date : 2018. 11. 07.
Expiration Date : 2020. 11. 07.
Publishes : N
Authorized Agency : Megazone(http://HOSTING.KR)
DNSSEC : unsigned
Domain Status : clientTransferProhibited

Primary Name Server
Host Name : ns1.cafe24.com

Secondary Name Server
Host Name : ns1.cafe24.co.kr
IP Address : 112.175.246.232
Host Name : ns2.cafe24.com
Host Name : ns2.cafe24.co.kr
IP Address : 112.175.247.232


- KISA/KRNIC WHOIS Service -
Last update was 7 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with 7mscore.co.kr in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
7mscore.co.kr widget