城市(city): unknown
省份(region): unknown
国家(country): Thailand
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.207.35.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11505
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;14.207.35.105. IN A
;; AUTHORITY SECTION:
. 178 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022700 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 13:35:43 CST 2022
;; MSG SIZE rcvd: 106105.35.207.14.in-addr.arpa domain name pointer mx-ll-14.207.35-105.dynamic.3bb.in.th.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
105.35.207.14.in-addr.arpa name = mx-ll-14.207.35-105.dynamic.3bb.in.th.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 37.59.55.14 | attackspambots | Aug 15 06:32:48 jane sshd[17058]: Failed password for root from 37.59.55.14 port 43872 ssh2 ... |
2020-08-15 14:56:54 |
| 179.124.19.240 | attackbots | Attempted Brute Force (dovecot) |
2020-08-15 14:24:19 |
| 177.42.9.234 | attackbots | Aug 15 09:47:59 gw1 sshd[28705]: Failed password for root from 177.42.9.234 port 42484 ssh2 ... |
2020-08-15 14:50:09 |
| 61.177.172.102 | attackspam | 2020-08-15T09:19:16.323566snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 2020-08-15T09:19:18.844188snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 2020-08-15T09:19:21.780359snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 ... |
2020-08-15 14:22:04 |
| 95.42.74.85 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:47:18 |
| 194.180.224.103 | attackspam | Aug 15 07:58:48 vpn01 sshd[4166]: Failed password for root from 194.180.224.103 port 34786 ssh2 ... |
2020-08-15 14:21:27 |
| 85.209.0.102 | attackbots | Aug 15 08:48:03 nextcloud sshd\[17232\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.209.0.102 user=root Aug 15 08:48:04 nextcloud sshd\[17233\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.209.0.102 user=root Aug 15 08:48:05 nextcloud sshd\[17232\]: Failed password for root from 85.209.0.102 port 24298 ssh2 |
2020-08-15 14:48:45 |
| 106.13.50.145 | attackspambots | Aug 15 03:46:23 rush sshd[5269]: Failed password for root from 106.13.50.145 port 55444 ssh2 Aug 15 03:50:55 rush sshd[5420]: Failed password for root from 106.13.50.145 port 53658 ssh2 ... |
2020-08-15 14:46:43 |
| 222.186.175.216 | attackspam | 2020-08-15T06:32:00.388063server.espacesoutien.com sshd[14054]: Failed password for root from 222.186.175.216 port 4494 ssh2 2020-08-15T06:32:03.534586server.espacesoutien.com sshd[14054]: Failed password for root from 222.186.175.216 port 4494 ssh2 2020-08-15T06:32:07.091563server.espacesoutien.com sshd[14054]: Failed password for root from 222.186.175.216 port 4494 ssh2 2020-08-15T06:32:10.862993server.espacesoutien.com sshd[14054]: Failed password for root from 222.186.175.216 port 4494 ssh2 ... |
2020-08-15 14:32:25 |
| 23.95.224.43 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found decubellisfamilychiropractic.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 |
2020-08-15 14:25:42 |
| 170.239.85.39 | attack | Lines containing failures of 170.239.85.39 Aug 13 05:10:30 shared03 sshd[1546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.85.39 user=r.r Aug 13 05:10:33 shared03 sshd[1546]: Failed password for r.r from 170.239.85.39 port 53174 ssh2 Aug 13 05:10:33 shared03 sshd[1546]: Received disconnect from 170.239.85.39 port 53174:11: Bye Bye [preauth] Aug 13 05:10:33 shared03 sshd[1546]: Disconnected from authenticating user r.r 170.239.85.39 port 53174 [preauth] Aug 13 05:13:09 shared03 sshd[2277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.85.39 user=r.r Aug 13 05:13:11 shared03 sshd[2277]: Failed password for r.r from 170.239.85.39 port 55778 ssh2 Aug 13 05:13:12 shared03 sshd[2277]: Received disconnect from 170.239.85.39 port 55778:11 .... truncated .... Lines containing failures of 170.239.85.39 Aug 13 05:10:30 shared03 sshd[1546]: pam_unix(sshd:auth): authentication fa........ ------------------------------ |
2020-08-15 14:37:12 |
| 94.102.49.190 | attackbots | Fail2Ban Ban Triggered |
2020-08-15 14:49:43 |
| 106.12.209.117 | attackspam | Aug 15 06:30:56 *** sshd[26051]: User root from 106.12.209.117 not allowed because not listed in AllowUsers |
2020-08-15 14:39:15 |
| 129.211.146.50 | attack | frenzy |
2020-08-15 14:41:26 |
| 93.174.89.55 | attackspambots | Port scanning [4 denied] |
2020-08-15 14:52:14 |