城市(city): Johannesburg
省份(region): Gauteng
国家(country): South Africa
运营商(isp): Vodacom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 105.245.42.41
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22903
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;105.245.42.41. IN A
;; AUTHORITY SECTION:
. 162 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052202 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 23 12:39:41 CST 2024
;; MSG SIZE rcvd: 10641.42.245.105.in-addr.arpa domain name pointer vc-gp-n-105-245-42-41.umts.vodacom.co.za.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
41.42.245.105.in-addr.arpa name = vc-gp-n-105-245-42-41.umts.vodacom.co.za.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 93.144.211.134 | attack | SSH login attempts. |
2020-09-07 23:56:08 |
| 194.36.174.121 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-08 00:04:59 |
| 138.255.0.27 | attackbotsspam | Sep 7 12:42:20 nextcloud sshd\[12804\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.255.0.27 user=root Sep 7 12:42:22 nextcloud sshd\[12804\]: Failed password for root from 138.255.0.27 port 36380 ssh2 Sep 7 12:46:31 nextcloud sshd\[13520\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.255.0.27 user=root |
2020-09-08 00:05:29 |
| 159.203.219.38 | attackspambots | 20 attempts against mh-ssh on cloud |
2020-09-08 00:00:05 |
| 121.101.132.241 | attackbotsspam | 121.101.132.241 (ID/Indonesia/-), 7 distributed sshd attacks on account [root] in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_DISTATTACK; Logs: Sep 7 04:48:04 server5 sshd[11120]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.101.132.241 user=root Sep 7 04:48:06 server5 sshd[11120]: Failed password for root from 121.101.132.241 port 37126 ssh2 Sep 7 04:44:46 server5 sshd[9535]: Failed password for root from 123.22.212.99 port 39453 ssh2 Sep 7 04:44:44 server5 sshd[9535]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.22.212.99 user=root Sep 7 04:49:43 server5 sshd[11960]: Failed password for root from 123.58.109.42 port 35832 ssh2 Sep 7 04:49:41 server5 sshd[11960]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.58.109.42 user=root Sep 7 04:50:01 server5 sshd[11974]: Failed password for root from 210.71.232.236 port 53620 ssh2 IP Addresses Blocked: |
2020-09-08 00:18:54 |
| 123.241.211.103 | attackspambots | DATE:2020-09-06 18:50:55, IP:123.241.211.103, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc) |
2020-09-08 00:13:26 |
| 203.158.177.149 | attack | Sep 7 17:25:35 buvik sshd[11692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.158.177.149 user=root Sep 7 17:25:37 buvik sshd[11692]: Failed password for root from 203.158.177.149 port 52862 ssh2 Sep 7 17:27:17 buvik sshd[11904]: Invalid user aruncs from 203.158.177.149 ... |
2020-09-07 23:46:31 |
| 23.108.46.43 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drmichaeltwalsh.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software tha |
2020-09-07 23:42:31 |
| 49.234.56.138 | attackbots | Sep 5 17:53:56 woof sshd[13292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138 user=r.r Sep 5 17:53:58 woof sshd[13292]: Failed password for r.r from 49.234.56.138 port 50218 ssh2 Sep 5 17:53:58 woof sshd[13292]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth] Sep 5 18:02:13 woof sshd[13854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138 user=r.r Sep 5 18:02:15 woof sshd[13854]: Failed password for r.r from 49.234.56.138 port 35694 ssh2 Sep 5 18:02:16 woof sshd[13854]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.234.56.138 |
2020-09-07 23:46:15 |
| 192.3.15.162 | attackbots | Sep 7 07:21:13 markkoudstaal sshd[15037]: Failed password for root from 192.3.15.162 port 48076 ssh2 Sep 7 07:21:22 markkoudstaal sshd[15083]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.15.162 Sep 7 07:21:25 markkoudstaal sshd[15083]: Failed password for invalid user oracle from 192.3.15.162 port 54418 ssh2 ... |
2020-09-07 23:50:41 |
| 89.33.192.200 | attack | Sep 7 10:37:22 rancher-0 sshd[1478203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.33.192.200 user=root Sep 7 10:37:24 rancher-0 sshd[1478203]: Failed password for root from 89.33.192.200 port 44144 ssh2 ... |
2020-09-07 23:57:23 |
| 5.188.206.194 | attackbots | Sep 7 17:49:14 relay postfix/smtpd\[6975\]: warning: unknown\[5.188.206.194\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 17:49:36 relay postfix/smtpd\[9762\]: warning: unknown\[5.188.206.194\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 17:58:10 relay postfix/smtpd\[13710\]: warning: unknown\[5.188.206.194\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 17:58:31 relay postfix/smtpd\[9829\]: warning: unknown\[5.188.206.194\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 7 18:01:52 relay postfix/smtpd\[10407\]: warning: unknown\[5.188.206.194\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-09-08 00:03:05 |
| 138.197.135.102 | attackbots | CMS (WordPress or Joomla) login attempt. |
2020-09-08 00:12:36 |
| 106.12.45.32 | attackbotsspam | firewall-block, port(s): 2167/tcp |
2020-09-08 00:16:42 |
| 185.158.142.144 | attackbots | Honeypot attack, port: 445, PTR: 144-142-158-185.wifi4all.it. |
2020-09-08 00:27:50 |