城市(city): Columbus
省份(region): Ohio
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 3.140.6.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5754
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.140.6.67. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025062900 1800 900 604800 86400
;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 29 19:18:31 CST 2025
;; MSG SIZE rcvd: 103
67.6.140.3.in-addr.arpa domain name pointer ec2-3-140-6-67.us-east-2.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
67.6.140.3.in-addr.arpa name = ec2-3-140-6-67.us-east-2.compute.amazonaws.com.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 101.89.151.127 | attackspambots | Banned for a week because repeated abuses, for example SSH, but not only |
2020-08-12 06:27:21 |
| 23.95.97.207 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found sordillochiropracticcentre.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new s |
2020-08-12 06:37:36 |
| 193.228.91.123 | attack | SSH brute-force attempt |
2020-08-12 06:24:06 |
| 222.186.15.158 | attack | Aug 12 00:37:15 *host* sshd\[2207\]: User *user* from 222.186.15.158 not allowed because none of user's groups are listed in AllowGroups |
2020-08-12 06:41:13 |
| 181.188.170.73 | attackbotsspam | Aug 11 22:35:38 server postfix/smtpd[19402]: NOQUEUE: reject: RCPT from unknown[181.188.170.73]: 554 5.7.1 Service unavailable; Client host [181.188.170.73] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/181.188.170.73 / https://www.spamhaus.org/sbl/query/SBLCSS; from= |
2020-08-12 06:33:09 |
| 119.4.225.31 | attackbotsspam | Aug 12 00:06:42 vm1 sshd[636]: Failed password for root from 119.4.225.31 port 39070 ssh2 ... |
2020-08-12 06:24:21 |
| 129.204.42.59 | attack | Failed password for root from 129.204.42.59 port 58686 ssh2 |
2020-08-12 06:18:42 |
| 167.99.155.36 | attack | DATE:2020-08-12 00:27:37,IP:167.99.155.36,MATCHES:10,PORT:ssh |
2020-08-12 06:31:16 |
| 152.136.105.190 | attack | Aug 11 13:26:12 pixelmemory sshd[3444952]: Failed password for root from 152.136.105.190 port 58006 ssh2 Aug 11 13:32:30 pixelmemory sshd[3459621]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.105.190 user=root Aug 11 13:32:32 pixelmemory sshd[3459621]: Failed password for root from 152.136.105.190 port 40300 ssh2 Aug 11 13:38:46 pixelmemory sshd[3474428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.105.190 user=root Aug 11 13:38:47 pixelmemory sshd[3474428]: Failed password for root from 152.136.105.190 port 50828 ssh2 ... |
2020-08-12 06:21:51 |
| 82.117.196.30 | attackspam | Fail2Ban Ban Triggered (2) |
2020-08-12 06:39:58 |
| 152.32.72.122 | attackspambots | Aug 12 01:01:57 lukav-desktop sshd\[9301\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.72.122 user=root Aug 12 01:01:59 lukav-desktop sshd\[9301\]: Failed password for root from 152.32.72.122 port 7238 ssh2 Aug 12 01:06:57 lukav-desktop sshd\[32231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.72.122 user=root Aug 12 01:06:59 lukav-desktop sshd\[32231\]: Failed password for root from 152.32.72.122 port 4644 ssh2 Aug 12 01:11:38 lukav-desktop sshd\[5211\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.72.122 user=root |
2020-08-12 06:14:37 |
| 222.64.19.198 | attackbotsspam | Aug 12 00:42:00 journals sshd\[121061\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.64.19.198 user=root Aug 12 00:42:02 journals sshd\[121061\]: Failed password for root from 222.64.19.198 port 2080 ssh2 Aug 12 00:45:33 journals sshd\[121257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.64.19.198 user=root Aug 12 00:45:34 journals sshd\[121257\]: Failed password for root from 222.64.19.198 port 2081 ssh2 Aug 12 00:49:10 journals sshd\[121518\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.64.19.198 user=root ... |
2020-08-12 06:06:10 |
| 193.27.229.190 | attackspambots | firewall-block, port(s): 11772/tcp, 41427/tcp, 52719/tcp |
2020-08-12 06:20:58 |
| 123.56.5.75 | attack | Detected by ModSecurity. Host header is an IP address, Request URI: / |
2020-08-12 06:39:43 |
| 189.254.21.6 | attackbotsspam | Aug 11 23:55:13 eventyay sshd[25409]: Failed password for root from 189.254.21.6 port 38170 ssh2 Aug 11 23:59:36 eventyay sshd[25536]: Failed password for root from 189.254.21.6 port 48812 ssh2 ... |
2020-08-12 06:08:47 |