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 of America (the)

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

;; QUESTION SECTION:
;207.19.53.145.			IN	A

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

;; Query time: 50 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 21:54:39 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 145.53.19.207.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 207.19.53.145.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.131 attackbots
$f2bV_matches
2019-12-01 07:00:21
176.115.93.53 attackbotsspam
fake user registration/login attempts
2019-12-01 07:24:39
184.75.211.148 attackbots
(From branco.doug@hotmail.com) Trying to find effective advertising that isn't full of crap? I apologize for sending you this message on your contact form but actually that was the whole point. We can send your promotional copy to websites via their contact forms just like you're receiving this ad right now. You can specify targets by keyword or just execute mass blasts to sites in the country of your choice. So let's say you want to send a message to all the web developers in the USA, we'll grab websites for just those and post your ad message to them. As long as you're advertising some kind of offer that's relevant to that business category then you'll receive an awesome result! 

Send an email to sarah1916eva@gmail.com to find out how we do this
2019-12-01 07:25:44
51.15.46.184 attack
Dec  1 00:03:07 localhost sshd\[30679\]: Invalid user rpm from 51.15.46.184 port 37528
Dec  1 00:03:07 localhost sshd\[30679\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.46.184
Dec  1 00:03:09 localhost sshd\[30679\]: Failed password for invalid user rpm from 51.15.46.184 port 37528 ssh2
2019-12-01 07:12:58
37.187.54.67 attackspam
Fail2Ban - SSH Bruteforce Attempt
2019-12-01 07:20:47
129.158.71.3 attackbotsspam
$f2bV_matches
2019-12-01 07:18:39
111.231.59.116 attackbotsspam
$f2bV_matches
2019-12-01 07:08:16
46.38.144.32 attackspambots
Nov 30 23:38:52 relay postfix/smtpd\[21833\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 30 23:39:19 relay postfix/smtpd\[22822\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 30 23:40:03 relay postfix/smtpd\[11831\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 30 23:40:35 relay postfix/smtpd\[10327\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 30 23:41:20 relay postfix/smtpd\[11831\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-01 07:17:30
101.109.250.73 attack
Port 1433 Scan
2019-12-01 07:20:04
112.85.42.171 attack
Dec  1 00:26:07 MK-Soft-Root1 sshd[17616]: Failed password for root from 112.85.42.171 port 49941 ssh2
Dec  1 00:26:10 MK-Soft-Root1 sshd[17616]: Failed password for root from 112.85.42.171 port 49941 ssh2
...
2019-12-01 07:30:21
82.49.115.58 attackbots
Nov 30 17:32:02 eola sshd[15852]: Invalid user pi from 82.49.115.58 port 52784
Nov 30 17:32:02 eola sshd[15853]: Invalid user pi from 82.49.115.58 port 52786
Nov 30 17:32:03 eola sshd[15852]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.49.115.58 
Nov 30 17:32:03 eola sshd[15853]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.49.115.58 
Nov 30 17:32:04 eola sshd[15852]: Failed password for invalid user pi from 82.49.115.58 port 52784 ssh2
Nov 30 17:32:04 eola sshd[15853]: Failed password for invalid user pi from 82.49.115.58 port 52786 ssh2
Nov 30 17:32:05 eola sshd[15853]: Connection closed by 82.49.115.58 port 52786 [preauth]
Nov 30 17:32:05 eola sshd[15852]: Connection closed by 82.49.115.58 port 52784 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=82.49.115.58
2019-12-01 07:19:05
78.129.146.110 attack
TCP Port Scanning
2019-12-01 07:12:42
219.150.116.52 attack
Fail2Ban - SMTP Bruteforce Attempt
2019-12-01 06:59:36
51.75.246.176 attack
Triggered by Fail2Ban at Vostok web server
2019-12-01 07:04:14
189.7.17.61 attackbotsspam
Invalid user www from 189.7.17.61 port 58461
2019-12-01 07:29:33

Recently Reported IPs

145.166.6.240 55.44.206.118 212.178.195.153 46.228.50.133
123.134.233.41 124.179.47.129 21.149.143.233 234.57.167.84
148.33.111.244 63.254.99.131 180.107.230.126 44.174.229.187
255.174.42.31 186.191.48.223 232.118.83.134 61.6.87.155
185.227.76.185 157.217.98.85 49.85.9.143 231.251.45.88