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

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

;; QUESTION SECTION:
;104.144.135.245.		IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 13:23:45 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 245.135.144.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 245.135.144.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
144.217.80.190 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-26 02:17:50
47.101.223.16 attackspambots
11/25/2019-10:18:53.973799 47.101.223.16 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-26 01:49:23
218.92.0.135 attackspambots
Nov 25 08:01:49 hanapaa sshd\[9014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.135  user=root
Nov 25 08:01:51 hanapaa sshd\[9014\]: Failed password for root from 218.92.0.135 port 17726 ssh2
Nov 25 08:01:54 hanapaa sshd\[9014\]: Failed password for root from 218.92.0.135 port 17726 ssh2
Nov 25 08:02:08 hanapaa sshd\[9050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.135  user=root
Nov 25 08:02:09 hanapaa sshd\[9050\]: Failed password for root from 218.92.0.135 port 2590 ssh2
2019-11-26 02:06:30
222.186.180.8 attackbots
SSH Brute Force, server-1 sshd[21403]: Failed password for root from 222.186.180.8 port 17314 ssh2
2019-11-26 02:02:59
124.156.54.68 attackbotsspam
" "
2019-11-26 02:20:17
115.236.35.107 attackbotsspam
Nov 25 19:09:50 eventyay sshd[29528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.236.35.107
Nov 25 19:09:52 eventyay sshd[29528]: Failed password for invalid user lauper from 115.236.35.107 port 60622 ssh2
Nov 25 19:14:21 eventyay sshd[29630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.236.35.107
...
2019-11-26 02:22:22
84.241.44.211 attackspam
Automatic report - Port Scan Attack
2019-11-26 02:03:26
106.12.180.210 attackspam
Nov 25 11:15:44 linuxvps sshd\[52050\]: Invalid user foy from 106.12.180.210
Nov 25 11:15:44 linuxvps sshd\[52050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.180.210
Nov 25 11:15:46 linuxvps sshd\[52050\]: Failed password for invalid user foy from 106.12.180.210 port 45168 ssh2
Nov 25 11:24:22 linuxvps sshd\[57326\]: Invalid user jaimy from 106.12.180.210
Nov 25 11:24:22 linuxvps sshd\[57326\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.180.210
2019-11-26 01:40:57
185.213.169.138 attackspam
Fail2Ban Ban Triggered
2019-11-26 02:16:21
189.145.121.44 attackbots
SMB Server BruteForce Attack
2019-11-26 02:18:33
31.209.62.168 attack
Nov 25 17:45:54 flomail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=, method=PLAIN, rip=31.209.62.168, lip=10.140.194.78, TLS, session=
Nov 25 17:46:08 flomail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 8 secs): user=, method=PLAIN, rip=31.209.62.168, lip=10.140.194.78, TLS: Disconnected, session=
Nov 25 17:50:11 flomail dovecot: imap-login: Disconnected (auth failed, 1 attempts in 5 secs): user=, method=PLAIN, rip=31.209.62.168, lip=10.140.194.78, TLS: Disconnected, session=
2019-11-26 02:04:58
167.99.83.237 attackspam
Nov 25 16:56:53 localhost sshd\[87986\]: Invalid user glossary from 167.99.83.237 port 55604
Nov 25 16:56:53 localhost sshd\[87986\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.83.237
Nov 25 16:56:54 localhost sshd\[87986\]: Failed password for invalid user glossary from 167.99.83.237 port 55604 ssh2
Nov 25 17:03:02 localhost sshd\[88208\]: Invalid user manohar from 167.99.83.237 port 34486
Nov 25 17:03:02 localhost sshd\[88208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.83.237
...
2019-11-26 02:18:50
113.28.150.73 attackspambots
Nov 25 18:37:30 server sshd\[25827\]: Invalid user nike from 113.28.150.73
Nov 25 18:37:30 server sshd\[25827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.28.150.73 
Nov 25 18:37:33 server sshd\[25827\]: Failed password for invalid user nike from 113.28.150.73 port 62913 ssh2
Nov 25 18:41:00 server sshd\[26824\]: Invalid user www-data from 113.28.150.73
Nov 25 18:41:00 server sshd\[26824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.28.150.73 
...
2019-11-26 02:01:18
117.208.3.23 attackspam
Automatic report - Port Scan Attack
2019-11-26 01:45:27
27.66.194.103 attack
19/11/25@09:36:16: FAIL: Alarm-SSH address from=27.66.194.103
...
2019-11-26 02:15:47

Recently Reported IPs

103.225.64.27 31.198.109.177 104.144.135.39 104.144.135.40
104.144.135.43 104.144.135.52 75.121.142.103 104.144.135.61
104.144.135.81 103.23.19.122 104.144.135.89 103.23.22.248
104.144.135.96 27.114.192.9 104.144.135.98 103.230.234.80
103.230.159.65 103.230.232.81 103.230.235.63 103.230.234.27