Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: San Diego

Region: California

Country: United States

Internet Service Provider: CARInet Inc.

Hostname: unknown

Organization: CariNet, Inc.

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
botsattackproxy
Botnet DB Scanner
2024-04-27 11:24:15
attackbotsspam
ET CINS Active Threat Intelligence Poor Reputation IP group 65 - port: 5060 proto: sip cat: Misc Attackbytes: 271
2020-10-14 05:06:43
attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 62 - port: 5006 proto: udp cat: Misc Attackbytes: 83
2020-10-08 03:22:01
attack
 TCP (SYN) 71.6.167.142:20832 -> port 995, len 44
2020-10-07 19:36:34
attack
 TCP (SYN) 71.6.167.142:20041 -> port 22, len 44
2020-09-04 00:39:49
attackspambots
[Tue Aug 18 06:17:35 2020] - DDoS Attack From IP: 71.6.167.142 Port: 24858
2020-09-03 08:14:32
attackspam
Hit honeypot r.
2020-08-27 20:53:54
attackspam
Fail2Ban Ban Triggered
2020-08-16 01:25:23
attackbots
Port scanning [2 denied]
2020-08-12 18:39:35
attack
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 7218
2020-08-07 20:54:56
attackspambots
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 11300
2020-07-21 20:56:57
attack
 UDP 71.6.167.142:14016 -> port 5353, len 74
2020-07-18 14:56:17
attack
 TCP (SYN) 71.6.167.142:27153 -> port 992, len 44
2020-07-07 01:08:13
attackspam
 TCP (SYN) 71.6.167.142:31802 -> port 993, len 44
2020-06-26 04:21:24
attack
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 25
2020-06-25 18:19:00
attack
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 9200
2020-06-06 08:40:18
attackbots
06/04/2020-13:14:40.824354 71.6.167.142 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 71
2020-06-05 01:37:46
attack
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 6697
2020-06-04 12:56:27
attack
 TCP (SYN) 71.6.167.142:23320 -> port 55443, len 44
2020-06-01 00:53:38
attackspambots
 UDP 71.6.167.142:14187 -> port 623, len 51
2020-05-16 02:58:41
attackspambots
ET CINS Active Threat Intelligence Poor Reputation IP group 60 - port: 37 proto: TCP cat: Misc Attack
2020-05-11 08:03:58
attack
05/06/2020-15:08:00.190447 71.6.167.142 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 71
2020-05-07 03:36:34
attack
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 8008
2020-04-26 00:18:26
attackspambots
scans once in preceeding hours on the ports (in chronological order) 5672 resulting in total of 13 scans from 71.6.128.0/17 block.
2020-04-24 21:25:23
attackspam
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 4444
2020-04-17 15:37:35
attackspambots
Port 3001 scan denied
2020-04-17 07:09:10
attackspam
Port scan: Attack repeated for 24 hours
2020-04-11 06:31:03
attackbotsspam
[portscan] tcp/143 [IMAP]
*(RWIN=31689)(03311119)
2020-03-31 16:43:55
attack
Automatic report - Banned IP Access
2020-03-29 03:24:36
attackspambots
Unauthorized connection attempt detected from IP address 71.6.167.142 to port 84
2020-03-28 20:14:38
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 71.6.167.142
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15478
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;71.6.167.142.			IN	A

;; AUTHORITY SECTION:
.			3600	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2019033000 1800 900 604800 86400

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Sat Mar 30 16:39:24 +08 2019
;; MSG SIZE  rcvd: 116

Host info
142.167.6.71.in-addr.arpa domain name pointer census9.shodan.io.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
142.167.6.71.in-addr.arpa	name = census9.shodan.io.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
167.172.157.75 attack
2020-03-22T18:45:48.081806randservbullet-proofcloud-66.localdomain sshd[32333]: Invalid user ln from 167.172.157.75 port 58360
2020-03-22T18:45:48.086589randservbullet-proofcloud-66.localdomain sshd[32333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.157.75
2020-03-22T18:45:48.081806randservbullet-proofcloud-66.localdomain sshd[32333]: Invalid user ln from 167.172.157.75 port 58360
2020-03-22T18:45:49.991507randservbullet-proofcloud-66.localdomain sshd[32333]: Failed password for invalid user ln from 167.172.157.75 port 58360 ssh2
...
2020-03-23 04:41:55
50.23.2.38 attackspam
Unauthorized connection attempt detected from IP address 50.23.2.38 to port 445
2020-03-23 04:37:23
73.185.241.75 attackbotsspam
Telnet/23 MH Probe, Scan, BF, Hack -
2020-03-23 04:58:38
89.122.190.209 attackspam
Honeypot attack, port: 5555, PTR: PTR record not found
2020-03-23 04:46:59
185.9.226.28 attackbotsspam
(sshd) Failed SSH login from 185.9.226.28 (DE/Germany/cable-185-9-226-28.cust.telecolumbus.net): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 22 21:33:01 amsweb01 sshd[24149]: Invalid user nc from 185.9.226.28 port 53888
Mar 22 21:33:03 amsweb01 sshd[24149]: Failed password for invalid user nc from 185.9.226.28 port 53888 ssh2
Mar 22 21:38:41 amsweb01 sshd[25011]: User admin from 185.9.226.28 not allowed because not listed in AllowUsers
Mar 22 21:38:41 amsweb01 sshd[25011]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.9.226.28  user=admin
Mar 22 21:38:43 amsweb01 sshd[25011]: Failed password for invalid user admin from 185.9.226.28 port 46254 ssh2
2020-03-23 04:39:28
134.209.178.109 attack
Mar 22 12:42:04 firewall sshd[3858]: Invalid user brett from 134.209.178.109
Mar 22 12:42:06 firewall sshd[3858]: Failed password for invalid user brett from 134.209.178.109 port 54904 ssh2
Mar 22 12:42:32 firewall sshd[3897]: Invalid user brett from 134.209.178.109
...
2020-03-23 05:05:36
186.103.196.86 attackspambots
Honeypot attack, port: 445, PTR: 186-103-196-86.static.tie.cl.
2020-03-23 04:49:17
218.250.126.197 attackbotsspam
Honeypot attack, port: 5555, PTR: n218250126197.netvigator.com.
2020-03-23 04:26:29
218.1.18.78 attackspambots
2020-03-22T14:23:54.084583linuxbox-skyline sshd[86037]: Invalid user luka from 218.1.18.78 port 34144
...
2020-03-23 05:07:51
138.97.93.194 attackbots
Mar 22 05:56:39 mockhub sshd[23022]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.97.93.194
Mar 22 05:56:41 mockhub sshd[23022]: Failed password for invalid user admin from 138.97.93.194 port 59806 ssh2
...
2020-03-23 05:02:04
185.175.93.18 attack
03/22/2020-15:36:54.358669 185.175.93.18 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-03-23 04:43:49
111.231.63.208 attackbotsspam
SSH Brute-Force Attack
2020-03-23 04:51:22
119.28.47.248 attack
SSH/22 MH Probe, BF, Hack -
2020-03-23 05:04:11
117.173.67.119 attack
Mar 22 20:23:09 serwer sshd\[30386\]: Invalid user zzy from 117.173.67.119 port 3007
Mar 22 20:23:09 serwer sshd\[30386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.173.67.119
Mar 22 20:23:12 serwer sshd\[30386\]: Failed password for invalid user zzy from 117.173.67.119 port 3007 ssh2
...
2020-03-23 04:36:06
124.123.34.179 attackbotsspam
Honeypot attack, port: 81, PTR: broadband.actcorp.in.
2020-03-23 04:44:27

Recently Reported IPs

202.155.149.162 23.229.29.237 213.32.69.98 177.67.48.198
121.49.99.9 99.149.251.77 186.116.196.212 180.64.71.114
109.255.228.154 107.170.202.91 174.22.165.106 114.35.191.170
64.76.49.68 152.249.226.38 106.13.89.192 162.243.165.39
83.208.68.198 76.25.119.25 181.39.1.37 200.206.92.194