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

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

;; QUESTION SECTION:
;104.138.189.45.			IN	A

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

;; Query time: 113 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 19:18:17 CST 2022
;; MSG SIZE  rcvd: 107
Host info
45.189.138.104.in-addr.arpa domain name pointer cpe-104-138-189-45.triad.res.rr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.189.138.104.in-addr.arpa	name = cpe-104-138-189-45.triad.res.rr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.217.23.161 attack
20/2/7@09:05:23: FAIL: Alarm-Network address from=190.217.23.161
20/2/7@09:05:23: FAIL: Alarm-Network address from=190.217.23.161
...
2020-02-08 01:34:03
222.186.42.136 attack
Feb  7 18:40:49 debian64 sshd\[1610\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136  user=root
Feb  7 18:40:51 debian64 sshd\[1610\]: Failed password for root from 222.186.42.136 port 39414 ssh2
Feb  7 18:40:55 debian64 sshd\[1610\]: Failed password for root from 222.186.42.136 port 39414 ssh2
...
2020-02-08 01:42:02
35.176.217.117 attackbots
Lines containing failures of 35.176.217.117
Feb  4 21:53:20 shared04 sshd[32613]: Did not receive identification string from 35.176.217.117 port 56908
Feb  4 21:53:20 shared04 sshd[32614]: Did not receive identification string from 35.176.217.117 port 46464
Feb  4 21:56:13 shared04 sshd[1041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.176.217.117  user=r.r
Feb  4 21:56:14 shared04 sshd[1044]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.176.217.117  user=r.r
Feb  4 21:56:15 shared04 sshd[1044]: Failed password for r.r from 35.176.217.117 port 40812 ssh2
Feb  4 21:56:15 shared04 sshd[1044]: Received disconnect from 35.176.217.117 port 40812:11: Normal Shutdown, Thank you for playing [preauth]
Feb  4 21:56:15 shared04 sshd[1044]: Disconnected from authenticating user r.r 35.176.217.117 port 40812 [preauth]
Feb  4 21:56:16 shared04 sshd[1041]: Failed password for r.r from 35.176.2........
------------------------------
2020-02-08 01:16:16
87.103.245.190 attack
Sending SPAM email
2020-02-08 01:21:35
115.144.141.2 attack
Port probing on unauthorized port 5555
2020-02-08 00:59:54
36.85.222.105 attackspambots
Feb  7 15:06:12 mail sshd\[9624\]: Failed password for root from 36.85.222.105 port 14930 ssh2
Feb  7 15:06:17 mail sshd\[9629\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.85.222.105  user=root
Feb  7 15:06:19 mail sshd\[9629\]: Failed password for root from 36.85.222.105 port 59884 ssh2
...
2020-02-08 01:03:29
199.195.254.80 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-08 01:02:21
5.200.48.150 attack
Feb  7 17:45:06 debian-2gb-nbg1-2 kernel: \[3353148.087224\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=5.200.48.150 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=27551 PROTO=TCP SPT=41473 DPT=3687 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-08 01:20:00
139.219.15.116 attackspambots
ssh failed login
2020-02-08 01:02:37
106.12.186.74 attackbots
Feb  7 15:02:31 silence02 sshd[4056]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.186.74
Feb  7 15:02:34 silence02 sshd[4056]: Failed password for invalid user mjp from 106.12.186.74 port 44210 ssh2
Feb  7 15:06:19 silence02 sshd[4341]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.186.74
2020-02-08 01:40:47
98.109.26.245 attackspambots
Feb  7 12:07:55 vps46666688 sshd[7243]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=98.109.26.245
Feb  7 12:07:58 vps46666688 sshd[7243]: Failed password for invalid user ytx from 98.109.26.245 port 55030 ssh2
...
2020-02-08 01:23:18
217.182.70.150 attackspambots
fraudulent SSH attempt
2020-02-08 01:02:53
209.17.97.114 attack
The IP has triggered Cloudflare WAF. CF-Ray: 560f92574fafd50d | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: MIA. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2020-02-08 01:24:28
176.113.115.101 attack
VPN Brute force
2020-02-08 01:21:19
222.186.175.148 attackspam
Feb  7 18:05:05 MK-Soft-VM5 sshd[3469]: Failed password for root from 222.186.175.148 port 5982 ssh2
Feb  7 18:05:09 MK-Soft-VM5 sshd[3469]: Failed password for root from 222.186.175.148 port 5982 ssh2
...
2020-02-08 01:23:50

Recently Reported IPs

104.137.70.163 104.137.9.62 101.109.150.7 104.138.249.108
104.138.249.44 104.139.101.20 104.139.101.31 104.138.247.195
104.138.215.158 104.139.102.190 104.139.102.135 104.139.102.182
209.189.141.87 104.139.104.129 104.139.104.185 101.109.150.83
104.139.102.78 104.139.104.61 104.139.104.217 104.139.105.234