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

Region: unknown

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

;; QUESTION SECTION:
;104.4.155.49.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 12:32:05 CST 2022
;; MSG SIZE  rcvd: 105
Host info
49.155.4.104.in-addr.arpa domain name pointer 104-4-155-49.lightspeed.mmphtn.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
49.155.4.104.in-addr.arpa	name = 104-4-155-49.lightspeed.mmphtn.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.250.186.78 attackbotsspam
Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found
2020-02-08 03:58:00
89.163.225.107 attackbots
89.163.225.107 was recorded 15 times by 9 hosts attempting to connect to the following ports: 33848,41794,6881. Incident counter (4h, 24h, all-time): 15, 63, 291
2020-02-08 04:07:31
61.167.99.163 attackspam
$f2bV_matches
2020-02-08 03:40:40
139.162.105.13 attack
ssh brute force
2020-02-08 04:19:24
201.190.176.19 attackbotsspam
Feb  7 19:44:22 163-172-32-151 sshd[6986]: Invalid user ftpuser from 201.190.176.19 port 40572
...
2020-02-08 03:51:24
3.104.156.83 attackbots
Feb  7 15:51:39 legacy sshd[26729]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.104.156.83
Feb  7 15:51:41 legacy sshd[26729]: Failed password for invalid user bhy from 3.104.156.83 port 40094 ssh2
Feb  7 16:01:26 legacy sshd[27255]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=3.104.156.83
...
2020-02-08 04:12:29
125.213.150.7 attackspam
Feb  7 19:47:47 srv-ubuntu-dev3 sshd[104981]: Invalid user oaj from 125.213.150.7
Feb  7 19:47:47 srv-ubuntu-dev3 sshd[104981]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.213.150.7
Feb  7 19:47:47 srv-ubuntu-dev3 sshd[104981]: Invalid user oaj from 125.213.150.7
Feb  7 19:47:49 srv-ubuntu-dev3 sshd[104981]: Failed password for invalid user oaj from 125.213.150.7 port 44050 ssh2
Feb  7 19:51:42 srv-ubuntu-dev3 sshd[105348]: Invalid user unw from 125.213.150.7
Feb  7 19:51:42 srv-ubuntu-dev3 sshd[105348]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.213.150.7
Feb  7 19:51:42 srv-ubuntu-dev3 sshd[105348]: Invalid user unw from 125.213.150.7
Feb  7 19:51:44 srv-ubuntu-dev3 sshd[105348]: Failed password for invalid user unw from 125.213.150.7 port 45354 ssh2
Feb  7 19:55:37 srv-ubuntu-dev3 sshd[105634]: Invalid user dki from 125.213.150.7
...
2020-02-08 04:03:40
113.22.186.168 attackbots
Unauthorized connection attempt from IP address 113.22.186.168 on Port 445(SMB)
2020-02-08 03:56:39
211.72.15.95 attackspambots
Unauthorized connection attempt from IP address 211.72.15.95 on Port 445(SMB)
2020-02-08 03:43:28
212.64.21.78 attackbots
2020-02-07T20:12:21.580507  sshd[20574]: Invalid user iy from 212.64.21.78 port 18153
2020-02-07T20:12:21.593484  sshd[20574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.21.78
2020-02-07T20:12:21.580507  sshd[20574]: Invalid user iy from 212.64.21.78 port 18153
2020-02-07T20:12:23.387254  sshd[20574]: Failed password for invalid user iy from 212.64.21.78 port 18153 ssh2
2020-02-07T20:27:31.054881  sshd[21205]: Invalid user duo from 212.64.21.78 port 60216
...
2020-02-08 04:01:32
153.37.214.220 attackspam
Feb  7 18:09:21 ourumov-web sshd\[32091\]: Invalid user yfu from 153.37.214.220 port 40430
Feb  7 18:09:21 ourumov-web sshd\[32091\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=153.37.214.220
Feb  7 18:09:23 ourumov-web sshd\[32091\]: Failed password for invalid user yfu from 153.37.214.220 port 40430 ssh2
...
2020-02-08 04:03:12
103.84.96.139 attack
Port 22 Scan, PTR: None
2020-02-08 04:17:30
183.83.236.251 attack
Feb  7 12:36:28 db01 sshd[9976]: Did not receive identification string from 183.83.236.251
Feb  7 12:36:29 db01 sshd[9977]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.83.236.251] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  7 12:36:30 db01 sshd[9977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.83.236.251  user=r.r
Feb  7 12:36:31 db01 sshd[9977]: Failed password for r.r from 183.83.236.251 port 12044 ssh2
Feb  7 12:36:31 db01 sshd[9977]: Connection closed by 183.83.236.251 [preauth]
Feb  7 12:36:33 db01 sshd[9989]: reveeclipse mapping checking getaddrinfo for broadband.actcorp.in [183.83.236.251] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  7 12:36:33 db01 sshd[9989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.83.236.251  user=r.r
Feb  7 12:36:35 db01 sshd[9989]: Failed password for r.r from 183.83.236.251 port 11828 ssh2
Feb  7 12:37:03 db01 sshd[9989]:........
-------------------------------
2020-02-08 03:54:18
15.185.35.140 attack
Brute force VPN server
2020-02-08 03:42:07
162.14.12.0 attackspam
ICMP MH Probe, Scan /Distributed -
2020-02-08 04:10:27

Recently Reported IPs

106.245.156.91 92.63.197.101 91.219.164.204 185.162.174.3
92.205.12.121 177.52.24.4 99.8.30.116 81.218.182.127
172.81.212.47 200.31.122.174 182.122.249.105 110.42.192.246
20.203.187.23 139.59.248.243 91.102.64.157 24.228.120.158
47.46.167.10 120.7.88.221 39.148.174.66 124.106.19.110