城市(city): Kimhae
省份(region): Gyeongsangnam-do
国家(country): South Korea
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 169.212.17.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20440
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;169.212.17.212. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022000 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 18:55:16 CST 2025
;; MSG SIZE rcvd: 107Host 212.17.212.169.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 212.17.212.169.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 31.133.72.25 | attackspam | Unauthorized connection attempt from IP address 31.133.72.25 on Port 445(SMB) |
2020-08-27 22:04:07 |
| 195.206.38.5 | attackspam | Unauthorized connection attempt from IP address 195.206.38.5 on Port 445(SMB) |
2020-08-27 22:31:31 |
| 113.176.195.85 | attackspam | Unauthorized connection attempt from IP address 113.176.195.85 on Port 445(SMB) |
2020-08-27 21:57:21 |
| 104.140.184.109 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mtjulietchiropractic.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 softwar |
2020-08-27 22:25:53 |
| 140.86.12.31 | attackbotsspam | Aug 27 15:42:34 rotator sshd\[2006\]: Invalid user git from 140.86.12.31Aug 27 15:42:35 rotator sshd\[2006\]: Failed password for invalid user git from 140.86.12.31 port 34261 ssh2Aug 27 15:46:52 rotator sshd\[2813\]: Invalid user g from 140.86.12.31Aug 27 15:46:54 rotator sshd\[2813\]: Failed password for invalid user g from 140.86.12.31 port 9249 ssh2Aug 27 15:51:03 rotator sshd\[3607\]: Invalid user upload from 140.86.12.31Aug 27 15:51:05 rotator sshd\[3607\]: Failed password for invalid user upload from 140.86.12.31 port 40711 ssh2 ... |
2020-08-27 22:00:37 |
| 149.202.130.96 | attack | Aug 27 20:38:02 webhost01 sshd[11265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.202.130.96 Aug 27 20:38:04 webhost01 sshd[11265]: Failed password for invalid user postgres from 149.202.130.96 port 55698 ssh2 ... |
2020-08-27 22:02:24 |
| 218.92.0.224 | attackspambots | Aug 27 15:15:58 ns308116 sshd[22729]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.224 user=root Aug 27 15:16:00 ns308116 sshd[22729]: Failed password for root from 218.92.0.224 port 33933 ssh2 Aug 27 15:16:04 ns308116 sshd[22729]: Failed password for root from 218.92.0.224 port 33933 ssh2 Aug 27 15:16:07 ns308116 sshd[22729]: Failed password for root from 218.92.0.224 port 33933 ssh2 Aug 27 15:16:11 ns308116 sshd[22729]: Failed password for root from 218.92.0.224 port 33933 ssh2 ... |
2020-08-27 22:25:19 |
| 91.231.42.248 | attack | 1598533348 - 08/27/2020 15:02:28 Host: 91.231.42.248/91.231.42.248 Port: 445 TCP Blocked |
2020-08-27 21:58:57 |
| 40.79.25.254 | attack | Aug 27 14:24:55 game-panel sshd[7447]: Failed password for root from 40.79.25.254 port 47288 ssh2 Aug 27 14:30:53 game-panel sshd[7877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.79.25.254 Aug 27 14:30:55 game-panel sshd[7877]: Failed password for invalid user sentry from 40.79.25.254 port 55508 ssh2 |
2020-08-27 22:38:23 |
| 103.96.15.4 | attackspambots | 20/8/27@09:01:55: FAIL: Alarm-Network address from=103.96.15.4 20/8/27@09:01:55: FAIL: Alarm-Network address from=103.96.15.4 ... |
2020-08-27 22:33:25 |
| 173.234.151.125 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mtjulietchiropractic.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 softwar |
2020-08-27 22:36:49 |
| 68.183.12.80 | attackbotsspam | 2020-08-27T13:13:43.749471shield sshd\[15891\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.12.80 user=root 2020-08-27T13:13:45.630619shield sshd\[15891\]: Failed password for root from 68.183.12.80 port 59830 ssh2 2020-08-27T13:17:36.003052shield sshd\[16229\]: Invalid user lois from 68.183.12.80 port 39862 2020-08-27T13:17:36.015149shield sshd\[16229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.12.80 2020-08-27T13:17:38.221536shield sshd\[16229\]: Failed password for invalid user lois from 68.183.12.80 port 39862 ssh2 |
2020-08-27 22:20:43 |
| 46.101.11.213 | attackbots | Aug 27 16:48:44 journals sshd\[111378\]: Invalid user ax from 46.101.11.213 Aug 27 16:48:44 journals sshd\[111378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.11.213 Aug 27 16:48:46 journals sshd\[111378\]: Failed password for invalid user ax from 46.101.11.213 port 47372 ssh2 Aug 27 16:52:58 journals sshd\[112134\]: Invalid user lizhen from 46.101.11.213 Aug 27 16:52:58 journals sshd\[112134\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.11.213 ... |
2020-08-27 22:01:06 |
| 49.235.204.59 | attackbotsspam | Aug 27 21:08:16 webhost01 sshd[11694]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.204.59 Aug 27 21:08:18 webhost01 sshd[11694]: Failed password for invalid user king from 49.235.204.59 port 33214 ssh2 ... |
2020-08-27 22:09:27 |
| 218.92.0.247 | attack | Aug 27 15:47:11 vps1 sshd[16933]: Failed none for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:11 vps1 sshd[16933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.247 user=root Aug 27 15:47:13 vps1 sshd[16933]: Failed password for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:19 vps1 sshd[16933]: Failed password for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:24 vps1 sshd[16933]: Failed password for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:29 vps1 sshd[16933]: Failed password for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:33 vps1 sshd[16933]: Failed password for invalid user root from 218.92.0.247 port 24484 ssh2 Aug 27 15:47:35 vps1 sshd[16933]: error: maximum authentication attempts exceeded for invalid user root from 218.92.0.247 port 24484 ssh2 [preauth] ... |
2020-08-27 21:57:39 |