城市(city): unknown
省份(region): unknown
国家(country): Netherlands
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 82.75.149.209
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30566
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;82.75.149.209. IN A
;; AUTHORITY SECTION:
. 367 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022012801 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 29 05:46:50 CST 2022
;; MSG SIZE rcvd: 106209.149.75.82.in-addr.arpa domain name pointer 82-75-149-209.cable.dynamic.v4.ziggo.nl.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
209.149.75.82.in-addr.arpa name = 82-75-149-209.cable.dynamic.v4.ziggo.nl.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 94.23.24.213 | attack | Apr 22 09:16:57 dns1 sshd[5784]: Failed password for root from 94.23.24.213 port 44290 ssh2 Apr 22 09:19:07 dns1 sshd[5984]: Failed password for root from 94.23.24.213 port 52152 ssh2 |
2020-04-22 20:31:37 |
| 81.51.156.171 | attack | Apr 22 12:19:54 localhost sshd\[28128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171 user=root Apr 22 12:19:56 localhost sshd\[28128\]: Failed password for root from 81.51.156.171 port 39386 ssh2 Apr 22 12:33:41 localhost sshd\[28477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171 user=root ... |
2020-04-22 20:59:22 |
| 69.203.144.38 | attackspam | Honeypot attack, port: 5555, PTR: cpe-69-203-144-38.nyc.res.rr.com. |
2020-04-22 20:34:44 |
| 173.44.164.14 | attack | (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:51:52 |
| 219.141.152.242 | attackspambots | Honeypot attack, port: 445, PTR: bj141-152-242.bjtelecom.net. |
2020-04-22 20:37:02 |
| 222.139.245.70 | attack | Apr 22 12:04:22 ws26vmsma01 sshd[115003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.139.245.70 Apr 22 12:04:24 ws26vmsma01 sshd[115003]: Failed password for invalid user deploy from 222.139.245.70 port 52769 ssh2 ... |
2020-04-22 20:58:32 |
| 95.155.36.152 | attackbots | Honeypot attack, port: 445, PTR: adsl-bb36-l152.crnagora.net. |
2020-04-22 20:30:08 |
| 172.245.193.245 | 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:46:06 |
| 185.50.149.5 | attackspam | Apr 22 13:59:40 srv01 postfix/smtpd\[26967\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 22 13:59:59 srv01 postfix/smtpd\[25172\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 22 14:07:59 srv01 postfix/smtpd\[6444\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 22 14:08:16 srv01 postfix/smtpd\[26967\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Apr 22 14:10:18 srv01 postfix/smtpd\[4803\]: warning: unknown\[185.50.149.5\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-04-22 20:41:36 |
| 150.109.147.145 | attackbots | Apr 22 04:59:18 mockhub sshd[9459]: Failed password for root from 150.109.147.145 port 49868 ssh2 Apr 22 05:04:59 mockhub sshd[9645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.147.145 ... |
2020-04-22 20:29:49 |
| 176.114.199.56 | attackspam | 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:00.8631781495-001 sshd[31606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:02.7832631495-001 sshd[31606]: Failed password for invalid user qd from 176.114.199.56 port 41434 ssh2 2020-04-22T08:05:12.3687021495-001 sshd[31838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 user=root 2020-04-22T08:05:14.2199191495-001 sshd[31838]: Failed password for root from 176.114.199.56 port 55034 ssh2 ... |
2020-04-22 20:28:28 |
| 222.186.31.83 | attackspambots | Apr 22 14:30:11 vmd38886 sshd\[31302\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83 user=root Apr 22 14:30:13 vmd38886 sshd\[31302\]: Failed password for root from 222.186.31.83 port 16436 ssh2 Apr 22 14:30:15 vmd38886 sshd\[31302\]: Failed password for root from 222.186.31.83 port 16436 ssh2 |
2020-04-22 20:42:21 |
| 113.21.123.142 | attackbotsspam | $f2bV_matches |
2020-04-22 20:43:39 |
| 219.137.92.89 | attack | Apr 22 11:08:47 vz239 sshd[6579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.137.92.89 user=r.r Apr 22 11:08:49 vz239 sshd[6579]: Failed password for r.r from 219.137.92.89 port 45640 ssh2 Apr 22 11:08:50 vz239 sshd[6579]: Received disconnect from 219.137.92.89: 11: Bye Bye [preauth] Apr 22 12:07:32 vz239 sshd[32408]: Invalid user gg from 219.137.92.89 Apr 22 12:07:32 vz239 sshd[32408]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.137.92.89 Apr 22 12:07:33 vz239 sshd[32408]: Failed password for invalid user gg from 219.137.92.89 port 43315 ssh2 Apr 22 12:07:34 vz239 sshd[32408]: Received disconnect from 219.137.92.89: 11: Bye Bye [preauth] Apr 22 12:11:17 vz239 sshd[32465]: Invalid user lq from 219.137.92.89 Apr 22 12:11:17 vz239 sshd[32465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.137.92.89 Apr 22 12:11:19 vz239 sshd[324........ ------------------------------- |
2020-04-22 20:49:04 |
| 186.149.46.4 | attackspam | Apr 22 08:41:47 NPSTNNYC01T sshd[10253]: Failed password for root from 186.149.46.4 port 9990 ssh2 Apr 22 08:46:31 NPSTNNYC01T sshd[10634]: Failed password for root from 186.149.46.4 port 16166 ssh2 ... |
2020-04-22 21:08:28 |