城市(city): unknown
省份(region): unknown
国家(country): Brazil
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 206.84.57.77
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19769
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;206.84.57.77. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022000 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 21:58:22 CST 2025
;; MSG SIZE rcvd: 105
77.57.84.206.in-addr.arpa domain name pointer 206.84.57.77.assistemas.net.br.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
77.57.84.206.in-addr.arpa name = 206.84.57.77.assistemas.net.br.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 222.186.169.194 | attackbotsspam | Jul 11 23:24:16 nextcloud sshd\[4104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194 user=root Jul 11 23:24:18 nextcloud sshd\[4104\]: Failed password for root from 222.186.169.194 port 41168 ssh2 Jul 11 23:24:34 nextcloud sshd\[4426\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194 user=root |
2020-07-12 05:26:22 |
| 201.91.86.28 | attack | Jul 11 23:06:39 santamaria sshd\[4001\]: Invalid user ipo from 201.91.86.28 Jul 11 23:06:39 santamaria sshd\[4001\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.91.86.28 Jul 11 23:06:41 santamaria sshd\[4001\]: Failed password for invalid user ipo from 201.91.86.28 port 38465 ssh2 ... |
2020-07-12 05:17:01 |
| 185.143.72.23 | attackspam | Jul 11 23:29:52 srv01 postfix/smtpd\[2999\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:23 srv01 postfix/smtpd\[1946\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:53 srv01 postfix/smtpd\[1945\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:24 srv01 postfix/smtpd\[1946\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:55 srv01 postfix/smtpd\[7677\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:46:20 |
| 46.38.148.22 | attackspambots | Jul 11 23:44:17 srv01 postfix/smtpd\[11186\]: warning: unknown\[46.38.148.22\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:44:40 srv01 postfix/smtpd\[10784\]: warning: unknown\[46.38.148.22\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:45:03 srv01 postfix/smtpd\[8986\]: warning: unknown\[46.38.148.22\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:45:23 srv01 postfix/smtpd\[7677\]: warning: unknown\[46.38.148.22\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:45:48 srv01 postfix/smtpd\[8986\]: warning: unknown\[46.38.148.22\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:47:23 |
| 93.152.159.11 | attack | Jul 11 16:04:04 ny01 sshd[27321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.152.159.11 Jul 11 16:04:06 ny01 sshd[27321]: Failed password for invalid user tarra from 93.152.159.11 port 40000 ssh2 Jul 11 16:07:10 ny01 sshd[27734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.152.159.11 |
2020-07-12 05:28:48 |
| 46.38.148.10 | attackspam | Jul 11 23:07:15 relay postfix/smtpd\[20454\]: warning: unknown\[46.38.148.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:07:29 relay postfix/smtpd\[13678\]: warning: unknown\[46.38.148.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:08:12 relay postfix/smtpd\[16009\]: warning: unknown\[46.38.148.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:08:26 relay postfix/smtpd\[16513\]: warning: unknown\[46.38.148.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:09:10 relay postfix/smtpd\[16011\]: warning: unknown\[46.38.148.10\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:11:59 |
| 91.203.81.226 | attack | Automatic report - Banned IP Access |
2020-07-12 05:17:18 |
| 23.129.64.216 | attack | Jul 11 22:07:22 lnxweb62 sshd[30272]: Failed password for root from 23.129.64.216 port 20407 ssh2 Jul 11 22:07:24 lnxweb62 sshd[30272]: Failed password for root from 23.129.64.216 port 20407 ssh2 Jul 11 22:07:27 lnxweb62 sshd[30272]: Failed password for root from 23.129.64.216 port 20407 ssh2 Jul 11 22:07:29 lnxweb62 sshd[30272]: Failed password for root from 23.129.64.216 port 20407 ssh2 |
2020-07-12 05:15:33 |
| 104.153.96.154 | attack | Jul 12 00:21:32 journals sshd\[110811\]: Invalid user demo from 104.153.96.154 Jul 12 00:21:32 journals sshd\[110811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.153.96.154 Jul 12 00:21:35 journals sshd\[110811\]: Failed password for invalid user demo from 104.153.96.154 port 37242 ssh2 Jul 12 00:28:26 journals sshd\[111403\]: Invalid user shiba from 104.153.96.154 Jul 12 00:28:26 journals sshd\[111403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.153.96.154 ... |
2020-07-12 05:30:25 |
| 186.193.124.2 | attackbotsspam | Lines containing failures of 186.193.124.2 Jul 10 17:17:47 neweola sshd[21874]: Invalid user shubham from 186.193.124.2 port 36144 Jul 10 17:17:47 neweola sshd[21874]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.193.124.2 Jul 10 17:17:50 neweola sshd[21874]: Failed password for invalid user shubham from 186.193.124.2 port 36144 ssh2 Jul 10 17:17:51 neweola sshd[21874]: Received disconnect from 186.193.124.2 port 36144:11: Bye Bye [preauth] Jul 10 17:17:51 neweola sshd[21874]: Disconnected from invalid user shubham 186.193.124.2 port 36144 [preauth] Jul 10 17:30:55 neweola sshd[22614]: Invalid user sunjingge from 186.193.124.2 port 35432 Jul 10 17:30:55 neweola sshd[22614]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.193.124.2 Jul 10 17:30:56 neweola sshd[22614]: Failed password for invalid user sunjingge from 186.193.124.2 port 35432 ssh2 Jul 10 17:30:57 neweola sshd[22614]:........ ------------------------------ |
2020-07-12 05:15:59 |
| 188.226.202.13 | attackbots | Invalid user sstcvetkov from 188.226.202.13 port 57671 |
2020-07-12 05:46:48 |
| 222.186.180.8 | attackbotsspam | Jul 11 23:11:29 nextcloud sshd\[21933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8 user=root Jul 11 23:11:31 nextcloud sshd\[21933\]: Failed password for root from 222.186.180.8 port 4210 ssh2 Jul 11 23:11:47 nextcloud sshd\[22296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8 user=root |
2020-07-12 05:22:15 |
| 134.209.102.196 | attackbots | Invalid user tsbot from 134.209.102.196 port 43134 |
2020-07-12 05:37:45 |
| 112.85.42.187 | attack | 2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root 2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root 2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 2020-07-11T17:41:50.965264uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 ... |
2020-07-12 05:43:20 |
| 23.94.4.205 | 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 palmerchiroga.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 v |
2020-07-12 05:34:01 |