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

Internet Service Provider: KKON Technologies Ltd

Hostname: unknown

Organization: unknown

Usage Type: Fixed Line ISP

Comments:
Type Details Datetime
attackbotsspam
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/102.67.2.145/ 
 NG - 1H : (10)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : NG 
 NAME ASN : ASN36920 
 
 IP : 102.67.2.145 
 
 CIDR : 102.67.2.0/24 
 
 PREFIX COUNT : 31 
 
 UNIQUE IP COUNT : 7936 
 
 
 WYKRYTE ATAKI Z ASN36920 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 2 
 
 DateTime : 2019-10-01 05:52:56 
 
 INFO : SERVER - Looking for resource vulnerabilities Detected and Blocked by ADMIN  - data recovery
2019-10-01 14:00:52
Comments on same subnet:
IP Type Details Datetime
102.67.29.216 spamattack
IP used in attempts to phish M365 user details and send out phising emails
also used in unauthorised access to M365 services.
2021-09-09 22:04:33
102.67.2.82 attack
Automatic report - Port Scan Attack
2019-07-14 04:17:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 102.67.2.145
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45939
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;102.67.2.145.			IN	A

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

;; Query time: 84 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 01 14:00:47 CST 2019
;; MSG SIZE  rcvd: 116
Host info
Host 145.2.67.102.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 145.2.67.102.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
43.240.21.31 attack
1578458874 - 01/08/2020 05:47:54 Host: 43.240.21.31/43.240.21.31 Port: 445 TCP Blocked
2020-01-08 18:32:56
172.247.123.99 attackbots
Unauthorized connection attempt detected from IP address 172.247.123.99 to port 2220 [J]
2020-01-08 18:47:01
139.162.122.110 attackbots
Jan  8 10:17:22 work-partkepr sshd\[15800\]: Invalid user  from 139.162.122.110 port 38630
Jan  8 10:17:22 work-partkepr sshd\[15800\]: Failed none for invalid user  from 139.162.122.110 port 38630 ssh2
...
2020-01-08 18:36:55
5.135.146.51 attackspam
ssh brute force
2020-01-08 18:56:08
86.149.220.118 attackbotsspam
Unauthorized connection attempt detected from IP address 86.149.220.118 to port 23 [J]
2020-01-08 18:49:14
101.108.191.131 attackspambots
20/1/7@23:48:00: FAIL: Alarm-Network address from=101.108.191.131
...
2020-01-08 18:32:37
192.241.213.168 attack
Jan  8 06:20:22 powerpi2 sshd[1713]: Invalid user lijy from 192.241.213.168 port 49696
Jan  8 06:20:24 powerpi2 sshd[1713]: Failed password for invalid user lijy from 192.241.213.168 port 49696 ssh2
Jan  8 06:23:16 powerpi2 sshd[1835]: Invalid user aaron from 192.241.213.168 port 49670
...
2020-01-08 18:43:47
121.229.0.154 attackbotsspam
Unauthorized connection attempt detected from IP address 121.229.0.154 to port 2220 [J]
2020-01-08 19:03:58
195.216.207.98 attackbots
Jan  7 20:12:35 auw2 sshd\[11728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.216.207.98  user=www-data
Jan  7 20:12:38 auw2 sshd\[11728\]: Failed password for www-data from 195.216.207.98 port 36172 ssh2
Jan  7 20:15:12 auw2 sshd\[11938\]: Invalid user miguel from 195.216.207.98
Jan  7 20:15:12 auw2 sshd\[11938\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.216.207.98
Jan  7 20:15:14 auw2 sshd\[11938\]: Failed password for invalid user miguel from 195.216.207.98 port 43328 ssh2
2020-01-08 18:46:08
139.255.108.114 attackbots
Unauthorized connection attempt from IP address 139.255.108.114 on Port 445(SMB)
2020-01-08 18:57:43
51.15.6.36 attackspambots
Jan  8 05:45:22 srv01 sshd[20523]: Invalid user bkf from 51.15.6.36 port 44648
Jan  8 05:45:22 srv01 sshd[20523]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.15.6.36
Jan  8 05:45:22 srv01 sshd[20523]: Invalid user bkf from 51.15.6.36 port 44648
Jan  8 05:45:25 srv01 sshd[20523]: Failed password for invalid user bkf from 51.15.6.36 port 44648 ssh2
Jan  8 05:47:22 srv01 sshd[20640]: Invalid user px from 51.15.6.36 port 35610
...
2020-01-08 18:55:23
118.97.232.146 attackspambots
Unauthorized connection attempt from IP address 118.97.232.146 on Port 445(SMB)
2020-01-08 19:00:47
117.31.76.86 attackspam
2020-01-07 22:46:53 dovecot_login authenticator failed for (nezbv) [117.31.76.86]:58890 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liutingting@lerctr.org)
2020-01-07 22:47:01 dovecot_login authenticator failed for (tdbrb) [117.31.76.86]:58890 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liutingting@lerctr.org)
2020-01-07 22:47:13 dovecot_login authenticator failed for (jdycy) [117.31.76.86]:58890 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=liutingting@lerctr.org)
...
2020-01-08 19:04:31
124.6.158.62 attackbotsspam
01/08/2020-05:47:18.904810 124.6.158.62 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-08 18:59:25
52.230.66.101 attackbots
Unauthorized connection attempt detected from IP address 52.230.66.101 to port 2220 [J]
2020-01-08 18:52:02

Recently Reported IPs

38.186.7.223 108.218.128.127 188.113.219.156 40.55.159.26
167.187.82.216 196.228.241.10 58.72.43.143 180.241.134.98
70.248.24.216 50.238.34.167 179.215.244.5 103.137.160.41
95.162.8.189 62.109.10.71 88.130.66.240 104.203.161.112
194.10.109.148 191.43.30.123 98.33.66.226 217.85.152.222