Royalknighttokyo.com valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title Royal Knight Tokyo
Description 毎日使う理美容用品にあなたのこだわりは反映されてますか?Royal Knight Tokyoでは、レトロな見た目に最新の機能を詰め込んだ美容室向けのドライヤーや、柄の入ったカットクロスやネックラバーなど他では中々手に入らない個性が引き立つサロンアイテムなどの販売を通じてあなたらしさを追求するサロンづくりに貢献致します。
Keywords royal knight tokyo,ビンテージスタイル barber,デニムエプロン  理容室,理容室 美容室 用品,美容室用,カットクロス,かわいいカットクロス
Server Information
WebSite royalknighttokyo favicon www.royalknighttokyo.com
Host IP 183.181.97.10
Location Osaka, Ōsaka, Japan
Related Websites
Site Rank
More to Explore
russkikhonline.ru
sadsj.jp
salesianer.si
se01.biz
seoulhc.com
sigma08.ru
sozosha.ac.jp
teancup.com
thefrenchieco.qa
torrentnori18.com
idealpecasdf.com.br
ief.mg.gov.br
Royalknighttokyo.com Valuation
US$46,197
Last updated: Feb 10, 2022

Royalknighttokyo.com has global traffic rank of 1,112,626. Royalknighttokyo.com has an estimated worth of US$ 46,197, based on its estimated Ads revenue. Royalknighttokyo.com receives approximately 2,812 unique visitors each day. Its web server is located in Osaka, Ōsaka, Japan, with IP address 183.181.97.10. According to SiteAdvisor, royalknighttokyo.com is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$46,197
Daily Ads Revenue US$25
Monthly Ads Revenue US$759
Yearly Ads Revenue US$9,239
Daily Unique Visitors 2,812
Note: All traffic and earnings values are estimates.
Traffic Ranks
Global Rank 1,112,626
Delta (90 Days) 0
Most Popular In Country N/A
Country Rank N/A
DNS Records
Host Type TTL Data
royalknighttokyo.com A 3600 IP: 183.181.97.10
royalknighttokyo.com MX 3600 Priority: 0
Target: royalknighttokyo.com.
royalknighttokyo.com NS 3600 Target: ns1.xserver.jp.
royalknighttokyo.com NS 3600 Target: ns2.xserver.jp.
royalknighttokyo.com NS 3600 Target: ns4.xserver.jp.
royalknighttokyo.com NS 3600 Target: ns3.xserver.jp.
royalknighttokyo.com NS 3600 Target: ns5.xserver.jp.
royalknighttokyo.com TXT 3600 TXT: v=spf1 +ip4:183.181.97.10 +a:sv7009.xserver.jp +mx ~all
royalknighttokyo.com SOA 3600 MNAME: ns1.xserver.jp.
RNAME: root.xserver.jp.
Serial: 0
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum TTL: 3600
HTTP Headers
HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 10 Feb 2022 13:28:09 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 237
Connection: keep-alive
Location: https://royalknighttokyo.com/

HTTP/2 200 
server: nginx
date: Thu, 10 Feb 2022 13:28:10 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
link: <https://royalknighttokyo.com/wp-json/>; rel="https://api.w.org/"

Royalknighttokyo.com Whois Information
   Domain Name: ROYALKNIGHTTOKYO.COM
   Registry Domain ID: 2243749615_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.star-domain.jp
   Registrar URL: http://www.netowl.jp
   Updated Date: 2021-03-02T05:06:52Z
   Creation Date: 2018-03-26T05:29:33Z
   Registry Expiry Date: 2022-03-26T05:29:33Z
   Registrar: Netowl, Inc.
   Registrar IANA ID: 1557
   Registrar Abuse Contact Email: registrar-abuse@netowl.jp
   Registrar Abuse Contact Phone: +81.752568553
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS1.XSERVER.JP
   Name Server: NS2.XSERVER.JP
   Name Server: NS3.XSERVER.JP
   Name Server: NS4.XSERVER.JP
   Name Server: NS5.XSERVER.JP
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

Domain Name: royalknighttokyo.com
Registry Domain ID: 
Registrar WHOIS Server: whois.star-domain.jp
Registrar URL: www.star-domain.jp
Updated Date: 2021-03-02T05:06:52Z
Creation Date: 2018-03-26T05:29:33Z
Registrar Registration Expiration Date: 2022-03-26T05:29:33Z
Registrar: Netowl, Inc.
Registrar IANA ID: 1557
Registrar Abuse Contact Email: registrar-abuse@netowl.jp
Registrar Abuse Contact Phone: +81.662928811
Domain Status:  - https://www.icann.org/epp#
Registry Registrant ID: 
Registrant Name: RYONOSUKE SATO
Registrant Organization: Kabushikigaishaaruke
Registrant Street: Senju3-67-4
Registrant Street: SG bill 1F
Registrant City: Adachi Ku
Registrant State/Province: Tokyo To
Registrant Postal Code: 120-0034
Registrant Country: JP
Registrant Phone: +81.9047147183
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: lambretta185@hotmail.com
Registry Admin ID: 
Admin Name: RYONOSUKE SATO
Admin Organization: Kabushikigaishaaruke
Admin Street: Senju3-67-4
Admin Street: SG bill 1F
Admin City: Adachi Ku
Admin State/Province: Tokyo To
Admin Postal Code: 120-0034
Admin Country: JP
Admin Phone: +81.9047147183
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: lambretta185@hotmail.com
Registry Tech ID: 
Tech Name: Xserver Xserver Inc.
Tech Organization: Xserver Inc.
Tech Street: GRAND FRONT OSAKA TOWER A 32F
Tech Street: 4-20 Ofukacho, Kita-ku
Tech City: Osaka
Tech State/Province: Osaka
Tech Postal Code: 5300011
Tech Country: JP
Tech Phone: +81.662928811
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: info@xserver.co.jp
Name Server: ns1.xserver.jp
Name Server: ns2.xserver.jp
Name Server: ns3.xserver.jp
Name Server: ns4.xserver.jp
Name Server: ns5.xserver.jp
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/

The WHOIS service (the "Service") offered by Netowl, Inc. ("Netowl") and the
access to the records provided via the Service are for informational purposes
only. Netowl makes this information available to you "as is" and does not
guarantee its accuracy. By submitting a WHOIS query, you agree that you will use
this data only for lawful purposes and that, under no circumstances will you use
this data: (1) to allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via direct mail, electronic
mail, or by telephone; (2) in contravention of any applicable data and privacy
protection acts; or (3) to enable high volume, automated, electronic processes
that apply to Netowl (or its systems). Compilation, repackaging, dissemination,
or other use of the WHOIS database in its entirety, or of a substantial portion
thereof, is strictly prohibited.

-status-codes-2014-06-16-en.