City: Ashburn
Region: Virginia
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.220.42.188
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57270
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;13.220.42.188. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025062700 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jun 27 21:22:14 CST 2025
;; MSG SIZE rcvd: 106
188.42.220.13.in-addr.arpa domain name pointer ec2-13-220-42-188.compute-1.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
188.42.220.13.in-addr.arpa name = ec2-13-220-42-188.compute-1.amazonaws.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
49.231.247.62 | attackspambots | Unauthorized connection attempt from IP address 49.231.247.62 on Port 445(SMB) |
2019-12-01 23:05:07 |
117.50.43.236 | attackbots | $f2bV_matches |
2019-12-01 23:20:20 |
95.181.2.92 | attack | Unauthorized connection attempt from IP address 95.181.2.92 on Port 445(SMB) |
2019-12-01 22:55:26 |
154.16.53.24 | attack | (From eric@talkwithcustomer.com) Hey, You have a website mikulachiropractic.net, right? Of course you do. I am looking at your website now. It gets traffic every day – that you’re probably spending $2 / $4 / $10 or more a click to get. Not including all of the work you put into creating social media, videos, blog posts, emails, and so on. So you’re investing seriously in getting people to that site. But how’s it working? Great? Okay? Not so much? If that answer could be better, then it’s likely you’re putting a lot of time, effort, and money into an approach that’s not paying off like it should. Now… imagine doubling your lead conversion in just minutes… In fact, I’ll go even better. You could actually get up to 100X more conversions! I’m not making this up. As Chris Smith, best-selling author of The Conversion Code says: Speed is essential - there is a 100x decrease in Leads when a Lead is contacted within 14 minutes vs being contacted within 5 minutes. He’s backed up by a |
2019-12-01 23:28:12 |
51.91.136.174 | attackbotsspam | Dec 1 16:50:50 server2 sshd\[12006\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers Dec 1 16:50:59 server2 sshd\[12008\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers Dec 1 16:52:00 server2 sshd\[12044\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers Dec 1 16:54:21 server2 sshd\[12165\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers Dec 1 16:54:58 server2 sshd\[12171\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers Dec 1 16:56:40 server2 sshd\[12500\]: User root from 51.91.136.174 not allowed because not listed in AllowUsers |
2019-12-01 23:11:10 |
183.87.14.30 | attack | Unauthorized connection attempt from IP address 183.87.14.30 on Port 445(SMB) |
2019-12-01 22:52:25 |
218.92.0.188 | attack | 2019-12-01T15:58:10.937078scmdmz1 sshd\[5610\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.188 user=root 2019-12-01T15:58:12.398861scmdmz1 sshd\[5610\]: Failed password for root from 218.92.0.188 port 4821 ssh2 2019-12-01T15:58:15.867422scmdmz1 sshd\[5610\]: Failed password for root from 218.92.0.188 port 4821 ssh2 ... |
2019-12-01 22:59:29 |
181.40.81.198 | attackspambots | Dec 1 14:45:47 venus sshd\[32044\]: Invalid user yulissa from 181.40.81.198 port 41953 Dec 1 14:45:47 venus sshd\[32044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.40.81.198 Dec 1 14:45:49 venus sshd\[32044\]: Failed password for invalid user yulissa from 181.40.81.198 port 41953 ssh2 ... |
2019-12-01 23:05:40 |
187.59.102.116 | attackspam | Automatic report - Port Scan Attack |
2019-12-01 22:56:23 |
151.124.159.246 | attackspam | Unauthorized connection attempt from IP address 151.124.159.246 on Port 445(SMB) |
2019-12-01 23:36:50 |
59.92.91.223 | attackbotsspam | Unauthorised access (Dec 1) SRC=59.92.91.223 LEN=52 TOS=0x08 TTL=109 ID=20270 DF TCP DPT=445 WINDOW=8192 SYN |
2019-12-01 23:14:54 |
49.206.17.31 | attack | Unauthorized connection attempt from IP address 49.206.17.31 on Port 445(SMB) |
2019-12-01 23:29:17 |
190.248.67.123 | attack | fail2ban |
2019-12-01 23:29:35 |
115.159.25.60 | attackbots | Dec 1 15:53:42 ns3110291 sshd\[20945\]: Invalid user pencil from 115.159.25.60 Dec 1 15:53:42 ns3110291 sshd\[20945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.25.60 Dec 1 15:53:44 ns3110291 sshd\[20945\]: Failed password for invalid user pencil from 115.159.25.60 port 40928 ssh2 Dec 1 15:57:20 ns3110291 sshd\[21022\]: Invalid user gulzar from 115.159.25.60 Dec 1 15:57:20 ns3110291 sshd\[21022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.25.60 ... |
2019-12-01 23:09:08 |
106.13.143.111 | attackspam | 2019-12-01T15:40:23.296459ns386461 sshd\[24387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.143.111 user=root 2019-12-01T15:40:25.278809ns386461 sshd\[24387\]: Failed password for root from 106.13.143.111 port 42360 ssh2 2019-12-01T15:45:39.297738ns386461 sshd\[29003\]: Invalid user village from 106.13.143.111 port 51192 2019-12-01T15:45:39.302854ns386461 sshd\[29003\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.143.111 2019-12-01T15:45:41.000545ns386461 sshd\[29003\]: Failed password for invalid user village from 106.13.143.111 port 51192 ssh2 ... |
2019-12-01 23:10:53 |