必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): unknown

省份(region): Free State

国家(country): South Africa

运营商(isp): MTN

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
% This is the AfriNIC Whois server.
% The AFRINIC whois database is subject to  the following terms of Use. See https://afrinic.net/whois/terms

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '41.122.0.0 - 41.122.127.255'

% No abuse contact registered for 41.122.0.0 - 41.122.127.255

inetnum:        41.122.0.0 - 41.122.127.255
netname:        MTNSA-41-122-0-0-17
descr:          Mobile Broadband Internet - Randburg
country:        ZA
admin-c:        MBIP-AFRINIC
tech-c:         MBIP-AFRINIC
status:         ASSIGNED PA
remarks:        report abuse to abuse@mtnbusiness.co.za
mnt-by:         MTNBUSINESS-MNT
source:         AFRINIC # Filtered
parent:         41.112.0.0 - 41.127.255.255

role:           MTN Business IP Maintainer
address:        MTN Business
address:        Heron Place
address:        c/o Century Boulevard and Heron Crescent
address:        Stand no 6465
address:        Century City
address:        Cape Town
address:        South Africa
admin-c:        AT32-AFRINIC
tech-c:         AT32-AFRINIC
nic-hdl:        MBIP-AFRINIC
mnt-by:         MTNBUSINESS-MNT
source:         AFRINIC # Filtered
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 41.122.72.202
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41813
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;41.122.72.202.			IN	A

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

;; Query time: 29 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Nov 10 10:03:50 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 202.72.122.41.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 202.72.122.41.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
119.27.164.206 attack
2019-10-31T16:40:25.614063abusebot-8.cloudsearch.cf sshd\[30547\]: Invalid user stock from 119.27.164.206 port 54548
2019-11-01 03:47:53
185.176.27.254 attackspam
10/31/2019-15:36:06.234885 185.176.27.254 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-01 04:06:27
14.116.194.20 attackbotsspam
2019-10-31 09:05:08,648 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:29:52,447 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:45:02,240 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 10:04:03,921 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 10:22:55,481 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:05:08,648 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:29:52,447 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:45:02,240 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 10:04:03,921 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 10:22:55,481 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 09:05:08,648 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.116.194.20
2019-10-31 0
2019-11-01 03:54:39
209.208.111.71 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/209.208.111.71/ 
 
 US - 1H : (246)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : US 
 NAME ASN : ASN6364 
 
 IP : 209.208.111.71 
 
 CIDR : 209.208.64.0/18 
 
 PREFIX COUNT : 55 
 
 UNIQUE IP COUNT : 60928 
 
 
 ATTACKS DETECTED ASN6364 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-31 12:57:53 
 
 INFO : Server 301 - Looking for resource vulnerabilities Detected and Blocked by ADMIN  - data recovery
2019-11-01 03:51:55
104.42.158.134 attackbotsspam
ssh failed login
2019-11-01 04:14:17
58.222.11.82 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2019-11-01 03:45:11
80.255.130.197 attackspam
Oct 31 14:52:46 DAAP sshd[14944]: Invalid user smmsp from 80.255.130.197 port 44902
Oct 31 14:52:46 DAAP sshd[14944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.255.130.197
Oct 31 14:52:46 DAAP sshd[14944]: Invalid user smmsp from 80.255.130.197 port 44902
Oct 31 14:52:48 DAAP sshd[14944]: Failed password for invalid user smmsp from 80.255.130.197 port 44902 ssh2
Oct 31 14:57:19 DAAP sshd[14969]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.255.130.197  user=root
Oct 31 14:57:21 DAAP sshd[14969]: Failed password for root from 80.255.130.197 port 35790 ssh2
...
2019-11-01 04:04:55
176.113.74.126 attack
PostgreSQL port 5432
2019-11-01 03:42:44
106.75.17.245 attackbotsspam
$f2bV_matches
2019-11-01 04:15:45
222.98.37.25 attack
(sshd) Failed SSH login from 222.98.37.25 (KR/South Korea/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 31 20:06:34 server2 sshd[17711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.98.37.25  user=root
Oct 31 20:06:35 server2 sshd[17711]: Failed password for root from 222.98.37.25 port 48147 ssh2
Oct 31 20:23:07 server2 sshd[18063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.98.37.25  user=root
Oct 31 20:23:09 server2 sshd[18063]: Failed password for root from 222.98.37.25 port 54651 ssh2
Oct 31 20:27:10 server2 sshd[18169]: Invalid user user from 222.98.37.25 port 53012
2019-11-01 03:43:29
119.29.132.143 attack
Oct 31 01:47:47 hostnameproxy sshd[1283]: Invalid user lan from 119.29.132.143 port 42468
Oct 31 01:47:47 hostnameproxy sshd[1283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.132.143
Oct 31 01:47:49 hostnameproxy sshd[1283]: Failed password for invalid user lan from 119.29.132.143 port 42468 ssh2
Oct 31 01:48:22 hostnameproxy sshd[1322]: Invalid user frank from 119.29.132.143 port 44072
Oct 31 01:48:22 hostnameproxy sshd[1322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.132.143
Oct 31 01:48:24 hostnameproxy sshd[1322]: Failed password for invalid user frank from 119.29.132.143 port 44072 ssh2
Oct 31 01:48:38 hostnameproxy sshd[1333]: Invalid user sinusbot from 119.29.132.143 port 45146
Oct 31 01:48:38 hostnameproxy sshd[1333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.132.143
Oct 31 01:48:41 hostnameproxy sshd[1333]:........
------------------------------
2019-11-01 04:07:14
14.63.221.108 attackbotsspam
2019-10-31 09:11:00,321 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:28:19,155 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:45:44,082 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 10:07:49,978 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 10:30:05,947 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:11:00,321 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:28:19,155 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:45:44,082 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 10:07:49,978 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 10:30:05,947 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 09:11:00,321 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 14.63.221.108
2019-10-31 0
2019-11-01 03:53:08
106.12.77.212 attackbots
Oct 31 16:08:23 *** sshd[17834]: User root from 106.12.77.212 not allowed because not listed in AllowUsers
2019-11-01 04:16:08
104.42.27.187 attack
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:27:54,342 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:45:44,284 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:03:37,791 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:21:16,437 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:27:54,342 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:45:44,284 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:03:37,791 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:21:16,437 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 1
2019-11-01 04:13:14
52.164.211.22 attackspambots
SSH Brute Force, server-1 sshd[24127]: Failed password for root from 52.164.211.22 port 40352 ssh2
2019-11-01 03:50:31

最近上报的IP列表

15.175.17.253 54.253.208.103 52.29.203.240 184.193.157.254
18.135.221.73 13.37.76.130 101.47.29.248 98.94.26.239
64.205.72.52 54.90.125.232 54.82.115.226 3.83.220.42
200.138.46.101 79.124.40.190 45.74.28.179 103.186.77.70
1.81.21.141 195.184.76.6 172.180.64.141 192.168.0.179