城市(city): unknown
省份(region): unknown
国家(country): Brazil
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 191.199.13.56
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15953
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;191.199.13.56. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022000 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 15:38:37 CST 2025
;; MSG SIZE rcvd: 10656.13.199.191.in-addr.arpa domain name pointer 191-199-13-56.user.vivozap.com.br.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
56.13.199.191.in-addr.arpa name = 191-199-13-56.user.vivozap.com.br.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 112.64.32.118 | attackspam | Feb 26 14:37:42 webmail sshd[26965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.64.32.118 Feb 26 14:37:44 webmail sshd[26965]: Failed password for invalid user wangmeng from 112.64.32.118 port 45098 ssh2 |
2020-02-26 22:52:29 |
| 64.94.211.152 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.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-02-26 23:09:34 |
| 213.230.67.32 | attack | $f2bV_matches |
2020-02-26 22:54:20 |
| 47.240.74.189 | attackspam | C1,WP GET /wp-login.php |
2020-02-26 22:51:14 |
| 213.87.101.176 | attackspam | $f2bV_matches |
2020-02-26 22:34:32 |
| 213.32.23.58 | attackspambots | $f2bV_matches |
2020-02-26 22:47:14 |
| 213.179.99.254 | attack | $f2bV_matches |
2020-02-26 23:04:28 |
| 213.32.120.155 | attack | $f2bV_matches |
2020-02-26 22:49:16 |
| 132.232.53.105 | attack | Feb 26 16:07:47 MK-Soft-VM8 sshd[2973]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.53.105 Feb 26 16:07:49 MK-Soft-VM8 sshd[2973]: Failed password for invalid user scan from 132.232.53.105 port 51370 ssh2 ... |
2020-02-26 23:10:23 |
| 190.156.231.245 | attack | Feb 26 15:42:28 vpn01 sshd[28122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.156.231.245 Feb 26 15:42:30 vpn01 sshd[28122]: Failed password for invalid user zhengyifan from 190.156.231.245 port 40403 ssh2 ... |
2020-02-26 22:59:57 |
| 213.85.3.250 | attackbots | $f2bV_matches |
2020-02-26 22:34:46 |
| 213.32.67.160 | attackspam | Feb 26 15:30:41 dev0-dcde-rnet sshd[18128]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.67.160 Feb 26 15:30:43 dev0-dcde-rnet sshd[18128]: Failed password for invalid user xiaoshengchang from 213.32.67.160 port 48626 ssh2 Feb 26 15:39:38 dev0-dcde-rnet sshd[18234]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.32.67.160 |
2020-02-26 22:45:30 |
| 213.6.8.38 | attackbotsspam | $f2bV_matches |
2020-02-26 22:39:24 |
| 222.186.173.154 | attackbots | Feb 26 15:33:23 h2177944 sshd\[13626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.154 user=root Feb 26 15:33:25 h2177944 sshd\[13626\]: Failed password for root from 222.186.173.154 port 60082 ssh2 Feb 26 15:33:28 h2177944 sshd\[13626\]: Failed password for root from 222.186.173.154 port 60082 ssh2 Feb 26 15:33:33 h2177944 sshd\[13626\]: Failed password for root from 222.186.173.154 port 60082 ssh2 ... |
2020-02-26 22:37:55 |
| 188.136.200.158 | attackbotsspam | 20/2/26@08:37:44: FAIL: Alarm-Network address from=188.136.200.158 20/2/26@08:37:44: FAIL: Alarm-Network address from=188.136.200.158 ... |
2020-02-26 22:50:14 |