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: Salem

Region: Oregon

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 75.148.84.138
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15803
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 10 09:23:06 CST 2020
;; MSG SIZE  rcvd: 117
Host info
138.84.148.75.in-addr.arpa domain name pointer 75-148-84-138-Oregon.hfc.comcastbusiness.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
138.84.148.75.in-addr.arpa	name = 75-148-84-138-Oregon.hfc.comcastbusiness.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.230.165.16 attackspam
Bruteforce detected by fail2ban
2020-04-06 08:59:00
193.142.59.231 attackspam
Microsoft-Windows-Security-Auditing
2020-04-06 09:08:16
193.248.33.189 attack
Apr  6 02:14:12 vmd26974 sshd[7672]: Failed password for root from 193.248.33.189 port 41608 ssh2
...
2020-04-06 08:56:01
185.200.118.89 attackspam
185.200.118.89 was recorded 11 times by 9 hosts attempting to connect to the following ports: 1080,1194. Incident counter (4h, 24h, all-time): 11, 12, 490
2020-04-06 08:43:47
192.241.202.169 attackbotsspam
2020-04-06T02:14:25.974001ns386461 sshd\[21083\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.202.169  user=root
2020-04-06T02:14:28.022551ns386461 sshd\[21083\]: Failed password for root from 192.241.202.169 port 40552 ssh2
2020-04-06T02:19:59.586579ns386461 sshd\[26586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.202.169  user=root
2020-04-06T02:20:01.154378ns386461 sshd\[26586\]: Failed password for root from 192.241.202.169 port 36054 ssh2
2020-04-06T02:23:12.686317ns386461 sshd\[29563\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.202.169  user=root
...
2020-04-06 09:05:30
222.186.31.135 attackbots
Apr  6 02:57:46 host5 sshd[32254]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.135  user=root
Apr  6 02:57:47 host5 sshd[32254]: Failed password for root from 222.186.31.135 port 28688 ssh2
...
2020-04-06 09:00:59
111.231.119.141 attack
Apr  5 22:34:49 *** sshd[19560]: User root from 111.231.119.141 not allowed because not listed in AllowUsers
2020-04-06 09:07:20
159.89.114.40 attack
$f2bV_matches
2020-04-06 08:50:17
1.179.185.50 attackspam
Apr  5 18:11:02 server1 sshd\[16480\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50  user=root
Apr  5 18:11:04 server1 sshd\[16480\]: Failed password for root from 1.179.185.50 port 55480 ssh2
Apr  5 18:15:08 server1 sshd\[17628\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50  user=root
Apr  5 18:15:10 server1 sshd\[17628\]: Failed password for root from 1.179.185.50 port 37754 ssh2
Apr  5 18:19:23 server1 sshd\[18838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.179.185.50  user=root
...
2020-04-06 09:08:45
111.68.46.68 attack
(sshd) Failed SSH login from 111.68.46.68 (PH/Philippines/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  6 03:12:07 s1 sshd[11196]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68  user=root
Apr  6 03:12:09 s1 sshd[11196]: Failed password for root from 111.68.46.68 port 48797 ssh2
Apr  6 03:25:04 s1 sshd[11486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68  user=root
Apr  6 03:25:06 s1 sshd[11486]: Failed password for root from 111.68.46.68 port 49754 ssh2
Apr  6 03:27:11 s1 sshd[11620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68  user=root
2020-04-06 08:46:22
45.126.74.195 attackspam
SSH brutforce
2020-04-06 08:41:35
222.186.173.180 attackspam
2020-04-06T00:38:28.857822shield sshd\[4552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.180  user=root
2020-04-06T00:38:30.340957shield sshd\[4552\]: Failed password for root from 222.186.173.180 port 54954 ssh2
2020-04-06T00:38:33.488864shield sshd\[4552\]: Failed password for root from 222.186.173.180 port 54954 ssh2
2020-04-06T00:38:36.717018shield sshd\[4552\]: Failed password for root from 222.186.173.180 port 54954 ssh2
2020-04-06T00:38:40.356368shield sshd\[4552\]: Failed password for root from 222.186.173.180 port 54954 ssh2
2020-04-06 08:42:41
185.204.3.36 attackspambots
SSH Brute-Force reported by Fail2Ban
2020-04-06 08:39:57
66.70.130.152 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-06 08:32:44
180.76.151.189 attackbotsspam
Unauthorized SSH login attempts
2020-04-06 09:05:55

Recently Reported IPs

89.135.147.161 156.170.33.145 58.188.91.158 111.168.100.66
86.214.43.105 179.157.2.121 124.192.127.149 95.173.93.77
91.237.205.104 42.93.127.234 12.234.223.248 83.5.43.146
52.44.48.67 194.126.64.228 78.5.196.222 100.212.35.172
35.239.166.231 114.162.11.199 200.132.152.245 82.60.98.0