城市(city): unknown
省份(region): unknown
国家(country): Hong Kong
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 118.141.137.68
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23048
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;118.141.137.68. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012801 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 02:08:07 CST 2025
;; MSG SIZE rcvd: 10768.137.141.118.in-addr.arpa domain name pointer sr-68-137-141-118-on-nets.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
68.137.141.118.in-addr.arpa name = sr-68-137-141-118-on-nets.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 219.141.152.242 | attackspambots | Honeypot attack, port: 445, PTR: bj141-152-242.bjtelecom.net. |
2020-04-22 20:37:02 |
| 123.207.235.247 | attack | Apr 22 14:12:03 mail sshd[18153]: Failed password for root from 123.207.235.247 port 59970 ssh2 Apr 22 14:15:51 mail sshd[18814]: Failed password for root from 123.207.235.247 port 49670 ssh2 |
2020-04-22 20:29:36 |
| 191.102.156.130 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.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-04-22 20:42:48 |
| 112.85.42.188 | attack | 04/22/2020-08:44:19.273837 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-22 20:45:27 |
| 111.206.198.53 | attack | Bad bot/spoofed identity |
2020-04-22 20:32:52 |
| 142.4.7.212 | attack | CMS (WordPress or Joomla) login attempt. |
2020-04-22 20:44:57 |
| 59.41.119.65 | attackbots | Lines containing failures of 59.41.119.65 Apr 22 09:12:26 nextcloud sshd[10898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.41.119.65 user=r.r Apr 22 09:12:28 nextcloud sshd[10898]: Failed password for r.r from 59.41.119.65 port 61012 ssh2 Apr 22 09:12:29 nextcloud sshd[10898]: Received disconnect from 59.41.119.65 port 61012:11: Bye Bye [preauth] Apr 22 09:12:29 nextcloud sshd[10898]: Disconnected from authenticating user r.r 59.41.119.65 port 61012 [preauth] Apr 22 09:24:13 nextcloud sshd[12627]: Invalid user test from 59.41.119.65 port 60166 Apr 22 09:24:13 nextcloud sshd[12627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.41.119.65 Apr 22 09:24:16 nextcloud sshd[12627]: Failed password for invalid user test from 59.41.119.65 port 60166 ssh2 Apr 22 09:24:16 nextcloud sshd[12627]: Received disconnect from 59.41.119.65 port 60166:11: Bye Bye [preauth] Apr 22 09:24:16 nextclou........ ------------------------------ |
2020-04-22 20:35:38 |
| 103.66.232.47 | attackspam | scan r |
2020-04-22 20:46:58 |
| 113.21.123.142 | attackbotsspam | $f2bV_matches |
2020-04-22 20:43:39 |
| 37.59.100.22 | attackspam | Apr 22 09:23:07 firewall sshd[2815]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.100.22 Apr 22 09:23:07 firewall sshd[2815]: Invalid user sg from 37.59.100.22 Apr 22 09:23:10 firewall sshd[2815]: Failed password for invalid user sg from 37.59.100.22 port 42766 ssh2 ... |
2020-04-22 20:34:10 |
| 42.159.228.125 | attackbots | Apr 22 14:00:17 DAAP sshd[32106]: Invalid user mz from 42.159.228.125 port 48830 Apr 22 14:00:18 DAAP sshd[32106]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.159.228.125 Apr 22 14:00:17 DAAP sshd[32106]: Invalid user mz from 42.159.228.125 port 48830 Apr 22 14:00:19 DAAP sshd[32106]: Failed password for invalid user mz from 42.159.228.125 port 48830 ssh2 Apr 22 14:05:07 DAAP sshd[32174]: Invalid user admin from 42.159.228.125 port 45247 ... |
2020-04-22 20:23:26 |
| 81.215.210.29 | attack | trying to access non-authorized port |
2020-04-22 20:32:02 |
| 203.160.58.194 | attackspambots | Sending SPAM email |
2020-04-22 20:20:38 |
| 106.12.70.118 | attackspam | Apr 22 13:59:26 minden010 sshd[25821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.70.118 Apr 22 13:59:28 minden010 sshd[25821]: Failed password for invalid user ubuntu from 106.12.70.118 port 38988 ssh2 Apr 22 14:04:55 minden010 sshd[26798]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.70.118 ... |
2020-04-22 20:24:05 |
| 178.128.174.179 | attack | WordPress login Brute force / Web App Attack on client site. |
2020-04-22 20:16:53 |