Browse Database |
Contact Us |
IMPORTANT: Read the classification explanations BEFORE
loading sites listed in this database (classification explanations
Sites resolving to 184.108.40.206 were found in our database
32392 220.127.116.11/16 OPENTRANSFER-ECOMMERCE - Ecommerce Corporation
# Query terms are ambiguous. The query is assumed to be:
# "n 18.104.22.168"
# Use "?" to get help.
# The following results may also be obtained via:
NetRange: 22.214.171.124 - 126.96.36.199
NetType: Direct Allocation
OrgName: Ecommerce Corporation
Address: 1774 Dividend Dr
OrgTechName: eCommerce NOC
OrgNOCName: eCommerce NOC
OrgAbuseName: eCommerce Inc ABUSE Dept
RNOCName: eCommerce NOC
RTechName: eCommerce NOC
RAbuseName: eCommerce Inc ABUSE Dept
# available at: https://www.arin.net/whois_tou.html
This data has been pulled from the hpHosts cache
Hint: Hover over each classification for additional information.
If you were referred here by a comment such as the following, on SiteAdvisor, please disregard it;
"According to http://www.hosts-file.net/ if you access this domain you risk to unwillingly download and install malicious software (virus, trojans, spyware, etc) that may damage your computer."
I'm sick to death of users such as Alexis Kauffman et al, that think it fun to mass-post comments such as the above.
These comments are NOT endorsed by me, nor are they in mosts cases, accurate (see the classification assigned to each domain).
Domain or netblock resolution query/problems?, please see;
Be advised, the matches shown in brackets next to the domain and IP (e.g. (10)), are fuzzy matches for the domain name (*domain.com), and /24 matches for the IP address.
The Computer Emergency Response Team for [ US ] can be reached at: soc AT us-cert.gov
I've so far identified [ 1 ] records for this IP
WARNING: The IP PTR [ rev.opentransfer.com.188.8.131.52.in-addr.arpa. ] does not resolve. This is considered very bad practice and contravines the RFC Standards. Most legit ISP's will have their PTR's resolve to an IP.
Database query took me [ 2 ] seconds
IP PTR query took me [ 0 ] seconds