城市(city): unknown
省份(region): unknown
国家(country): Taiwan (Province of China)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 220.133.121.84
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16825
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;220.133.121.84. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020602 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 13:27:10 CST 2025
;; MSG SIZE rcvd: 10784.121.133.220.in-addr.arpa domain name pointer 220-133-121-84.hinet-ip.hinet.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
84.121.133.220.in-addr.arpa name = 220-133-121-84.hinet-ip.hinet.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 185.153.199.185 | attackbotsspam | Aug 10 22:19:13 [host] kernel: [2757769.623724] [U Aug 10 22:24:26 [host] kernel: [2758082.654987] [U Aug 10 22:27:58 [host] kernel: [2758294.458162] [U Aug 10 22:36:15 [host] kernel: [2758791.550905] [U Aug 10 22:37:28 [host] kernel: [2758864.681577] [U Aug 10 22:46:33 [host] kernel: [2759408.869504] [U |
2020-08-11 05:03:43 |
| 164.132.98.75 | attackspam | Aug 10 22:43:59 eventyay sshd[19821]: Failed password for root from 164.132.98.75 port 40751 ssh2 Aug 10 22:47:56 eventyay sshd[19947]: Failed password for root from 164.132.98.75 port 45687 ssh2 ... |
2020-08-11 04:59:19 |
| 167.99.170.83 | attack | Aug 10 22:25:49 PorscheCustomer sshd[8482]: Failed password for root from 167.99.170.83 port 48274 ssh2 Aug 10 22:28:51 PorscheCustomer sshd[8564]: Failed password for root from 167.99.170.83 port 47028 ssh2 ... |
2020-08-11 04:57:36 |
| 222.186.180.223 | attackbotsspam | Aug 10 23:08:27 server sshd[13775]: Failed none for root from 222.186.180.223 port 9832 ssh2 Aug 10 23:08:29 server sshd[13775]: Failed password for root from 222.186.180.223 port 9832 ssh2 Aug 10 23:08:32 server sshd[13775]: Failed password for root from 222.186.180.223 port 9832 ssh2 |
2020-08-11 05:18:46 |
| 191.6.8.142 | attackspambots | Unauthorized connection attempt from IP address 191.6.8.142 on Port 445(SMB) |
2020-08-11 05:06:59 |
| 222.124.202.179 | attackbotsspam | Unauthorized connection attempt from IP address 222.124.202.179 on Port 445(SMB) |
2020-08-11 05:11:46 |
| 37.98.170.162 | attack | Unauthorized connection attempt from IP address 37.98.170.162 on Port 445(SMB) |
2020-08-11 05:36:19 |
| 112.85.42.185 | attackbots | 2020-08-10T23:55:06.132356lavrinenko.info sshd[24210]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.185 user=root 2020-08-10T23:55:07.752567lavrinenko.info sshd[24210]: Failed password for root from 112.85.42.185 port 48560 ssh2 2020-08-10T23:55:06.132356lavrinenko.info sshd[24210]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.185 user=root 2020-08-10T23:55:07.752567lavrinenko.info sshd[24210]: Failed password for root from 112.85.42.185 port 48560 ssh2 2020-08-10T23:55:09.971288lavrinenko.info sshd[24210]: Failed password for root from 112.85.42.185 port 48560 ssh2 ... |
2020-08-11 05:07:13 |
| 213.6.67.54 | attackbotsspam | Unauthorized connection attempt from IP address 213.6.67.54 on Port 445(SMB) |
2020-08-11 05:01:18 |
| 23.95.204.95 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mcfaddenchiropractic.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-11 05:26:07 |
| 180.252.224.20 | attack | Unauthorised access (Aug 10) SRC=180.252.224.20 LEN=52 TOS=0x10 PREC=0x40 TTL=117 ID=19527 DF TCP DPT=445 WINDOW=8192 SYN |
2020-08-11 04:58:56 |
| 197.247.226.243 | attackspam | Email rejected due to spam filtering |
2020-08-11 05:27:38 |
| 51.91.158.178 | attack | 2020-08-10T20:56:23.084897shield sshd\[15881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.ip-51-91-158.eu user=root 2020-08-10T20:56:25.612938shield sshd\[15881\]: Failed password for root from 51.91.158.178 port 53200 ssh2 2020-08-10T20:58:30.539360shield sshd\[16077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.ip-51-91-158.eu user=root 2020-08-10T20:58:32.507004shield sshd\[16077\]: Failed password for root from 51.91.158.178 port 59138 ssh2 2020-08-10T21:00:38.523262shield sshd\[16257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.ip-51-91-158.eu user=root |
2020-08-11 05:10:35 |
| 196.247.168.39 | attack | Unauthorized access detected from black listed ip! |
2020-08-11 05:00:32 |
| 193.27.229.47 | attackbots | firewall-block, port(s): 62461/tcp, 62465/tcp, 62488/tcp, 62495/tcp |
2020-08-11 05:02:07 |