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:
IP Type Details Datetime
1.0.145.1 attack
20/7/8@23:54:35: FAIL: Alarm-Network address from=1.0.145.1
...
2020-07-09 15:52:56
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 1.0.145.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47256
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;1.0.145.80.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 03:55:23 CST 2022
;; MSG SIZE  rcvd: 103
Host info
80.145.0.1.in-addr.arpa domain name pointer node-3f4.pool-1-0.dynamic.totinternet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
80.145.0.1.in-addr.arpa	name = node-3f4.pool-1-0.dynamic.totinternet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
138.68.30.68 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-07 01:08:00
46.101.101.66 attackbots
Nov  6 09:47:15 server sshd\[29805\]: Invalid user applmgr from 46.101.101.66
Nov  6 09:47:15 server sshd\[29805\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.101.66 
Nov  6 09:47:17 server sshd\[29805\]: Failed password for invalid user applmgr from 46.101.101.66 port 34990 ssh2
Nov  6 19:43:30 server sshd\[23144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.101.66  user=root
Nov  6 19:43:31 server sshd\[23144\]: Failed password for root from 46.101.101.66 port 40764 ssh2
...
2019-11-07 01:21:33
114.4.193.227 attack
2019-11-06T16:20:53.586523abusebot-7.cloudsearch.cf sshd\[21649\]: Invalid user pz from 114.4.193.227 port 33578
2019-11-07 01:22:45
123.178.150.230 attackspam
Fail2Ban - FTP Abuse Attempt
2019-11-07 01:25:39
191.83.102.105 attackspambots
Telnet Server BruteForce Attack
2019-11-07 01:08:29
209.97.168.118 attackspambots
2019-11-06T15:46:48.187796lon01.zurich-datacenter.net sshd\[26190\]: Invalid user wxmsyy97945 from 209.97.168.118 port 48416
2019-11-06T15:46:48.193903lon01.zurich-datacenter.net sshd\[26190\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.168.118
2019-11-06T15:46:50.316943lon01.zurich-datacenter.net sshd\[26190\]: Failed password for invalid user wxmsyy97945 from 209.97.168.118 port 48416 ssh2
2019-11-06T15:51:32.869659lon01.zurich-datacenter.net sshd\[26320\]: Invalid user GuiZhouDX from 209.97.168.118 port 59720
2019-11-06T15:51:32.876404lon01.zurich-datacenter.net sshd\[26320\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.97.168.118
...
2019-11-07 01:29:13
210.217.24.246 attackspambots
Nov  6 17:09:12 vpn01 sshd[542]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.217.24.246
Nov  6 17:09:15 vpn01 sshd[542]: Failed password for invalid user emplazamiento from 210.217.24.246 port 49196 ssh2
...
2019-11-07 01:22:05
168.232.67.201 attack
Nov  6 17:43:28 MK-Soft-VM6 sshd[13198]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.67.201 
Nov  6 17:43:30 MK-Soft-VM6 sshd[13198]: Failed password for invalid user kuang from 168.232.67.201 port 54180 ssh2
...
2019-11-07 01:17:49
200.164.217.212 attack
2019-11-06T14:39:58.363310abusebot-5.cloudsearch.cf sshd\[8479\]: Invalid user test from 200.164.217.212 port 48169
2019-11-07 00:45:18
222.186.173.154 attackbotsspam
Nov  6 12:14:37 debian sshd\[18168\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.154  user=root
Nov  6 12:14:39 debian sshd\[18168\]: Failed password for root from 222.186.173.154 port 22734 ssh2
Nov  6 12:14:43 debian sshd\[18168\]: Failed password for root from 222.186.173.154 port 22734 ssh2
...
2019-11-07 01:20:52
122.51.49.91 attack
Nov  6 06:40:30 web1 sshd\[23620\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.49.91  user=root
Nov  6 06:40:32 web1 sshd\[23620\]: Failed password for root from 122.51.49.91 port 47742 ssh2
Nov  6 06:44:31 web1 sshd\[23963\]: Invalid user plesk from 122.51.49.91
Nov  6 06:44:31 web1 sshd\[23963\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.49.91
Nov  6 06:44:33 web1 sshd\[23963\]: Failed password for invalid user plesk from 122.51.49.91 port 50088 ssh2
2019-11-07 00:51:46
37.146.144.194 attackbotsspam
firewall-block, port(s): 445/tcp
2019-11-07 00:43:45
45.136.109.95 attackspambots
11/06/2019-11:39:42.032804 45.136.109.95 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 40
2019-11-07 01:19:49
2a00:c760:83:def:aced:ffff:b921:3610 attackbots
ENG,WP GET /wp-login.php
GET /wp-login.php
2019-11-07 01:20:13
222.92.244.42 attackspam
port scan and connect, tcp 22 (ssh)
2019-11-07 01:16:20

Recently Reported IPs

1.0.145.72 1.0.145.90 105.112.30.227 1.0.145.92
1.0.146.116 1.0.146.121 1.0.146.124 1.0.146.129
1.0.146.137 1.0.146.147 1.0.146.15 223.182.37.123
1.0.148.186 231.32.146.141 1.0.148.193 1.0.148.198
1.0.148.216 1.0.148.221 1.0.148.223 1.0.148.235