Rongyiju.net was registered on name.com, inc. on 06 September 2015.
The site is almost absent on social networks.
The site receives 1,470 visitors every month, which put its worth at around $ approximately.
The website has a good alexa rank of 2,574,629.
The site is hosted in United States by Internet Assigned Numbers Authority.
The webmasters of the website can be contacted at .
The domain for the website was purchased through name.com, inc. on 06 September 2015 (2 years ago) and will expire in 1 year 2 months.
Alexa Rank 2,574,629
Visitors 40 daily
Approx. Monthly Revenue $12
Text lanuage None
Family safe text Yes
The report was last updated on May 05, 2016.
If its not up to date, please click the update button for the same.
Social Network Presence
Following statistics represent rongyiju.net activity on various social networks.
Find out about the infrastructure of rongyiju.net, e.g. how the website works, what hardware and software it uses etc.
12025 Waterfront Drive, Los Angeles, CA, United States
Email hosted by
Web Hosting Provider
Internet Assigned Numbers Authority
Site Generating Software
SSL Certificate Issuer
Domain Registered by
These records can help to identify the owners of rongyiju.net. You can contact the admins through the email present in these records.
06 September 2015
08 September 2015
06 September 2016
Domain Name: RONGYIJU.NET
Registrar: NAME.COM, INC.
Sponsoring Registrar IANA ID: 625
Whois Server: whois.name.com
Name Server: F1G1NS1.DNSPOD.NET
Name Server: F1G1NS2.DNSPOD.NET
Status: clientTransferProhibited Updated Date: 08-sep-2015
Creation Date: 06-sep-2015
Expiration Date: 06-sep-2016
Domain Name: RONGYIJU.NET
Registry Domain ID: 1957850688_DOMAIN_NET-VRSN
Registrar WHOIS Server: whois.name.com
Updated Date: 2015-09-08T05:01:03Z
Creation Date: 2015-09-06T07:20:45Z
Registrar Registration Expiration Date: 2016-09-06T07:20:45Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Domain Status: clientTransferProhibited
Registry Registrant ID:
Registrant Name: y sz
Registrant Organization: xiaozhu
Registrant Street: beijing haidian
Registrant City: beijing
Registrant State/Province: beijing
Registrant Postal Code: 100080
Registrant Country: CN
Registrant Phone: +86.15311463330
Registry Admin ID:
Admin Name: y sz
Admin Organization: xiaozhu
Admin Street: beijing haidian
Admin City: beijing
Admin State/Province: beijing
Admin Postal Code: 100080
Admin Country: CN
Admin Phone: +86.15311463330
Registry Tech ID:
Tech Name: y sz
Tech Organization: xiaozhu
Tech Street: beijing haidian
Tech City: beijing
Tech State/Province: beijing
Tech Postal Code: 100080
Tech Country: CN
Tech Phone: +86.15311463330
Name Server: f1g1ns1.dnspod.net
Name Server: f1g1ns2.dnspod.net
DNSSEC: Unsigned Delegation
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: +1.1 7203101849
URL of the ICANN WHOIS Data Problem Reporting System:
The Data in the Name.com, Inc. WHOIS database is provided by Name.com, Inc. for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. Name.com, Inc. 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 to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to Name.com, Inc. (or its systems). Name.com, Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Find out all the details about the IP address used by the website, including the nameservers and IP location.
No. of IP Addresses 1
IP Location 12025 Waterfront Drive, Los Angeles, CA, United States
Following are the links associated with the homepage of the website.
Following information represents the extra metadata sent by the website servers on requesting the homepage of the website.
No HTTP Headers were found for rongyiju.net, it could be because the site was offline when the report was created!