City: Jakarta
Region: Jakarta
Country: Indonesia
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.192.126.219
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24113
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;139.192.126.219. IN A
;; AUTHORITY SECTION:
. 348 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019121401 1800 900 604800 86400
;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 15 05:00:28 CST 2019
;; MSG SIZE rcvd: 119Host 219.126.192.139.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 219.126.192.139.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 125.112.109.238 | attackbotsspam | Port 1433 Scan |
2019-10-28 15:37:09 |
| 201.17.192.178 | attackbotsspam | 8080/tcp [2019-10-28]1pkt |
2019-10-28 15:31:54 |
| 182.56.188.93 | attackbotsspam | Honeypot attack, port: 23, PTR: static-mum-182.56.188.93.mtnl.net.in. |
2019-10-28 15:46:04 |
| 27.3.8.35 | attackspam | 445/tcp [2019-10-28]1pkt |
2019-10-28 15:30:05 |
| 184.75.211.142 | attackspambots | (From david@davidmelnichuk.com) I saw this form on your site, and I submitted it. Now you’re reading this, so that means it works. Awesome! But that’s not enough. For this form to make your business money, people have to respond to you when you reach out to them. Don’t you hate it when they never answer, or by the time you get back to them, they already decided to do business with your competitor? This ends today. I made a free video tutorial that shows you how to setup an immediate SMS message and email response to go out to every lead that submits this form so you can start a conversation while they are still thinking about your services. If you contact a lead in the first 2 minutes after they’ve submitted this web form, they’re 100x more likely to respond and 78% of customers buy from the first responder. Check out my free tutorial on how to set this up: http://bit.ly/how-to-setup-an-automatic-sms-and-email What’s the catch? Nothing. My step-by-step training here is completely free and will show y |
2019-10-28 15:40:16 |
| 129.28.191.55 | attackbots | Oct 28 04:11:00 www_kotimaassa_fi sshd[4178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.191.55 Oct 28 04:11:02 www_kotimaassa_fi sshd[4178]: Failed password for invalid user Snda-GZrjy@))* from 129.28.191.55 port 58756 ssh2 ... |
2019-10-28 15:31:34 |
| 123.132.133.80 | attackbotsspam | 23/tcp [2019-10-28]1pkt |
2019-10-28 15:27:49 |
| 123.21.33.151 | attackspam | 2019-10-28T03:42:46.141992shield sshd\[23429\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.21.33.151 user=root 2019-10-28T03:42:48.049051shield sshd\[23429\]: Failed password for root from 123.21.33.151 port 3612 ssh2 2019-10-28T03:51:43.586132shield sshd\[24780\]: Invalid user sysop from 123.21.33.151 port 11169 2019-10-28T03:51:43.590430shield sshd\[24780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.21.33.151 2019-10-28T03:51:45.552451shield sshd\[24780\]: Failed password for invalid user sysop from 123.21.33.151 port 11169 ssh2 |
2019-10-28 15:33:53 |
| 132.145.213.82 | attack | rain |
2019-10-28 16:00:32 |
| 221.185.193.144 | attackspambots | 23/tcp [2019-10-28]1pkt |
2019-10-28 15:37:32 |
| 184.22.79.240 | attack | Fail2Ban Ban Triggered |
2019-10-28 15:49:38 |
| 81.22.45.116 | attackbotsspam | Oct 28 08:20:32 h2177944 kernel: \[5123011.224674\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=2210 PROTO=TCP SPT=46708 DPT=31903 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 28 08:22:13 h2177944 kernel: \[5123111.955026\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=10515 PROTO=TCP SPT=46708 DPT=32373 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 28 08:27:45 h2177944 kernel: \[5123444.175891\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=2650 PROTO=TCP SPT=46708 DPT=32093 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 28 08:28:13 h2177944 kernel: \[5123471.486128\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.116 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=12988 PROTO=TCP SPT=46708 DPT=32207 WINDOW=1024 RES=0x00 SYN URGP=0 Oct 28 08:29:35 h2177944 kernel: \[5123553.959429\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=81.22.45.116 DST=85.214.117.9 LE |
2019-10-28 15:34:20 |
| 189.209.255.191 | attackbotsspam | Automatic report - Port Scan Attack |
2019-10-28 15:44:48 |
| 171.228.203.118 | attackbotsspam | 445/tcp [2019-10-28]1pkt |
2019-10-28 15:28:33 |
| 185.211.245.170 | attack | Oct 28 01:14:30 elektron postfix/smtpd\[16645\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 01:14:39 elektron postfix/smtpd\[18352\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 01:17:13 elektron postfix/smtpd\[16645\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 02:23:40 elektron postfix/smtpd\[27542\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 02:23:49 elektron postfix/smtpd\[25872\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 02:25:08 elektron postfix/smtpd\[25872\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 02:25:16 elektron postfix/smtpd\[23685\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 03:10:39 elektron postfix/smtpd\[2173\]: warning: unknown\[185.211.245.170\]: SASL PLAIN authentication failed: Oct 28 03:10:47 elektron postfix/smtpd\[3860\]: warning: unknown\ |
2019-10-28 15:43:01 |