City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.219.107.140
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6302
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.219.107.140. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012301 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Jan 24 03:10:39 CST 2025
;; MSG SIZE rcvd: 107
140.107.219.54.in-addr.arpa domain name pointer ec2-54-219-107-140.us-west-1.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
140.107.219.54.in-addr.arpa name = ec2-54-219-107-140.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
175.107.198.23 | attackspambots | Nov 11 02:19:24 rb06 sshd[23092]: Failed password for invalid user named from 175.107.198.23 port 44858 ssh2 Nov 11 02:19:24 rb06 sshd[23092]: Received disconnect from 175.107.198.23: 11: Bye Bye [preauth] Nov 11 02:27:16 rb06 sshd[24585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.107.198.23 user=r.r Nov 11 02:27:18 rb06 sshd[24585]: Failed password for r.r from 175.107.198.23 port 44736 ssh2 Nov 11 02:27:18 rb06 sshd[24585]: Received disconnect from 175.107.198.23: 11: Bye Bye [preauth] Nov 11 02:31:22 rb06 sshd[25871]: Failed password for invalid user ws from 175.107.198.23 port 34946 ssh2 Nov 11 02:31:22 rb06 sshd[25871]: Received disconnect from 175.107.198.23: 11: Bye Bye [preauth] Nov 11 02:35:22 rb06 sshd[23742]: Failed password for invalid user phylys from 175.107.198.23 port 53389 ssh2 Nov 11 02:35:22 rb06 sshd[23742]: Received disconnect from 175.107.198.23: 11: Bye Bye [preauth] Nov 11 02:41:14 rb06 sshd[537]........ ------------------------------- |
2019-11-11 13:23:48 |
92.119.160.66 | attackspam | 11/11/2019-00:29:53.798861 92.119.160.66 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2019-11-11 13:30:40 |
123.207.90.4 | attackspambots | 5x Failed Password |
2019-11-11 13:58:31 |
185.162.235.107 | attack | Nov 11 06:31:59 mail postfix/smtpd[15439]: warning: unknown[185.162.235.107]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 11 06:37:35 mail postfix/smtpd[16712]: warning: unknown[185.162.235.107]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 11 06:37:40 mail postfix/smtpd[16508]: warning: unknown[185.162.235.107]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2019-11-11 13:47:20 |
117.160.138.79 | attackbots | 117.160.138.79 was recorded 5 times by 5 hosts attempting to connect to the following ports: 33889,8089. Incident counter (4h, 24h, all-time): 5, 43, 289 |
2019-11-11 13:28:04 |
190.85.108.186 | attackspam | Nov 11 06:26:26 MK-Soft-Root2 sshd[23846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.108.186 Nov 11 06:26:28 MK-Soft-Root2 sshd[23846]: Failed password for invalid user guest from 190.85.108.186 port 58048 ssh2 ... |
2019-11-11 13:39:22 |
94.1.139.197 | attackspambots | Caught in portsentry honeypot |
2019-11-11 13:45:01 |
218.94.136.90 | attackspambots | 2019-11-11T05:11:14.804638shield sshd\[21726\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.94.136.90 user=root 2019-11-11T05:11:16.753484shield sshd\[21726\]: Failed password for root from 218.94.136.90 port 35420 ssh2 2019-11-11T05:15:30.887824shield sshd\[22432\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.94.136.90 user=root 2019-11-11T05:15:32.981987shield sshd\[22432\]: Failed password for root from 218.94.136.90 port 7040 ssh2 2019-11-11T05:19:43.829816shield sshd\[23065\]: Invalid user muat from 218.94.136.90 port 48064 |
2019-11-11 13:37:30 |
148.70.106.148 | attack | Nov 11 07:47:54 www sshd\[26227\]: Invalid user ching from 148.70.106.148 Nov 11 07:47:54 www sshd\[26227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.70.106.148 Nov 11 07:47:56 www sshd\[26227\]: Failed password for invalid user ching from 148.70.106.148 port 43137 ssh2 ... |
2019-11-11 14:00:05 |
114.246.11.178 | attackspambots | Nov 11 05:49:14 v22019058497090703 sshd[2575]: Failed password for root from 114.246.11.178 port 48834 ssh2 Nov 11 05:53:46 v22019058497090703 sshd[2915]: Failed password for sync from 114.246.11.178 port 58586 ssh2 ... |
2019-11-11 13:41:52 |
112.221.179.133 | attack | 2019-11-11T04:58:54.163435abusebot-8.cloudsearch.cf sshd\[23515\]: Invalid user microft from 112.221.179.133 port 58259 |
2019-11-11 13:24:18 |
106.12.209.117 | attackbotsspam | Nov 11 04:58:49 sshgateway sshd\[4574\]: Invalid user efren from 106.12.209.117 Nov 11 04:58:49 sshgateway sshd\[4574\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.209.117 Nov 11 04:58:50 sshgateway sshd\[4574\]: Failed password for invalid user efren from 106.12.209.117 port 37466 ssh2 |
2019-11-11 13:26:41 |
88.203.200.170 | attackbotsspam | Nov 11 05:58:58 MK-Soft-VM8 sshd[25910]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.203.200.170 Nov 11 05:59:00 MK-Soft-VM8 sshd[25910]: Failed password for invalid user media from 88.203.200.170 port 53498 ssh2 ... |
2019-11-11 13:18:28 |
49.206.31.144 | attack | Nov 11 06:28:37 markkoudstaal sshd[32305]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.206.31.144 Nov 11 06:28:38 markkoudstaal sshd[32305]: Failed password for invalid user josh from 49.206.31.144 port 39916 ssh2 Nov 11 06:32:54 markkoudstaal sshd[32654]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.206.31.144 |
2019-11-11 13:35:23 |
190.64.74.58 | attack | Nov 10 23:58:14 web1 postfix/smtpd[31558]: warning: unknown[190.64.74.58]: SASL LOGIN authentication failed: authentication failure ... |
2019-11-11 13:48:55 |