raku-care.jp Raku-care.jp

   
楽々ケア

Domain Summary

What is the traffic rank for Raku-care.jp?

• Raku-care.jp ranks #1,427,869 globally on HypeStat.

What percent of global Internet users visit Raku-care.jp?

• 1.2E-5% of global Internet users visit Raku-care.jp

How many people visit Raku-care.jp each day?

• Raku-care.jp receives approximately 590 visitors and 2,534 page impressions per day.

Which countries does Raku-care.jp receive most of its visitors from?

• Raku-care.jp is mostly visited by people located in Japan.

How much Raku-care.jp can earn?

• Raku-care.jp should earn about $0.91/day from advertising revenue.

What is Raku-care.jp estimated value?

• Estimated value of Raku-care.jp is $945.39.

What IP addresses does Raku-care.jp resolve to?

• Raku-care.jp resolves to the IP addresses 165.76.149.82.

Where are Raku-care.jp servers located in?

• Raku-care.jp has servers located in Shukugawara, Kanagawa, 214-0021, Japan.

raku-care.jp Profile

Title:楽々ケア
Category:Health / Other Health
Edit Site Info

What technologies does raku-care.jp use?

These are the technologies used at raku-care.jp. raku-care.jp has a total of 2 technologies installed in 2 different categories.
Web Servers
Apache HTTP Server Apache HTTP Server
Analytics
Google Analytics Google Analytics

raku-care.jp Traffic Analysis

Raku-care.jp is ranked #1,427,869 in the world. This website is viewed by an estimated 590 visitors daily, generating a total of 2.5K pageviews. This equates to about 17.9K monthly visitors.
Daily Visitors590
Monthly Visits17.9K
Pages per Visit4.29
Visit duration08:24
Bounce Rate32.81%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
590
Monthly Visits:
17,877
Pages per Visit:
4.29
Daily Pageviews:
2,534
Avg. visit duration:
08:24
Bounce rate:
32.81%
Global Reach:
1.2E-5%
Monthly Visits (SimilarWeb):
17,538
HypeRank:
1,427,869
SEMrush Rank:
29,279,856
SimilarWeb Rank:
1,427,869
*All traffic values are estimates only.

Total Visits Last 3 Months

22K
DEC
17.9K
JAN
17.9K
FEB

Visitors by country

Country
Users%
 
Japan 100.00%

Which sites are competitors to raku-care.jp?

Websites similar to raku-care.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.
Last update was 1 day ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with raku-care.jp in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
194

  ▼

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.
SemRushSemRush
Domain:
  raku-care.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  29,279,856
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1
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
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $0.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $27.3 and annual gross revenue of approximately $332.2. Based on these figures, the site's net worth is estimated at around $0.9K.

How much would raku-care.jp make?

Daily Revenue:
$0.91
Monthly Revenue:
$27.30
Yearly Revenue:
$332.15
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 2,534$0.91

Loss of money due to Adblock?

Daily Revenue Loss:
$0.03
Monthly Revenue Loss:
$0.82
Yearly Revenue Loss:
$9.99
Daily Pageviews Blocked:
76
Monthly Pageviews Blocked:
2,281
Yearly Pageviews Blocked:
27,747

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 76$0.03

How much is raku-care.jp worth?

Website Value:
$0.9K

Ad Experience Report ▼

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

Mobile summary

Root domain:
raku-care.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:
raku-care.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:
raku-care.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 raku-care.jp hosted? ▼

Raku-care.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
165.76.149.82
ASN:
AS17676 
ISP:
Softbank BB Corp. 
Server Location:
Shukugawara
Kanagawa, 14
214-0021
Japan, JP
 

Other sites hosted on 165.76.149.82

There are no other sites hosted on this IP

How fast does raku-care.jp load? ▼

The average loading time of raku-care.jp is 736 ms. The Desktop speed index is 97 and mobile speed index is 88.
Average Load Time:
736 ms

Page Speed (Google PageSpeed Insights) - Desktop

97
0-49 50-89 90-100 i

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 100% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 100% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)546ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 11% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 11% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)698ms 91% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 91% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)35ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)702ms 94% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 94% 1% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 1% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an AVERAGE 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 93% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)858ms 71% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 71% 24% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 24% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)36ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.2s 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 1% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 1% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

Lab Data

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
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
Max Potential First Input Delay 50 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
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
Time to Interactive 1.2 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
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
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
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
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 Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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

Page Speed (Google PageSpeed Insights) - Mobile

88
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE 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 100% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 100% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)285ms 82% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 88% 8% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 8% 3% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)672ms 91% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)360ms 97% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 0% 99% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 99% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)687ms 94% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 0%

Origin Data

All pages served from this origin have an AVERAGE 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 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)755ms 75% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 75% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.3s 89% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 89% 7% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 7% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)312ms 50% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 50% 48% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 48% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.3s 95% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 95% 4% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 4% 0% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 0%

Lab Data

Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Max Potential First Input Delay 50 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint 3.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
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
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
Time to Interactive 3.6 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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
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
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does raku-care.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 raku-care.jp are reduced by %.
raku-care.jp does not use compression.
Original size: 4.74 KB
Compressed size: n/a
File reduced by: (%)

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.
Status:
  SAFE

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. raku-care.jp supports HTTPS.
 raku-care.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.raku-care.jp
Organization:
Location:
Issuer: JPRS Domain Validation Authority - G4
Valid from: Feb 5 00:32:29 2025 GMT
Valid until: Feb 28 14:59:59 2026 GMT
Authority:
Keysize: 2048 Bits
Common Name: JPRS Domain Validation Authority - G4
Organization: "Japan Registry Services Co., Ltd."
Location: JP
Issuer:
Valid from: Jul 22 10:40:53 2020 GMT
Valid until: May 29 05:00:39 2029 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.
 raku-care.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: Mon, 31 Mar 2025 11:06:23 GMT
Server: Apache
Cache-Control: no-cache
X-XSS-Protection: 1; mode=block
X-Request-Id: ba1e78ab-2684-4a58-9494-c61950dc97c0
X-Runtime: 0.001472
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
X-Powered-By: Phusion Passenger 6.0.1
Location: https://raku-care.jp/login.html
Status: 302 Found
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked

HTTP/1.1 200 OK
Date: Mon, 31 Mar 2025 11:06:24 GMT
Server: Apache
Last-Modified: Tue, 18 Mar 2025 10:38:16 GMT
ETag: "12f8-6309b809b7600"
Accept-Ranges: bytes
Content-Length: 4856
Content-Type: text/html; charset=UTF-8

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
MX mx18.gmoserver.jp 3600
SOA 86400
Mname 01.dnsv.jp
Rname hostmaster.dnsv.jp
Serial Number 1742197917
Refresh 3600
Retry 900
Expire 604800
Minimum TTL 300
A 165.76.149.82 3538
NS 03.dnsv.jp 86338
NS 04.dnsv.jp 86338
NS 01.dnsv.jp 86338
NS 02.dnsv.jp 86338

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 March 2, 2018 and will expire on March 31, 2025 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on March 17, 2025.
Domain Created:
2018-03-02
Domain Expires:
2025-03-31
Domain Updated:
2025-03-17
Domain Age:
7 years 1 months
Domain Owner:
(Not displayed by registrant's request)
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:
[Domain Name]                   RAKU-CARE.JP

[Registrant]                    (Not displayed by registrant's request)
                                For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)

[Name Server]                   03.dnsv.jp
[Name Server]                   02.dnsv.jp
[Name Server]                   01.dnsv.jp
[Name Server]                   04.dnsv.jp
[Signing Key]                   

[Created on]                    2018/03/02
[Expires on]                    2025/03/31
[Status]                        Active
[Last Updated]                  2025/03/17 16:52:01 (JST)

Contact Information:
[Name]                          Whois Privacy Protection Service by onamae.com
[Email]                         email
[Web Page]                       
[Postal code]                   150-8512
[Postal Address]                Shibuya-ku
                                26-1 Sakuragaoka-cho
                                Cerulean Tower 11F
[Phone]                         +81.354562560
[Fax]