Home | Blog | Browse Database | Contact Us | Download | Forums | History | Need Help? | Privacy Policy
Find  
IMPORTANT: Read the classification explanations BEFORE loading sites listed in this database (classification explanations).

IMPORTANT: If you are using programs such as HostsMan, uBlock, ABP or are using the files for blocking on devices such as routers, please consider switching to the dedicated classification files.
Query: internet-turbo.com
I've so far recorded 41 historical records for internet-turbo.com:
# Hostname IP PTR Date Recorded
1 internet-turbo.com 64.111.214.157 care5.isprime.com 30/12/2012 04:17:58
2 internet-turbo.com 50.112.112.223 ec2-50-112-112-223.us-west-2.compute.amazonaws.com 12/12/2013 14:51:27
3 internet-turbo.com 54.214.247.254 IP Resolution failed 27/09/2014 09:35:11
4 internet-turbo.com 54.214.33.160 IP Resolution failed 22/10/2014 09:53:10
5 internet-turbo.com 50.112.127.124 IP Resolution failed 29/03/2015 07:39:03
6 internet-turbo.com 54.244.112.122 IP Resolution failed 26/08/2015 20:03:49
7 internet-turbo.com 54.245.120.101 IP Resolution failed 09/10/2015 01:59:59
8 internet-turbo.com 54.214.45.218 IP Resolution failed 21/04/2016 06:01:49
9 internet-turbo.com 54.244.230.54 ec2-54-244-230-54.us-west-2.compute.amazonaws.com 21/04/2016 06:01:50
10 internet-turbo.com 54.214.45.218 IP Resolution failed 26/04/2016 13:21:56
11 internet-turbo.com 54.244.230.54 IP Resolution failed 26/04/2016 13:21:56
12 internet-turbo.com 54.214.248.174 IP Resolution failed 01/07/2016 23:22:28
13 internet-turbo.com 54.245.252.139 ec2-54-245-252-139.us-west-2.compute.amazonaws.com 01/07/2016 23:22:29
14 internet-turbo.com 54.214.43.144 IP Resolution failed 04/08/2016 19:11:33
15 internet-turbo.com 54.245.92.68 IP Resolution failed 04/08/2016 19:11:33
16 internet-turbo.com 54.214.43.144 IP Resolution failed 05/08/2016 19:38:24
17 internet-turbo.com 54.245.92.68 IP Resolution failed 05/08/2016 19:38:24
18 internet-turbo.com 54.244.119.190 IP Resolution failed 31/08/2016 19:53:34
19 internet-turbo.com 54.245.236.39 ec2-54-245-236-39.us-west-2.compute.amazonaws.com 31/08/2016 19:53:35
20 internet-turbo.com 54.244.119.186 IP Resolution failed 11/10/2016 11:28:41
21 internet-turbo.com 54.214.45.96 IP Resolution failed 11/10/2016 11:28:41
22 internet-turbo.com 54.244.119.186 IP Resolution failed 08/12/2016 03:29:01
23 internet-turbo.com 54.244.119.186 IP Resolution failed 14/02/2017 02:35:39
24 internet-turbo.com 54.244.119.186 IP Resolution failed 21/04/2017 19:54:24
25 internet-turbo.com 54.244.112.220 ec2-54-244-112-220.us-west-2.compute.amazonaws.com 21/04/2017 19:55:24
26 internet-turbo.com 54.244.112.220 IP Resolution failed 01/05/2017 22:38:18
27 internet-turbo.com 54.244.249.189 ec2-54-244-249-189.us-west-2.compute.amazonaws.com 01/05/2017 22:38:55
28 internet-turbo.com 54.244.112.220 IP Resolution failed 03/05/2017 06:14:20
29 internet-turbo.com 207.244.67.218 Resolution failed 09/12/2017 00:53:44
30 internet-turbo.com 185.141.60.5 IP Resolution failed 27/04/2018 21:23:16
31 internet-turbo.com 64.32.8.67 IP Resolution failed 29/06/2018 11:28:07
32 internet-turbo.com 162.210.195.123 IP Resolution failed 15/06/2019 01:12:41
33 internet-turbo.com 207.244.67.216 IP Resolution failed 18/07/2019 20:45:42
34 internet-turbo.com 162.210.195.122 IP Resolution failed 19/07/2019 15:48:27
35 internet-turbo.com 5.79.68.108 IP Resolution failed 19/07/2019 21:22:33
36 internet-turbo.com 207.244.67.215 IP Resolution failed 22/07/2019 19:31:08
37 internet-turbo.com 5.79.68.110 IP Resolution failed 24/07/2019 08:44:47
38 internet-turbo.com 64.32.8.68 IP Resolution failed 25/07/2019 01:15:03
39 internet-turbo.com 5.79.68.107 IP Resolution failed 26/07/2019 06:06:40
40 internet-turbo.com 207.244.67.138 IP Resolution failed 27/07/2019 04:43:09
41 internet-turbo.com 208.91.197.46 IP Resolution failed 04/08/2019 18:33:31

Note: These results do not necessarily include data from the main hpHosts database as the history is used to log the hostname, IP and IPPTR for all hosts and IP's queried using this service.

Technical stuff:

Database query took me [ 0 ] seconds