City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 135.213.5.173
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34934
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;135.213.5.173. IN A
;; AUTHORITY SECTION:
. 278 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022011000 1800 900 604800 86400
;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 10 17:20:08 CST 2022
;; MSG SIZE rcvd: 106173.5.213.135.in-addr.arpa domain name pointer nothing.attdns.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
173.5.213.135.in-addr.arpa name = nothing.attdns.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 134.122.85.244 | attack | Scanned 1 times in the last 24 hours on port 5060 |
2020-04-11 08:08:35 |
| 91.134.235.254 | attackbots | Apr 10 18:10:36 server1 sshd\[27436\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.235.254 user=root Apr 10 18:10:38 server1 sshd\[27436\]: Failed password for root from 91.134.235.254 port 43090 ssh2 Apr 10 18:14:08 server1 sshd\[28526\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.235.254 user=root Apr 10 18:14:10 server1 sshd\[28526\]: Failed password for root from 91.134.235.254 port 51000 ssh2 Apr 10 18:17:41 server1 sshd\[29421\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.134.235.254 user=root ... |
2020-04-11 08:17:48 |
| 157.230.249.90 | attack | Apr 10 23:48:35 NPSTNNYC01T sshd[4657]: Failed password for root from 157.230.249.90 port 55464 ssh2 Apr 10 23:52:37 NPSTNNYC01T sshd[4994]: Failed password for root from 157.230.249.90 port 34936 ssh2 Apr 10 23:56:34 NPSTNNYC01T sshd[5428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.249.90 ... |
2020-04-11 12:01:01 |
| 139.99.34.219 | attack | 22/tcp 22/tcp 22/tcp [2020-03-27/04-10]3pkt |
2020-04-11 08:08:19 |
| 141.98.81.150 | attackspam | ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak |
2020-04-11 08:07:57 |
| 51.68.32.21 | attackbotsspam | ET CINS Active Threat Intelligence Poor Reputation IP group 37 - port: 23 proto: TCP cat: Misc Attack |
2020-04-11 08:32:22 |
| 80.82.77.139 | attack | Fail2Ban Ban Triggered |
2020-04-11 08:22:13 |
| 60.170.180.96 | attackbotsspam | ET CINS Active Threat Intelligence Poor Reputation IP group 46 - port: 23 proto: TCP cat: Misc Attack |
2020-04-11 08:29:18 |
| 107.173.178.131 | attack | none |
2020-04-11 12:00:44 |
| 77.247.109.241 | attack | Scanned 2 times in the last 24 hours on port 5060 |
2020-04-11 08:24:17 |
| 78.29.9.120 | attackspam | ET CINS Active Threat Intelligence Poor Reputation IP group 65 - port: 1433 proto: TCP cat: Misc Attack |
2020-04-11 08:24:02 |
| 106.18.137.11 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic |
2020-04-11 08:10:33 |
| 111.223.49.134 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic |
2020-04-11 08:09:52 |
| 58.217.103.57 | attack | ET CINS Active Threat Intelligence Poor Reputation IP group 40 - port: 1433 proto: TCP cat: Misc Attack |
2020-04-11 08:29:40 |
| 89.248.160.150 | attackspam | 89.248.160.150 was recorded 26 times by 12 hosts attempting to connect to the following ports: 7775,7771,7582. Incident counter (4h, 24h, all-time): 26, 138, 10714 |
2020-04-11 08:18:54 |