城市(city): Los Angeles
省份(region): California
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 148.107.253.214
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29413
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;148.107.253.214. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025032501 1800 900 604800 86400
;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 26 05:08:17 CST 2025
;; MSG SIZE rcvd: 108Host 214.253.107.148.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 214.253.107.148.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 110.139.171.171 | attack | Unauthorized connection attempt from IP address 110.139.171.171 on Port 445(SMB) |
2020-03-18 19:04:51 |
| 103.72.162.44 | attack | Brute-force attempt banned |
2020-03-18 19:17:24 |
| 82.200.168.92 | attackspam | Brute-force attempt banned |
2020-03-18 19:09:55 |
| 192.3.143.60 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found savannahhillsfamilychiropractic.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 |
2020-03-18 18:58:41 |
| 73.186.43.46 | attackbotsspam | Chat Spam |
2020-03-18 18:51:29 |
| 41.38.121.79 | attackbotsspam | Unauthorized connection attempt detected from IP address 41.38.121.79 to port 445 |
2020-03-18 19:03:57 |
| 117.48.227.43 | attackspam | Mar 18 03:49:49 mail sshd\[48407\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.48.227.43 user=root ... |
2020-03-18 18:40:13 |
| 218.92.0.208 | attackbots | Mar 18 11:09:46 IngegnereFirenze sshd[7652]: User root from 218.92.0.208 not allowed because not listed in AllowUsers ... |
2020-03-18 19:18:58 |
| 131.255.227.166 | attackspam | Mar 18 10:34:10 |
2020-03-18 19:00:12 |
| 49.233.92.166 | attackbots | $f2bV_matches |
2020-03-18 18:46:42 |
| 183.107.196.132 | attack | Mar 18 01:08:09 mockhub sshd[10120]: Failed password for root from 183.107.196.132 port 42157 ssh2 ... |
2020-03-18 19:00:41 |
| 46.101.17.215 | attackbotsspam | $f2bV_matches |
2020-03-18 19:15:12 |
| 39.106.190.42 | attackspambots | firewall-block, port(s): 1433/tcp, 6380/tcp, 7001/tcp, 7002/tcp, 9200/tcp |
2020-03-18 19:15:42 |
| 187.188.90.141 | attack | Mar 18 17:33:17 webhost01 sshd[3725]: Failed password for root from 187.188.90.141 port 60122 ssh2 ... |
2020-03-18 18:40:35 |
| 81.145.158.178 | attack | Mar 17 23:59:38 web9 sshd\[1662\]: Invalid user arma from 81.145.158.178 Mar 17 23:59:38 web9 sshd\[1662\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.145.158.178 Mar 17 23:59:40 web9 sshd\[1662\]: Failed password for invalid user arma from 81.145.158.178 port 37932 ssh2 Mar 18 00:07:32 web9 sshd\[2934\]: Invalid user server from 81.145.158.178 Mar 18 00:07:32 web9 sshd\[2934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.145.158.178 |
2020-03-18 18:39:28 |