城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 70.195.254.237
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3212
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;70.195.254.237. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 09:51:23 CST 2025
;; MSG SIZE rcvd: 107237.254.195.70.in-addr.arpa domain name pointer 237.sub-70-195-254.myvzw.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
237.254.195.70.in-addr.arpa name = 237.sub-70-195-254.myvzw.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 62.234.20.135 | attack | Sep 6 07:57:36 ns382633 sshd\[18769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root Sep 6 07:57:38 ns382633 sshd\[18769\]: Failed password for root from 62.234.20.135 port 36218 ssh2 Sep 6 07:59:38 ns382633 sshd\[18983\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root Sep 6 07:59:41 ns382633 sshd\[18983\]: Failed password for root from 62.234.20.135 port 55252 ssh2 Sep 6 08:00:40 ns382633 sshd\[19521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root |
2020-09-06 15:19:08 |
| 49.88.112.72 | attack | Sep 6 12:21:09 mx sshd[582441]: Failed password for root from 49.88.112.72 port 26984 ssh2 Sep 6 12:22:00 mx sshd[582446]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.72 user=root Sep 6 12:22:02 mx sshd[582446]: Failed password for root from 49.88.112.72 port 60150 ssh2 Sep 6 12:22:56 mx sshd[582454]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.72 user=root Sep 6 12:22:57 mx sshd[582454]: Failed password for root from 49.88.112.72 port 37065 ssh2 ... |
2020-09-06 15:01:15 |
| 51.77.220.127 | attackspam | 51.77.220.127 - - [06/Sep/2020:10:38:00 +0400] "POST /GponForm/diag_Form?style/ HTTP/1.1" 502 157 "-" "curl/7.3.2" ... |
2020-09-06 14:49:35 |
| 221.225.229.60 | attackspambots | Aug 31 07:09:03 georgia postfix/smtpd[35470]: connect from unknown[221.225.229.60] Aug 31 07:09:08 georgia postfix/smtpd[35470]: warning: unknown[221.225.229.60]: SASL LOGIN authentication failed: authentication failure Aug 31 07:09:09 georgia postfix/smtpd[35470]: lost connection after AUTH from unknown[221.225.229.60] Aug 31 07:09:09 georgia postfix/smtpd[35470]: disconnect from unknown[221.225.229.60] ehlo=1 auth=0/1 commands=1/2 Aug 31 07:09:10 georgia postfix/smtpd[35470]: connect from unknown[221.225.229.60] Aug 31 07:09:16 georgia postfix/smtpd[35470]: warning: unknown[221.225.229.60]: SASL LOGIN authentication failed: authentication failure Aug 31 07:09:17 georgia postfix/smtpd[35470]: lost connection after AUTH from unknown[221.225.229.60] Aug 31 07:09:17 georgia postfix/smtpd[35470]: disconnect from unknown[221.225.229.60] ehlo=1 auth=0/1 commands=1/2 Aug 31 07:09:17 georgia postfix/smtpd[35470]: connect from unknown[221.225.229.60] Aug 31 07:09:21 georgia pos........ ------------------------------- |
2020-09-06 15:04:31 |
| 185.220.100.255 | attackspambots | log:/img/meteo_804d_photo.jpg |
2020-09-06 14:50:09 |
| 134.202.64.131 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found staytunedchiropractic.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 softwa |
2020-09-06 15:12:16 |
| 106.12.84.63 | attackspam | 2020-09-05T23:21:57.488771shield sshd\[22936\]: Invalid user anurag from 106.12.84.63 port 49481 2020-09-05T23:21:57.498134shield sshd\[22936\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.84.63 2020-09-05T23:21:59.309120shield sshd\[22936\]: Failed password for invalid user anurag from 106.12.84.63 port 49481 ssh2 2020-09-05T23:24:41.003568shield sshd\[23408\]: Invalid user praveen from 106.12.84.63 port 32582 2020-09-05T23:24:41.014161shield sshd\[23408\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.84.63 |
2020-09-06 14:55:50 |
| 202.72.243.198 | attackbots | Sep 6 08:11:35 root sshd[14296]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.72.243.198 ... |
2020-09-06 14:48:15 |
| 218.92.0.184 | attack | Sep 5 20:33:52 hanapaa sshd\[22992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.184 user=root Sep 5 20:33:54 hanapaa sshd\[22992\]: Failed password for root from 218.92.0.184 port 23759 ssh2 Sep 5 20:33:57 hanapaa sshd\[22992\]: Failed password for root from 218.92.0.184 port 23759 ssh2 Sep 5 20:34:00 hanapaa sshd\[22992\]: Failed password for root from 218.92.0.184 port 23759 ssh2 Sep 5 20:34:03 hanapaa sshd\[22992\]: Failed password for root from 218.92.0.184 port 23759 ssh2 |
2020-09-06 14:53:42 |
| 164.132.46.14 | attackbots | Sep 6 08:15:05 root sshd[16768]: Failed password for root from 164.132.46.14 port 55950 ssh2 ... |
2020-09-06 14:54:58 |
| 104.206.119.2 | attackspam | Aug 31 06:40:58 mxgate1 postfix/postscreen[24409]: CONNECT from [104.206.119.2]:60811 to [176.31.12.44]:25 Aug 31 06:41:04 mxgate1 postfix/postscreen[24409]: PASS NEW [104.206.119.2]:60811 Aug 31 06:41:04 mxgate1 postfix/smtpd[24410]: warning: hostname iseedragon.com does not resolve to address 104.206.119.2: Name or service not known Aug 31 06:41:04 mxgate1 postfix/smtpd[24410]: connect from unknown[104.206.119.2] Aug 31 06:41:04 mxgate1 postfix/smtpd[24410]: DEA36A03F4: client=unknown[104.206.119.2] Aug 31 06:41:08 mxgate1 postfix/smtpd[24410]: disconnect from unknown[104.206.119.2] ehlo=1 mail=1 rcpt=1 data=1 quhostname=1 commands=5 Aug 31 06:41:08 mxgate1 postfix/postscreen[24409]: CONNECT from [104.206.119.2]:51121 to [176.31.12.44]:25 Aug 31 06:41:08 mxgate1 postfix/postscreen[24409]: PASS OLD [104.206.119.2]:51121 Aug 31 06:41:08 mxgate1 postfix/smtpd[24410]: warning: hostname iseedragon.com does not resolve to address 104.206.119.2: Name or service not known Aug........ ------------------------------- |
2020-09-06 14:44:41 |
| 92.63.197.71 | attackbotsspam | [portscan] tcp/3389 [MS RDP] *(RWIN=1024)(09060936) |
2020-09-06 15:04:05 |
| 103.78.15.2 | attack | Automatic report - Banned IP Access |
2020-09-06 15:09:08 |
| 222.186.180.8 | attack | Sep 6 08:58:05 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:08 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:17 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:17 minden010 sshd[21624]: error: maximum authentication attempts exceeded for root from 222.186.180.8 port 49334 ssh2 [preauth] ... |
2020-09-06 15:13:18 |
| 185.214.164.6 | attackspambots | 20 attempts against mh-misbehave-ban on oak |
2020-09-06 14:43:02 |