城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.140.169.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41005
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.140.169.4. IN A
;; AUTHORITY SECTION:
. 86 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022801 1800 900 604800 86400
;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 01 03:08:54 CST 2022
;; MSG SIZE rcvd: 106
4.169.140.104.in-addr.arpa domain name pointer 4-169-140-104.staticrdns.eonix.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
4.169.140.104.in-addr.arpa name = 4-169-140-104.staticrdns.eonix.net.
Authoritative answers can be found from:
IP | 类型 | 评论内容 | 时间 |
---|---|---|---|
157.230.186.166 | attackspambots | Jul 7 12:30:50 server sshd\[47691\]: Invalid user sergey from 157.230.186.166 Jul 7 12:30:50 server sshd\[47691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.186.166 Jul 7 12:30:51 server sshd\[47691\]: Failed password for invalid user sergey from 157.230.186.166 port 51740 ssh2 ... |
2019-07-12 01:25:03 |
75.127.5.51 | attackbotsspam | (From eric@talkwithcustomer.com) Hello lifesourcefamilychiro.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website lifesourcefamilychiro.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website lifesourcefamilychiro.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Ti |
2019-07-12 00:28:40 |
181.118.122.40 | attackbots | Caught in portsentry honeypot |
2019-07-12 00:54:59 |
159.203.179.230 | attackspambots | Jun 23 09:56:28 server sshd\[23396\]: Invalid user herve from 159.203.179.230 Jun 23 09:56:28 server sshd\[23396\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.179.230 Jun 23 09:56:30 server sshd\[23396\]: Failed password for invalid user herve from 159.203.179.230 port 59634 ssh2 ... |
2019-07-12 00:37:31 |
159.65.137.23 | attackspambots | Jul 7 07:15:08 server sshd\[38228\]: Invalid user raja from 159.65.137.23 Jul 7 07:15:08 server sshd\[38228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.137.23 Jul 7 07:15:10 server sshd\[38228\]: Failed password for invalid user raja from 159.65.137.23 port 43744 ssh2 ... |
2019-07-12 00:15:16 |
157.230.183.255 | attackbots | May 26 01:52:31 server sshd\[233242\]: Invalid user zang from 157.230.183.255 May 26 01:52:31 server sshd\[233242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.183.255 May 26 01:52:33 server sshd\[233242\]: Failed password for invalid user zang from 157.230.183.255 port 51168 ssh2 ... |
2019-07-12 01:27:59 |
82.202.212.60 | attack | Jul 11 14:15:07 ip-172-31-62-245 sshd\[22163\]: Invalid user kafka from 82.202.212.60\ Jul 11 14:15:08 ip-172-31-62-245 sshd\[22163\]: Failed password for invalid user kafka from 82.202.212.60 port 49718 ssh2\ Jul 11 14:15:11 ip-172-31-62-245 sshd\[22165\]: Invalid user ec2-user from 82.202.212.60\ Jul 11 14:15:13 ip-172-31-62-245 sshd\[22165\]: Failed password for invalid user ec2-user from 82.202.212.60 port 54904 ssh2\ Jul 11 14:15:14 ip-172-31-62-245 sshd\[22167\]: Invalid user awsgui from 82.202.212.60\ |
2019-07-12 00:31:52 |
104.42.25.12 | attack | NAME : MSFT CIDR : 104.40.0.0/13 SYN Flood DDoS Attack USA - Washington - block certain countries :) IP: 104.42.25.12 Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN - data recovery https://help-dysk.pl |
2019-07-12 01:23:45 |
90.127.199.222 | attack | $f2bV_matches |
2019-07-12 01:02:22 |
157.230.44.56 | attackbots | Jul 3 00:11:08 server sshd\[169753\]: Invalid user vijaya from 157.230.44.56 Jul 3 00:11:08 server sshd\[169753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.44.56 Jul 3 00:11:10 server sshd\[169753\]: Failed password for invalid user vijaya from 157.230.44.56 port 52388 ssh2 ... |
2019-07-12 01:02:55 |
159.65.150.212 | attack | Jul 11 04:31:27 extapp sshd[32246]: Invalid user fake from 159.65.150.212 Jul 11 04:31:29 extapp sshd[32246]: Failed password for invalid user fake from 159.65.150.212 port 56038 ssh2 Jul 11 04:31:30 extapp sshd[32266]: Invalid user ubnt from 159.65.150.212 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=159.65.150.212 |
2019-07-12 01:17:16 |
158.69.192.35 | attackbotsspam | Jun 25 20:11:27 server sshd\[188318\]: Invalid user Alphanetworks from 158.69.192.35 Jun 25 20:11:27 server sshd\[188318\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.192.35 Jun 25 20:11:29 server sshd\[188318\]: Failed password for invalid user Alphanetworks from 158.69.192.35 port 38680 ssh2 ... |
2019-07-12 00:53:07 |
157.230.190.247 | attack | Apr 30 20:27:28 server sshd\[165016\]: Invalid user uploader from 157.230.190.247 Apr 30 20:27:28 server sshd\[165016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.190.247 Apr 30 20:27:30 server sshd\[165016\]: Failed password for invalid user uploader from 157.230.190.247 port 39242 ssh2 ... |
2019-07-12 01:23:21 |
159.203.12.135 | attack | Jul 4 10:20:29 server sshd\[7064\]: Invalid user gts from 159.203.12.135 Jul 4 10:20:29 server sshd\[7064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.12.135 Jul 4 10:20:31 server sshd\[7064\]: Failed password for invalid user gts from 159.203.12.135 port 58414 ssh2 ... |
2019-07-12 00:46:49 |
81.22.45.219 | attack | 11.07.2019 16:31:48 Connection to port 6698 blocked by firewall |
2019-07-12 00:44:13 |