City: unknown
Region: unknown
Country: South Africa
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 105.213.173.58
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15573
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;105.213.173.58. IN A
;; AUTHORITY SECTION:
. 311 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022701 1800 900 604800 86400
;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 14:17:55 CST 2022
;; MSG SIZE rcvd: 107
58.173.213.105.in-addr.arpa domain name pointer 105-213-173-58.access.mtnbusiness.co.za.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
58.173.213.105.in-addr.arpa name = 105-213-173-58.access.mtnbusiness.co.za.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
101.4.130.249 | attackbots | Feb 12 17:15:07 lnxded64 sshd[28276]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.4.130.249 |
2020-02-13 04:23:31 |
217.165.219.7 | attackbotsspam | 20/2/12@08:40:34: FAIL: Alarm-Network address from=217.165.219.7 ... |
2020-02-13 04:28:33 |
91.232.96.101 | attack | Feb 12 14:40:09 grey postfix/smtpd\[12383\]: NOQUEUE: reject: RCPT from rebel.kumsoft.com\[91.232.96.101\]: 554 5.7.1 Service unavailable\; Client host \[91.232.96.101\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[91.232.96.101\]\; from=\ |
2020-02-13 04:55:58 |
94.177.214.200 | attackspam | 2020-02-12T20:14:10.102744homeassistant sshd[24663]: Invalid user applications from 94.177.214.200 port 38570 2020-02-12T20:14:10.109451homeassistant sshd[24663]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.214.200 ... |
2020-02-13 04:57:28 |
192.160.102.166 | attack | 02/12/2020-14:40:41.812285 192.160.102.166 Protocol: 6 ET TOR Known Tor Exit Node Traffic group 38 |
2020-02-13 04:22:44 |
178.205.150.6 | attackspambots | Attempt to attack host OS, exploiting network vulnerabilities, on 12-02-2020 13:40:15. |
2020-02-13 04:47:13 |
220.132.82.203 | attack | 23/tcp 23/tcp 23/tcp [2020-02-01/12]3pkt |
2020-02-13 04:24:38 |
65.49.20.99 | attackbots | 443/udp 22/tcp... [2019-12-18/2020-02-12]5pkt,1pt.(tcp),1pt.(udp) |
2020-02-13 04:39:36 |
171.246.63.22 | attackbots | 20/2/12@15:01:06: FAIL: IoT-Telnet address from=171.246.63.22 ... |
2020-02-13 04:50:33 |
112.85.42.227 | attackspambots | Feb 12 15:00:18 NPSTNNYC01T sshd[26448]: Failed password for root from 112.85.42.227 port 23848 ssh2 Feb 12 15:01:23 NPSTNNYC01T sshd[26475]: Failed password for root from 112.85.42.227 port 23818 ssh2 ... |
2020-02-13 04:18:06 |
94.153.235.114 | attackbots | Attempt to attack host OS, exploiting network vulnerabilities, on 12-02-2020 13:40:29. |
2020-02-13 04:35:16 |
118.179.112.169 | attackspam | Feb 12 13:40:34 work-partkepr sshd\[26283\]: Invalid user 666666 from 118.179.112.169 port 58675 Feb 12 13:40:34 work-partkepr sshd\[26283\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.179.112.169 ... |
2020-02-13 04:34:31 |
43.225.23.18 | attack | 445/tcp 445/tcp 445/tcp... [2019-12-28/2020-02-12]4pkt,1pt.(tcp) |
2020-02-13 04:14:10 |
197.248.38.174 | attackspam | Unauthorized connection attempt detected from IP address 197.248.38.174 to port 445 |
2020-02-13 04:38:34 |
190.66.3.92 | attackspam | Feb 12 17:50:02 vlre-nyc-1 sshd\[897\]: Invalid user ishimaki from 190.66.3.92 Feb 12 17:50:02 vlre-nyc-1 sshd\[897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.66.3.92 Feb 12 17:50:04 vlre-nyc-1 sshd\[897\]: Failed password for invalid user ishimaki from 190.66.3.92 port 43682 ssh2 Feb 12 17:52:34 vlre-nyc-1 sshd\[939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.66.3.92 user=root Feb 12 17:52:36 vlre-nyc-1 sshd\[939\]: Failed password for root from 190.66.3.92 port 36050 ssh2 ... |
2020-02-13 04:33:53 |