城市(city): unknown
省份(region): unknown
国家(country): Korea Republic of
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.196.35.22
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;119.196.35.22. IN A
;; AUTHORITY SECTION:
. 362 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022700 1800 900 604800 86400
;; Query time: 52 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 16:34:03 CST 2022
;; MSG SIZE rcvd: 106
Host 22.35.196.119.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 22.35.196.119.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 196.171.39.7 | spamattack | They took over somehow my domain. I believe they have some buggy DNS servers that allow it do such thing. While they do have my domain for a little while - they are using my company's real email address to send tons of emails to nonexistent email recipients (hotmail, yahoo, google, etc. (public mail providers)). After a little while I get back tons of NDRs in my SMTP gateways and in corresponding user mailbox. Now the tricky part - I have to be on time when NDRs come in my SMTP gateway - because I have to remove them as soon as possible or there will be another loop and I my SMTP gateway will banned to global spam lists (p.s. It is banned now) |
2020-07-30 16:00:45 |
| 213.242.44.28 | attackbots | Automatic report - Port Scan Attack |
2020-07-30 15:43:47 |
| 222.76.203.58 | attack | Invalid user teraria from 222.76.203.58 port 2222 |
2020-07-30 15:41:32 |
| 221.155.59.5 | attackspambots | k+ssh-bruteforce |
2020-07-30 15:56:44 |
| 118.25.153.63 | attackspam | Invalid user teamspeak from 118.25.153.63 port 33070 |
2020-07-30 16:12:08 |
| 49.233.21.163 | attackbots | prod11 ... |
2020-07-30 16:10:26 |
| 122.51.45.200 | attackspambots | Invalid user weibb from 122.51.45.200 port 38802 |
2020-07-30 15:47:05 |
| 179.191.224.126 | attackspam | Jul 30 16:33:17 NG-HHDC-SVS-001 sshd[20062]: Invalid user wangjingxuan from 179.191.224.126 ... |
2020-07-30 16:01:44 |
| 103.151.125.49 | attackspam | Brute forcing email accounts |
2020-07-30 15:42:20 |
| 183.88.225.4 | attack | trying to access non-authorized port |
2020-07-30 15:59:36 |
| 120.53.12.94 | attackbotsspam | Jul 30 06:58:24 rush sshd[17218]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.53.12.94 Jul 30 06:58:26 rush sshd[17218]: Failed password for invalid user emuser from 120.53.12.94 port 57278 ssh2 Jul 30 07:03:19 rush sshd[17310]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.53.12.94 ... |
2020-07-30 15:57:36 |
| 184.105.139.125 | attackspambots | 07/29/2020-23:52:16.633026 184.105.139.125 Protocol: 17 GPL RPC xdmcp info query |
2020-07-30 15:48:31 |
| 182.74.25.246 | attackbotsspam | Invalid user gabriele from 182.74.25.246 port 21638 |
2020-07-30 16:18:53 |
| 54.253.145.214 | attack | Scanning for exploits - /wp-config.php |
2020-07-30 15:42:56 |
| 111.72.197.61 | attackbotsspam | Jul 30 08:42:24 srv01 postfix/smtpd\[18145\]: warning: unknown\[111.72.197.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 30 08:48:56 srv01 postfix/smtpd\[22727\]: warning: unknown\[111.72.197.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 30 08:59:23 srv01 postfix/smtpd\[22727\]: warning: unknown\[111.72.197.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 30 08:59:37 srv01 postfix/smtpd\[22727\]: warning: unknown\[111.72.197.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 30 08:59:53 srv01 postfix/smtpd\[22727\]: warning: unknown\[111.72.197.61\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-30 15:53:35 |