城市(city): Johannesburg
省份(region): Gauteng
国家(country): South Africa
运营商(isp): MTN
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 105.213.127.166
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44168
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;105.213.127.166. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022033000 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 30 14:41:00 CST 2022
;; MSG SIZE rcvd: 108
166.127.213.105.in-addr.arpa domain name pointer 105-213-127-166.access.mtnbusiness.co.za.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
166.127.213.105.in-addr.arpa name = 105-213-127-166.access.mtnbusiness.co.za.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 36.90.63.130 | attackspambots | 1597463488 - 08/15/2020 05:51:28 Host: 36.90.63.130/36.90.63.130 Port: 445 TCP Blocked |
2020-08-15 17:59:09 |
| 45.72.61.23 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found norburgchiro.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 that c |
2020-08-15 17:50:04 |
| 103.219.112.47 | attackspambots | 2020-08-15T15:19:30.077827hostname sshd[87400]: Failed password for root from 103.219.112.47 port 56496 ssh2 2020-08-15T15:23:59.333795hostname sshd[87852]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.47 user=root 2020-08-15T15:24:01.448277hostname sshd[87852]: Failed password for root from 103.219.112.47 port 37592 ssh2 ... |
2020-08-15 17:50:35 |
| 157.230.53.57 | attackbots | TCP ports : 9167 / 28640 |
2020-08-15 18:29:26 |
| 219.138.153.114 | attack | Lines containing failures of 219.138.153.114 (max 1000) Aug 12 04:55:35 localhost sshd[21066]: User r.r from 219.138.153.114 not allowed because listed in DenyUsers Aug 12 04:55:35 localhost sshd[21066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.138.153.114 user=r.r Aug 12 04:55:37 localhost sshd[21066]: Failed password for invalid user r.r from 219.138.153.114 port 36916 ssh2 Aug 12 04:55:39 localhost sshd[21066]: Received disconnect from 219.138.153.114 port 36916:11: Bye Bye [preauth] Aug 12 04:55:39 localhost sshd[21066]: Disconnected from invalid user r.r 219.138.153.114 port 36916 [preauth] Aug 12 05:15:20 localhost sshd[25771]: User r.r from 219.138.153.114 not allowed because listed in DenyUsers Aug 12 05:15:20 localhost sshd[25771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.138.153.114 user=r.r Aug 12 05:15:22 localhost sshd[25771]: Failed password for invalid u........ ------------------------------ |
2020-08-15 18:27:35 |
| 45.124.144.116 | attackbotsspam | SSH Bruteforce attack |
2020-08-15 18:15:08 |
| 35.196.37.206 | attackspambots | 35.196.37.206 - - \[15/Aug/2020:10:25:20 +0200\] "POST /wp-login.php HTTP/1.1" 200 12822 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 35.196.37.206 - - \[15/Aug/2020:10:25:22 +0200\] "POST /wp-login.php HTTP/1.1" 200 12657 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" ... |
2020-08-15 18:04:22 |
| 42.236.10.121 | attackbotsspam | Automatic report - Banned IP Access |
2020-08-15 17:57:40 |
| 192.241.239.189 | attack | [Thu Aug 06 03:49:30 2020] - DDoS Attack From IP: 192.241.239.189 Port: 54114 |
2020-08-15 17:59:33 |
| 218.92.0.250 | attackbotsspam | Aug 15 13:16:42 ift sshd\[41138\]: Failed password for root from 218.92.0.250 port 2591 ssh2Aug 15 13:16:46 ift sshd\[41138\]: Failed password for root from 218.92.0.250 port 2591 ssh2Aug 15 13:16:49 ift sshd\[41138\]: Failed password for root from 218.92.0.250 port 2591 ssh2Aug 15 13:16:52 ift sshd\[41138\]: Failed password for root from 218.92.0.250 port 2591 ssh2Aug 15 13:16:55 ift sshd\[41138\]: Failed password for root from 218.92.0.250 port 2591 ssh2 ... |
2020-08-15 18:17:43 |
| 101.69.200.162 | attackbotsspam | Aug 15 11:44:36 vpn01 sshd[7782]: Failed password for root from 101.69.200.162 port 29292 ssh2 ... |
2020-08-15 18:16:03 |
| 222.153.54.40 | attackspam | REQUESTED PAGE: /wp-json/contact-form-7/v1/contact-forms/4/feedback |
2020-08-15 18:19:56 |
| 147.135.169.185 | attackspambots | 2020-08-15 04:42:55.315570-0500 localhost sshd[52422]: Failed password for root from 147.135.169.185 port 41770 ssh2 |
2020-08-15 17:54:34 |
| 157.48.157.160 | attackbotsspam | IP 157.48.157.160 attacked honeypot on port: 8080 at 8/14/2020 8:50:28 PM |
2020-08-15 18:02:29 |
| 85.209.0.131 | attackspambots |
|
2020-08-15 18:21:12 |