E-shishobako.ne.jp
E-私書箱
Domain Summary
What percent of global Internet users visit E-shishobako.ne.jp?
• 0.0018498% of global Internet users visit E-shishobako.ne.jp
How many people visit E-shishobako.ne.jp each day?
• E-shishobako.ne.jp receives approximately 91.2K visitors and 355,282 page impressions per day.
Which countries does E-shishobako.ne.jp receive most of its visitors from?
• E-shishobako.ne.jp is mostly visited by people located in Japan,United States,Indonesia.
How much E-shishobako.ne.jp can earn?
• E-shishobako.ne.jp should earn about $130.03/day from advertising revenue.
What is E-shishobako.ne.jp estimated value?
• Estimated value of E-shishobako.ne.jp is $134,168.30.
What IP addresses does E-shishobako.ne.jp resolve to?
• E-shishobako.ne.jp resolves to the IP addresses 45.223.62.151.
Where are E-shishobako.ne.jp servers located in?
• E-shishobako.ne.jp has servers located in United States.
e-shishobako.ne.jp Profile

e-shishobako.ne.jp Traffic Analysis
This website is viewed by an estimated 91.2K visitors daily, generating a total of 355.3K pageviews. This equates to about 2.8M monthly visitors. E-shishobako.ne.jp traffic has decreased by 12.44% compared to last month.Daily Visitors91.2K
6.47%
Monthly Visits2.8M
12.44%
Pages per Visit3.90
13.95%
Visit duration03:04
36.36%
Bounce Rate31.55%
126.99%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 91,192
- Monthly Visits:
- 2,763,118
- Pages per Visit:
- 3.90
- Daily Pageviews:
- 355,282
- Avg. visit duration:
- 03:04
- Bounce rate:
- 31.55%
- Global Reach:
- 0.0018498%
- Monthly Visits (SEMrush):
- 2,921,259
- Monthly Unique Visitors (SEMrush):
- 1,405,305
- Monthly Visits (SimilarWeb):
- 2,791,587
- HypeRank:
- n/a
- SEMrush Rank:
- 12,881,611
- SimilarWeb Rank:
- 19,162
Traffic sources
- Direct:
- 30.97%
- Referral:
- 67.80%
- Search:
- 1.24%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 75.37%
- Mobile:
- 24.63%
Total Visits Last 3 Months
2.2M
DEC
3.2M
JAN
2.8M
FEB
Visitors by country
- Country
- Users%
- Japan 99.83%
- United States 0.14%
- Indonesia 0.02%
- Taiwan 0.02%
Backlinks Report ▼
E-shishobako.ne.jp has a total of 511 backlinks from 285 referring domains and most of them comes from Singapore.- Total Backlinks:
- 511
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 285
- Referring IPs:
- 129
- Authority Domain Score:
- 37
Backlinks by country
- Country
- Domains
- Singapore 177
- Japan 38
- United States 29
- Romania 6
- Finland 1
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 105
- .in
- 42
- .jp
- 32
- .edu
- 0
- .gov
- 0
Which sites are competitors to e-shishobako.ne.jp?
Websites similar to e-shishobako.ne.jp are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.- Domain
- CompareDaily Visitors
- kabushiki.jp
- Compare >8.6K
Last update was 41 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with e-shishobako.ne.jp in any way. Only publicly available statistics data are displayed.
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- e-shishobako.ne.jp
- Rank:
(Rank based on keywords, cost and organic traffic) - 12,881,611
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 137
- 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
Revenue report ▼
Google.com would generate approximately $130 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $3.9K and annual gross revenue of approximately $47.5K. Based on these figures, the site's net worth is estimated at around $134.2K.How much would e-shishobako.ne.jp make?
- Daily Revenue:
- $130.03
- Monthly Revenue:
- $3,900.90
- Yearly Revenue:
- $47,460.95
Daily earning by country
- CountryPageviewsEarning
- Japan 354,687$127.69
- United States 480$2.32
- Taiwan 56$0.01
- Indonesia 59$0.01
Loss of money due to Adblock?
- Daily Revenue Loss:
- $4.25
- Monthly Revenue Loss:
- $127.62
- Yearly Revenue Loss:
- $1,552.71
- Daily Pageviews Blocked:
- 10,770
- Monthly Pageviews Blocked:
- 323,106
- Yearly Pageviews Blocked:
- 3,931,118
Daily revenue loss by country
- CountryBlockedLost Money
- Japan 10,641$3.83
- United States 86$0.42
- Indonesia 34$0.00
- Taiwan 9$0.00
How much is e-shishobako.ne.jp worth?
- Website Value:
- $134.2K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- e-shishobako.ne.jp
- 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
Desktop summary
- Root domain:
- e-shishobako.ne.jp
- 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 ▼
Summary of the abusive experience rating of a website.- Root domain:
- e-shishobako.ne.jp
- 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
Where is e-shishobako.ne.jp hosted? ▼
E-shishobako.ne.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 45.223.62.151
- ASN:
- AS19551
- ISP:
- Incapsula Inc
- Server Location:
United States, US
Other sites hosted on 45.223.62.151
There are no other sites hosted on this IPHow fast does e-shishobako.ne.jp load? ▼
The average loading time of e-shishobako.ne.jp is 758 ms. The Desktop speed index is 99 and mobile speed index is 86.- Average Load Time:
- 758 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)100ms
First Contentful Paint (FCP)291ms
First Input Delay (FID)0
Interaction To Next Paint (INP)31ms
Largest Contentful Paint (LCP)309ms
Origin Data
All pages served from this origin have an FAST 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.
Cumulative Layout Shift (CLS)1ms
Time To First Byte (TTFB)254ms
First Contentful Paint (FCP)692ms
First Input Delay (FID)0
Interaction To Next Paint (INP)35ms
Largest Contentful Paint (LCP)760ms
Lab Data
Font display
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Time to Interactive 0.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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 how to minimize third-party impact
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 how to minimize third-party impact
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
CSS Selector costs
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Long critical network tree
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)323ms
First Contentful Paint (FCP)876ms
First Input Delay (FID)0
Interactive To Next Paint (INP)95ms
Largest Contentful Paint (LCP)1.0s
Origin Data
All pages served from this origin have an FAST 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.
Cumulative Layout Shift (CLS)0ms
Time To First Byte (TTFB)323ms
First Contentful Paint (FCP)876ms
First Input Delay (FID)0
Interactive To Next Paint (INP)95ms
Largest Contentful Paint (LCP)1.0s
Lab Data
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Time to Interactive 3.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
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 how to minimize third-party impact
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 how to minimize third-party impact
First Contentful Paint 2.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint 3.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Long critical network tree
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Font display
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
CSS Selector costs
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Does e-shishobako.ne.jp use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on e-shishobako.ne.jp are reduced by 69%.
e-shishobako.ne.jp use gzip compression.
Original size: 6.87 KB
Compressed size: 2.1 KB
File reduced by: 4.77 KB (69%)
Compressed size: 2.1 KB
File reduced by: 4.77 KB (69%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious
MyWot.com Reputation Ratings
MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. e-shishobako.ne.jp has 80 Safety Reputations.- Status:
- SAFE
- Safety Reputations:
- 80
- Safety Confidence:
- 51
SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. e-shishobako.ne.jp supports HTTPS. e-shishobako.ne.jp supports HTTPS
Verifying SSL Support. Please wait...
Common Name: e-shishobako.ne.jp
Organization: "Nomura Research Institute, Ltd."
Location: Chiyoda-ku, street = 1-9-2 Otemachi, Tokyo, JP
Issuer: GlobalSign Extended Validation CA - SHA256 - G3
Valid from: Nov 22 06:46:02 2024 GMT
Valid until: Dec 24 06:46:01 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization: "Nomura Research Institute, Ltd."
Location: Chiyoda-ku, street = 1-9-2 Otemachi, Tokyo, JP
Issuer: GlobalSign Extended Validation CA - SHA256 - G3
Valid from: Nov 22 06:46:02 2024 GMT
Valid until: Dec 24 06:46:01 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GlobalSign Extended Validation CA - SHA256 - G3
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Sep 21 00:00:00 2016 GMT
Valid until: Sep 21 00:00:00 2026 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Sep 21 00:00:00 2016 GMT
Valid until: Sep 21 00:00:00 2026 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. e-shishobako.ne.jp does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.Date: Sun, 16 Mar 2025 06:30:31 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
Pragma: no-cache
Cache-Control: must-revalidate
Cache-Control: no-cache
Cache-Control: no-store
Expires: Wed, 31 Dec 1969 23:59:59 GMT
Content-Language: ja-JP
Strict-Transport-Security: max-age=15768000; includeSubDomains
Set-Cookie: JSESSIONID=t1bEwvKtJkNYfr02MiRe9Zig; Path=/; Secure; HttpOnly
Set-Cookie: cookie_e-shishobako.ne.jp_lo_a_1_443=!aab9guTPYnp8RyEsvlCQ+4Stb9zn49zB631G2CjVrsq7jCX/8PptnBS+gWAHrNQcwfq41A0v3Hcr; path=/; HttpOnly
Content-Encoding: gzip
Set-Cookie: cookie_e-shishobako.ne.jp_443=!PYaN3KPBLzfMFJipkAuSRoR5wIZs5zxrqaECDV+nkKOPOKcwf15ZdKbB6+K1DaUL0l+LghlvEmBI; path=/
Set-Cookie: TS01c30e9e=01ad159b578d1960814cfbf50e162e2e0ce262f2fbbc29ba7c0a9394120a5bb6f6fc91abcc0bce1159daacee54ac449dbf8cbfd822; Path=/
Transfer-Encoding: chunked
Set-Cookie: visid_incap_2939260=XGWBhe48QO+r/ftQ5Ps4WQdw1mcAAAAAQUIPAAAAAAByCibr31n9lXRk1qPj+b+G; expires=Sun, 15 Mar 2026 07:53:06 GMT; HttpOnly; path=/; Domain=.e-shishobako.ne.jp
Set-Cookie: nlbi_2939260=uiz/YYvA7lRc4xm/wuFaowAAAADCNgDqvRjv+TJ2kHZSzKVp; HttpOnly; path=/; Domain=.e-shishobako.ne.jp
Set-Cookie: incap_ses_1845_2939260=NecyW0/YEgWphbL4CMKaGQdw1mcAAAAAdvSxDqbYHMnKjty/LxBZZg==; path=/; Domain=.e-shishobako.ne.jp
X-CDN: Imperva
X-Iinfo: 58-177479746-177479757 NNNN CT(167 333 0) RT(1742106630550 33) q(0 0 5 -1) r(7 7) U5
DNS Lookup ▼
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.Type | Ip | Target/Txt | TTL |
SOA | 3600 | ||
Mname | master.dns.ne.jp | ||
Rname | tech.sakura.ad.jp | ||
Serial Number | 2025022101 | ||
Refresh | 3600 | ||
Retry | 900 | ||
Expire | 3600000 | ||
Minimum TTL | 3600 | ||
TXT | 600 | ||
A | 45.223.62.151 | 525 | |
NS | 3600 | ||
NS | 3600 |
Whois Lookup ▼
Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on June 16, 2017 and will expire on April 26, 2025 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on June 30, 2024.- Domain Created:
- 2017-06-16
- Domain Updated:
- 2024-06-30
- Domain Age:
- 7 years 10 months 10 days
- WhoIs:
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'. ] Domain Information: a. [Domain Name] E-SHISHOBAKO.NE.JP d. [Network Service Name] e-SHISHOBAKO service l. [Organization Type] Network Service m. [Administrative Contact] HH36012JP n. [Technical Contact] KW419JP p. [Name Server] ns1.dns.ne.jp p. [Name Server] ns2.dns.ne.jp s. [Signing Key] [State] Connected (2025/06/30) [Registered Date] 2017/06/16 [Connected Date] 2018/05/02 [Last Update] 2024/07/01 01:07:37 (JST)