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: Santa Cruz

Region: California

Country: United States

Internet Service Provider: AT&T

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 <<>> 104.182.244.202
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46280
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.182.244.202.		IN	A

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 16:31:53 CST 2025
;; MSG SIZE  rcvd: 108
Host info
202.244.182.104.in-addr.arpa domain name pointer 104-182-244-202.lightspeed.stlsmo.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
202.244.182.104.in-addr.arpa	name = 104-182-244-202.lightspeed.stlsmo.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.16.199.56 attackspam
Wordpress Admin Login attack
2019-08-17 11:35:03
190.72.110.195 attack
Unauthorized connection attempt from IP address 190.72.110.195 on Port 445(SMB)
2019-08-17 11:32:48
122.2.112.101 attackbots
2019-08-17T03:15:04.251640abusebot-5.cloudsearch.cf sshd\[19267\]: Invalid user Access from 122.2.112.101 port 52630
2019-08-17 11:27:02
178.128.57.96 attackspam
Invalid user sx from 178.128.57.96 port 37218
2019-08-17 11:49:17
220.135.48.40 attack
Fail2Ban Ban Triggered
2019-08-17 11:36:59
139.198.5.79 attackbots
Aug 16 20:31:08 TORMINT sshd\[25612\]: Invalid user admin from 139.198.5.79
Aug 16 20:31:08 TORMINT sshd\[25612\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79
Aug 16 20:31:10 TORMINT sshd\[25612\]: Failed password for invalid user admin from 139.198.5.79 port 58968 ssh2
...
2019-08-17 11:29:48
189.50.3.234 attackspam
Unauthorized connection attempt from IP address 189.50.3.234 on Port 445(SMB)
2019-08-17 11:13:56
189.164.172.36 attackspam
Aug 16 21:06:28 XXX sshd[25201]: Invalid user gz from 189.164.172.36 port 53802
2019-08-17 11:29:32
142.93.174.47 attack
Automated report - ssh fail2ban:
Aug 17 03:08:14 wrong password, user=bao, port=36180, ssh2
Aug 17 03:41:23 authentication failure 
Aug 17 03:41:25 wrong password, user=password, port=49154, ssh2
2019-08-17 11:38:09
51.79.107.66 attackspam
Aug 16 21:01:15 XXX sshd[24888]: Invalid user backup from 51.79.107.66 port 49884
2019-08-17 11:35:38
125.92.223.150 attackspam
Aug 17 04:53:02 datentool sshd[24064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.92.223.150  user=r.r
Aug 17 04:53:05 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:07 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:09 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:10 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:12 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:15 datentool sshd[24064]: Failed password for r.r from 125.92.223.150 port 56318 ssh2
Aug 17 04:53:15 datentool sshd[24064]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.92.223.150  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=125.92.223.150
2019-08-17 11:07:07
104.248.71.7 attackbots
Aug 17 05:42:32 vps691689 sshd[4293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
Aug 17 05:42:35 vps691689 sshd[4293]: Failed password for invalid user mysql from 104.248.71.7 port 55976 ssh2
Aug 17 05:46:44 vps691689 sshd[4454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.71.7
...
2019-08-17 11:50:50
103.129.221.7 attackspam
Aug 17 04:33:05 site2 sshd\[47526\]: Invalid user vivo from 103.129.221.7Aug 17 04:33:08 site2 sshd\[47526\]: Failed password for invalid user vivo from 103.129.221.7 port 38868 ssh2Aug 17 04:38:06 site2 sshd\[47615\]: Failed password for root from 103.129.221.7 port 56086 ssh2Aug 17 04:42:30 site2 sshd\[48137\]: Invalid user gnbc from 103.129.221.7Aug 17 04:42:32 site2 sshd\[48137\]: Failed password for invalid user gnbc from 103.129.221.7 port 47492 ssh2
...
2019-08-17 11:15:07
104.248.211.180 attackbots
Aug 17 03:24:47 MK-Soft-VM3 sshd\[29937\]: Invalid user support from 104.248.211.180 port 40322
Aug 17 03:24:47 MK-Soft-VM3 sshd\[29937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.211.180
Aug 17 03:24:49 MK-Soft-VM3 sshd\[29937\]: Failed password for invalid user support from 104.248.211.180 port 40322 ssh2
...
2019-08-17 11:41:33
200.233.138.102 attackspam
Unauthorized connection attempt from IP address 200.233.138.102 on Port 445(SMB)
2019-08-17 11:28:53

Recently Reported IPs

72.98.84.79 55.223.228.97 236.94.115.57 53.149.233.80
150.129.46.121 89.171.149.181 90.31.155.118 144.185.50.85
242.203.243.147 63.221.29.39 25.70.129.28 123.239.235.24
67.65.173.126 14.69.186.136 59.196.3.203 116.176.84.170
148.46.16.123 219.95.80.162 41.109.209.27 40.67.239.191