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

城市(city): unknown

省份(region): unknown

国家(country): Russian Federation

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 109.111.134.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64127
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;109.111.134.42.			IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 17:06:08 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
42.134.111.109.in-addr.arpa domain name pointer ppp109-111-134-42.tis-dialog.ru.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.134.111.109.in-addr.arpa	name = ppp109-111-134-42.tis-dialog.ru.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
185.232.30.130 attackbotsspam
04/23/2020-13:20:48.299639 185.232.30.130 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-24 03:50:11
62.205.165.137 attackbotsspam
Apr 23 20:40:07 ourumov-web sshd\[12934\]: Invalid user vb from 62.205.165.137 port 56112
Apr 23 20:40:07 ourumov-web sshd\[12934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.205.165.137
Apr 23 20:40:09 ourumov-web sshd\[12934\]: Failed password for invalid user vb from 62.205.165.137 port 56112 ssh2
...
2020-04-24 03:15:37
137.74.173.182 attack
2020-04-23T19:47:36.157641vps751288.ovh.net sshd\[5809\]: Invalid user cm from 137.74.173.182 port 50434
2020-04-23T19:47:36.164615vps751288.ovh.net sshd\[5809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=aula.madridemprende.es
2020-04-23T19:47:37.902515vps751288.ovh.net sshd\[5809\]: Failed password for invalid user cm from 137.74.173.182 port 50434 ssh2
2020-04-23T19:51:23.952168vps751288.ovh.net sshd\[5839\]: Invalid user test from 137.74.173.182 port 36364
2020-04-23T19:51:23.957909vps751288.ovh.net sshd\[5839\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=aula.madridemprende.es
2020-04-24 03:17:48
13.92.138.88 attack
xmlrpc attack
2020-04-24 03:43:49
200.199.142.162 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-04-24 03:27:10
45.83.118.106 attack
[2020-04-23 15:18:20] NOTICE[1170][C-000043bb] chan_sip.c: Call from '' (45.83.118.106:52280) to extension '46842002315' rejected because extension not found in context 'public'.
[2020-04-23 15:18:20] SECURITY[1184] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-04-23T15:18:20.699-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="46842002315",SessionID="0x7f6c0866f058",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.83.118.106/52280",ACLName="no_extension_match"
[2020-04-23 15:20:21] NOTICE[1170][C-000043bf] chan_sip.c: Call from '' (45.83.118.106:51258) to extension '01146842002315' rejected because extension not found in context 'public'.
[2020-04-23 15:20:21] SECURITY[1184] res_security_log.c: SecurityEvent="FailedACL",EventTV="2020-04-23T15:20:21.010-0400",Severity="Error",Service="SIP",EventVersion="1",AccountID="01146842002315",SessionID="0x7f6c0805fd68",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/45.83.118.
...
2020-04-24 03:51:45
183.83.78.180 attack
Invalid user login from 183.83.78.180 port 37169
2020-04-24 03:22:48
43.226.49.23 attackspambots
Apr 23 19:35:53 * sshd[10405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.49.23
Apr 23 19:35:55 * sshd[10405]: Failed password for invalid user temp from 43.226.49.23 port 55274 ssh2
2020-04-24 03:14:43
179.191.237.172 attackbotsspam
Apr 23 18:43:50 vpn01 sshd[5500]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.191.237.172
Apr 23 18:43:52 vpn01 sshd[5500]: Failed password for invalid user tt from 179.191.237.172 port 55244 ssh2
...
2020-04-24 03:21:00
175.138.108.78 attackbots
$f2bV_matches
2020-04-24 03:56:12
181.126.83.125 attackspambots
Apr 24 00:14:40 webhost01 sshd[24291]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.126.83.125
Apr 24 00:14:42 webhost01 sshd[24291]: Failed password for invalid user dv from 181.126.83.125 port 40070 ssh2
...
2020-04-24 03:23:01
104.215.188.2 attackspam
2020-04-23T18:08:24Z - RDP login failed multiple times. (104.215.188.2)
2020-04-24 03:39:45
5.45.68.189 attackbotsspam
Dear Sir / Madam, 
Yesterday, my close friend (Simona Simova) was contacted via fake Facebook profile to be informed that she has a profile on a escort website. While researching via the German phone number used in the advert, we have came across more ads. These profiles are created without her permission and she is now very upset. 

Here is a list of the profiles we have found: 

- https://escortsofia.info/de/sia-11/ (5.45.68.189)
- https://escortsofia.info/de/eleonora-8/ (5.45.68.189)
- https://escortinberlin.info/eleonora-3/ (5.45.68.189)
- https://escortinberlin.info/sia-2/ (5.45.68.189)

We have already hired a lawyer in Germany who will escalate the issue to the authorities.
2020-04-24 03:31:08
2.249.176.128 attackbots
Honeypot attack, port: 5555, PTR: 2-249-176-128-no2200.tbcn.telia.com.
2020-04-24 03:49:51
138.197.221.114 attackbotsspam
Apr 23 20:37:23 ourumov-web sshd\[12672\]: Invalid user ubuntu from 138.197.221.114 port 43688
Apr 23 20:37:23 ourumov-web sshd\[12672\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.221.114
Apr 23 20:37:24 ourumov-web sshd\[12672\]: Failed password for invalid user ubuntu from 138.197.221.114 port 43688 ssh2
...
2020-04-24 03:21:57

最近上报的IP列表

109.111.134.39 109.111.134.28 109.111.134.45 109.111.134.55
109.111.134.60 109.111.134.59 109.111.134.62 109.111.134.69
109.111.134.7 109.111.134.50 109.111.134.78 109.111.134.81
109.111.134.77 109.111.134.88 109.111.134.74 109.111.134.94
109.111.135.108 109.111.135.112 109.111.135.111 109.111.135.107