City: Boardman
Region: Oregon
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.213.204.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13668
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;54.213.204.139. IN A
;; AUTHORITY SECTION:
. 459 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020080801 1800 900 604800 86400
;; Query time: 51 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 09 09:12:35 CST 2020
;; MSG SIZE rcvd: 118139.204.213.54.in-addr.arpa domain name pointer ec2-54-213-204-139.us-west-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
139.204.213.54.in-addr.arpa name = ec2-54-213-204-139.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 154.83.15.28 | attackspambots | $f2bV_matches |
2019-10-18 23:23:04 |
| 51.79.129.237 | attackbots | 2019-10-18T14:34:18.297264abusebot-5.cloudsearch.cf sshd\[21234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip237.ip-51-79-129.net user=root |
2019-10-18 22:59:04 |
| 49.88.112.111 | attack | Oct 18 16:56:03 vps647732 sshd[23676]: Failed password for root from 49.88.112.111 port 25618 ssh2 ... |
2019-10-18 23:15:45 |
| 198.251.89.80 | attackspam | 2019-10-18T15:23:59.280819abusebot.cloudsearch.cf sshd\[19521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=tor-exit-01.nonanet.net user=root |
2019-10-18 23:25:03 |
| 188.165.238.65 | attackspambots | 2019-09-23 07:49:48,386 fail2ban.actions [818]: NOTICE [sshd] Ban 188.165.238.65 2019-09-23 10:56:41,492 fail2ban.actions [818]: NOTICE [sshd] Ban 188.165.238.65 2019-09-23 14:02:18,350 fail2ban.actions [818]: NOTICE [sshd] Ban 188.165.238.65 ... |
2019-10-18 22:58:03 |
| 129.28.97.252 | attack | Automatic report - Banned IP Access |
2019-10-18 23:27:39 |
| 39.98.43.197 | attack | HTTP/80/443 Probe, BF, WP, Hack - |
2019-10-18 23:13:03 |
| 139.178.76.99 | attack | Automatic report - Banned IP Access |
2019-10-18 23:17:11 |
| 185.153.208.26 | attack | Automatic report - Banned IP Access |
2019-10-18 23:20:38 |
| 181.45.227.38 | attack | Fail2Ban Ban Triggered |
2019-10-18 23:01:28 |
| 162.62.26.238 | attack | firewall-block, port(s): 623/udp |
2019-10-18 23:03:01 |
| 202.98.248.123 | attackbotsspam | 2019-09-24 13:04:32,604 fail2ban.actions [818]: NOTICE [sshd] Ban 202.98.248.123 2019-09-24 16:10:21,102 fail2ban.actions [818]: NOTICE [sshd] Ban 202.98.248.123 2019-09-24 19:23:21,140 fail2ban.actions [818]: NOTICE [sshd] Ban 202.98.248.123 ... |
2019-10-18 22:57:00 |
| 139.198.189.36 | attack | Oct 18 11:59:47 firewall sshd[14948]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.189.36 Oct 18 11:59:47 firewall sshd[14948]: Invalid user shashank from 139.198.189.36 Oct 18 11:59:48 firewall sshd[14948]: Failed password for invalid user shashank from 139.198.189.36 port 45334 ssh2 ... |
2019-10-18 23:34:59 |
| 106.201.238.226 | attackbots | firewall-block, port(s): 1433/tcp |
2019-10-18 23:07:40 |
| 60.172.53.138 | attackbotsspam | Unauthorised access (Oct 18) SRC=60.172.53.138 LEN=52 TOS=0x10 PREC=0x40 TTL=48 ID=13781 DF TCP DPT=445 WINDOW=8192 SYN |
2019-10-18 23:11:06 |