城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 137.140.121.154
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13429
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;137.140.121.154. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 19 00:00:35 CST 2025
;; MSG SIZE rcvd: 108Host 154.121.140.137.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 154.121.140.137.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 71.83.123.141 | spambotsattackproxynormal | Sent attack |
2020-04-09 15:00:17 |
| 58.210.128.130 | attack | ssh brute force |
2020-04-09 15:01:38 |
| 51.91.157.101 | attackspam | Apr 9 06:54:31 markkoudstaal sshd[17150]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.157.101 Apr 9 06:54:33 markkoudstaal sshd[17150]: Failed password for invalid user jenkins from 51.91.157.101 port 44140 ssh2 Apr 9 06:58:30 markkoudstaal sshd[17681]: Failed password for root from 51.91.157.101 port 53178 ssh2 |
2020-04-09 15:02:06 |
| 47.75.172.46 | attackbots | xmlrpc attack |
2020-04-09 15:03:40 |
| 193.112.102.52 | attack | SSH login attempts. |
2020-04-09 15:30:35 |
| 218.92.0.200 | attack | Unauthorized connection attempt detected from IP address 218.92.0.200 to port 22 [T] |
2020-04-09 15:03:24 |
| 142.93.53.214 | attack | Apr 9 09:22:39 server sshd\[15073\]: Invalid user ubuntu from 142.93.53.214 Apr 9 09:22:39 server sshd\[15073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.53.214 Apr 9 09:22:41 server sshd\[15073\]: Failed password for invalid user ubuntu from 142.93.53.214 port 40088 ssh2 Apr 9 09:27:21 server sshd\[16094\]: Invalid user db2inst1 from 142.93.53.214 Apr 9 09:27:21 server sshd\[16094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.53.214 ... |
2020-04-09 14:58:54 |
| 80.91.164.72 | attackspambots | $f2bV_matches |
2020-04-09 15:07:28 |
| 157.245.158.214 | attackbotsspam | SSH login attempts. |
2020-04-09 15:25:24 |
| 188.163.104.88 | attackbots | CMS (WordPress or Joomla) login attempt. |
2020-04-09 15:37:44 |
| 14.18.53.156 | attackbots | Brute forcing RDP port 3389 |
2020-04-09 15:24:59 |
| 49.235.139.216 | attack | Apr 9 12:27:31 gw1 sshd[8437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.139.216 Apr 9 12:27:33 gw1 sshd[8437]: Failed password for invalid user postgres from 49.235.139.216 port 54050 ssh2 ... |
2020-04-09 15:29:44 |
| 173.234.48.67 | attackbots | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with lakechirocenter.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture any |
2020-04-09 15:29:19 |
| 193.56.28.16 | attackbotsspam | Apr 9 09:26:30 relay postfix/smtpd\[30131\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 9 09:26:30 relay postfix/smtpd\[31822\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 9 09:26:32 relay postfix/smtpd\[31822\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 9 09:26:32 relay postfix/smtpd\[30131\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 9 09:26:34 relay postfix/smtpd\[31822\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 9 09:26:34 relay postfix/smtpd\[30131\]: warning: unknown\[193.56.28.16\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-04-09 15:30:59 |
| 111.229.126.37 | attackspam | SSH login attempts. |
2020-04-09 15:45:12 |