城市(city): unknown
省份(region): unknown
国家(country): United Kingdom of Great Britain and Northern Ireland (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.142.232.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57666
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.142.232.212. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012802 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 08:00:21 CST 2025
;; MSG SIZE rcvd: 108Host 212.232.142.134.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 212.232.142.134.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 66.150.69.237 | attackspam | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across performancechiroofga.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http:// |
2020-03-18 14:35:28 |
| 202.153.34.244 | attackspam | Invalid user at from 202.153.34.244 port 44101 |
2020-03-18 14:24:55 |
| 31.207.34.147 | attackbots | SSH Brute-Force attacks |
2020-03-18 14:14:29 |
| 118.143.232.4 | attackbotsspam | $f2bV_matches |
2020-03-18 14:38:47 |
| 222.79.49.42 | attackspam | Fail2Ban Ban Triggered |
2020-03-18 14:15:29 |
| 181.177.114.65 | attack | Unauthorized access detected from black listed ip! |
2020-03-18 14:12:28 |
| 111.68.46.68 | attack | Mar 18 07:50:43 mout sshd[13405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68 user=root Mar 18 07:50:46 mout sshd[13405]: Failed password for root from 111.68.46.68 port 43262 ssh2 |
2020-03-18 14:54:27 |
| 103.42.57.65 | attackspambots | $f2bV_matches |
2020-03-18 14:33:04 |
| 148.233.136.34 | attackspambots | Invalid user oracle from 148.233.136.34 port 34591 |
2020-03-18 14:14:45 |
| 151.14.6.9 | attackbotsspam | SMB Server BruteForce Attack |
2020-03-18 14:56:49 |
| 51.75.208.177 | attack | Mar 18 06:27:31 vlre-nyc-1 sshd\[32679\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.208.177 user=root Mar 18 06:27:33 vlre-nyc-1 sshd\[32679\]: Failed password for root from 51.75.208.177 port 34730 ssh2 Mar 18 06:30:45 vlre-nyc-1 sshd\[307\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.208.177 user=root Mar 18 06:30:46 vlre-nyc-1 sshd\[307\]: Failed password for root from 51.75.208.177 port 43778 ssh2 Mar 18 06:33:55 vlre-nyc-1 sshd\[394\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.208.177 user=root ... |
2020-03-18 14:39:09 |
| 119.39.47.182 | attackbots | Fail2Ban Ban Triggered |
2020-03-18 14:16:37 |
| 218.92.0.179 | attack | Mar 18 07:03:22 h2779839 sshd[32609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179 user=root Mar 18 07:03:25 h2779839 sshd[32609]: Failed password for root from 218.92.0.179 port 18262 ssh2 Mar 18 07:03:36 h2779839 sshd[32609]: Failed password for root from 218.92.0.179 port 18262 ssh2 Mar 18 07:03:22 h2779839 sshd[32609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179 user=root Mar 18 07:03:25 h2779839 sshd[32609]: Failed password for root from 218.92.0.179 port 18262 ssh2 Mar 18 07:03:36 h2779839 sshd[32609]: Failed password for root from 218.92.0.179 port 18262 ssh2 Mar 18 07:03:22 h2779839 sshd[32609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.179 user=root Mar 18 07:03:25 h2779839 sshd[32609]: Failed password for root from 218.92.0.179 port 18262 ssh2 Mar 18 07:03:36 h2779839 sshd[32609]: Failed password for root fr ... |
2020-03-18 14:23:39 |
| 104.248.122.143 | attack | Mar 17 19:44:15 kapalua sshd\[8284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.122.143 user=root Mar 17 19:44:17 kapalua sshd\[8284\]: Failed password for root from 104.248.122.143 port 58824 ssh2 Mar 17 19:48:22 kapalua sshd\[8648\]: Invalid user testftp from 104.248.122.143 Mar 17 19:48:22 kapalua sshd\[8648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.122.143 Mar 17 19:48:24 kapalua sshd\[8648\]: Failed password for invalid user testftp from 104.248.122.143 port 52766 ssh2 |
2020-03-18 14:38:14 |
| 114.5.248.51 | attackbots | SpamScore above: 10.0 |
2020-03-18 14:41:33 |