Browse Database |
Contact Us |
IMPORTANT: Read the classification explanations BEFORE
loading sites listed in this database (classification explanations
Sites resolving to 22.214.171.124 were NOT found in our database
23352 126.96.36.199/21 SERVERCENTRAL - Server Central Network
# Query terms are ambiguous. The query is assumed to be:
# "n 188.8.131.52"
# Use "?" to get help.
# The following results may also be obtained via:
NetRange: 184.108.40.206 - 220.127.116.11
NetType: Direct Allocation
OrgName: Server Central Network
Address: 209 W. Jackson Blvd.
Address: Suite 700
OrgAbuseName: Abuse Department
OrgNOCName: Network Operations
OrgTechName: Network Operations
RAbuseName: Abuse Department
RTechName: Network Operations
RNOCName: Network Operations
# 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;
It should also be noted that lack of a listing in this database, does NOT mean it is "clean" or "safe" (and certainly does not mean it is approved by hpHosts!), it could simply be that I'm not yet aware of it, or haven't yet analyzed it. If you suspect a domain is malicious, and it's not yet listed in the database, please consider dropping by the forums and letting me know.
The Computer Emergency Response Team for [ US ] can be reached at: soc AT us-cert.gov
I've so far identified [ 2 ] records for this IP
WARNING: The IP PTR associated with this record, does not resolve back to it's original IP address. This is very bad practice.
PTR IP: 18.104.22.168
Database query took me [ 2 ] seconds
IP PTR query took me [ 0 ] seconds