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 <<>> 44.214.140.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5966
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;44.214.140.48. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022701 1800 900 604800 86400
;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 03:00:11 CST 2025
;; MSG SIZE rcvd: 106
48.140.214.44.in-addr.arpa domain name pointer ec2-44-214-140-48.compute-1.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
48.140.214.44.in-addr.arpa name = ec2-44-214-140-48.compute-1.amazonaws.com.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 222.186.15.10 | attackspam | $f2bV_matches |
2020-02-22 20:51:57 |
| 104.244.78.197 | attackspambots | suspicious action Sat, 22 Feb 2020 10:14:00 -0300 |
2020-02-22 21:28:09 |
| 145.239.82.11 | attackbots | Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266 Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266 Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 Feb 22 14:13:58 tuxlinux sshd[17063]: Invalid user q3 from 145.239.82.11 port 40266 Feb 22 14:13:58 tuxlinux sshd[17063]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.82.11 Feb 22 14:13:59 tuxlinux sshd[17063]: Failed password for invalid user q3 from 145.239.82.11 port 40266 ssh2 ... |
2020-02-22 21:27:52 |
| 3.0.120.96 | attackbotsspam | xmlrpc attack |
2020-02-22 20:53:22 |
| 24.95.181.4 | attackbotsspam | Brute-force attempt banned |
2020-02-22 20:54:08 |
| 104.203.153.141 | attack | Invalid user developer from 104.203.153.141 port 54580 |
2020-02-22 21:07:30 |
| 136.232.243.134 | attack | SSH Brute Force |
2020-02-22 20:58:22 |
| 92.63.194.7 | attack | Invalid user admin from 92.63.194.7 port 47662 |
2020-02-22 21:10:00 |
| 37.114.158.193 | attackbots | SSH Brute Force |
2020-02-22 21:02:58 |
| 51.77.195.1 | attackspambots | Failed password for invalid user takamatsu from 51.77.195.1 port 40168 ssh2 Invalid user activiti from 51.77.195.1 port 60306 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.195.1 Failed password for invalid user activiti from 51.77.195.1 port 60306 ssh2 Invalid user remote from 51.77.195.1 port 52212 |
2020-02-22 21:11:23 |
| 196.28.101.137 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic |
2020-02-22 21:15:56 |
| 129.204.188.93 | attack | SSH Brute-Force attacks |
2020-02-22 20:58:42 |
| 106.13.47.10 | attackspambots | Feb 22 09:41:45 firewall sshd[22177]: Invalid user share from 106.13.47.10 Feb 22 09:41:47 firewall sshd[22177]: Failed password for invalid user share from 106.13.47.10 port 34832 ssh2 Feb 22 09:45:49 firewall sshd[22318]: Invalid user robert from 106.13.47.10 ... |
2020-02-22 20:53:39 |
| 175.141.245.35 | attackbotsspam | Automatic report - SSH Brute-Force Attack |
2020-02-22 21:25:27 |
| 123.140.114.252 | attackspambots | Invalid user web from 123.140.114.252 port 56702 |
2020-02-22 20:59:13 |