城市(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.242.23.196
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52913
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;70.242.23.196. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022500 1800 900 604800 86400
;; Query time: 98 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 26 01:30:28 CST 2025
;; MSG SIZE rcvd: 106196.23.242.70.in-addr.arpa domain name pointer adsl-70-242-23-196.dsl.hstntx.swbell.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
196.23.242.70.in-addr.arpa name = adsl-70-242-23-196.dsl.hstntx.swbell.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 58.62.18.194 | attackbotsspam | Aug 28 22:23:36 mailserver sshd\[23786\]: Invalid user xavier from 58.62.18.194 ... |
2020-08-29 06:07:15 |
| 154.16.203.118 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjamieswellnesscenter.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 softw |
2020-08-29 06:08:24 |
| 211.253.27.146 | attackbots | Invalid user denis from 211.253.27.146 port 35800 |
2020-08-29 05:59:48 |
| 41.72.197.182 | attackspam | IP blocked |
2020-08-29 05:45:24 |
| 106.53.249.204 | attack | 2020-08-29T03:35:54.347088hostname sshd[15897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.249.204 2020-08-29T03:35:54.328857hostname sshd[15897]: Invalid user daniel from 106.53.249.204 port 33711 2020-08-29T03:35:56.026304hostname sshd[15897]: Failed password for invalid user daniel from 106.53.249.204 port 33711 ssh2 ... |
2020-08-29 06:10:10 |
| 45.176.208.50 | attackspambots | Invalid user friedrich from 45.176.208.50 port 43039 |
2020-08-29 06:01:23 |
| 106.75.148.228 | attack | Total attacks: 2 |
2020-08-29 06:14:32 |
| 188.131.138.175 | attack | Aug 28 23:10:56 master sshd[2230]: Failed password for invalid user aek from 188.131.138.175 port 47730 ssh2 Aug 28 23:33:10 master sshd[2839]: Failed password for root from 188.131.138.175 port 54282 ssh2 Aug 28 23:38:55 master sshd[2887]: Failed password for invalid user vvk from 188.131.138.175 port 58576 ssh2 Aug 28 23:44:32 master sshd[3013]: Failed password for invalid user ftpuser from 188.131.138.175 port 34636 ssh2 Aug 28 23:50:14 master sshd[3147]: Failed password for invalid user moon from 188.131.138.175 port 38928 ssh2 Aug 29 00:01:33 master sshd[3660]: Failed password for invalid user wf from 188.131.138.175 port 47506 ssh2 Aug 29 00:07:08 master sshd[3714]: Failed password for invalid user esteban from 188.131.138.175 port 51794 ssh2 Aug 29 00:12:43 master sshd[3836]: Failed password for invalid user alexis from 188.131.138.175 port 56074 ssh2 Aug 29 00:23:48 master sshd[3999]: Failed password for root from 188.131.138.175 port 36408 ssh2 |
2020-08-29 06:13:29 |
| 128.199.128.98 | attackspam | SSH Invalid Login |
2020-08-29 06:09:51 |
| 85.209.0.101 | attack | Aug 23 03:12:49 : SSH login attempts with invalid user |
2020-08-29 06:09:11 |
| 122.224.168.22 | attackspam | SSH Invalid Login |
2020-08-29 05:54:57 |
| 202.44.40.193 | attackbots | Aug 29 00:15:04 ip106 sshd[8841]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.44.40.193 Aug 29 00:15:06 ip106 sshd[8841]: Failed password for invalid user us from 202.44.40.193 port 39986 ssh2 ... |
2020-08-29 06:15:45 |
| 51.79.70.223 | attackbotsspam | Aug 28 23:56:18 ns381471 sshd[24116]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.70.223 Aug 28 23:56:20 ns381471 sshd[24116]: Failed password for invalid user deploy from 51.79.70.223 port 40676 ssh2 |
2020-08-29 06:18:59 |
| 222.186.30.59 | attack | Aug 29 00:00:46 vps639187 sshd\[19950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.59 user=root Aug 29 00:00:49 vps639187 sshd\[19950\]: Failed password for root from 222.186.30.59 port 49287 ssh2 Aug 29 00:00:51 vps639187 sshd\[19950\]: Failed password for root from 222.186.30.59 port 49287 ssh2 ... |
2020-08-29 06:06:09 |
| 103.151.123.187 | attack | Aug 28 22:22:57 localhost postfix/smtpd\[28168\]: warning: unknown\[103.151.123.187\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 28 22:23:04 localhost postfix/smtpd\[27537\]: warning: unknown\[103.151.123.187\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 28 22:23:16 localhost postfix/smtpd\[28168\]: warning: unknown\[103.151.123.187\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 28 22:23:42 localhost postfix/smtpd\[27537\]: warning: unknown\[103.151.123.187\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 28 22:23:50 localhost postfix/smtpd\[27537\]: warning: unknown\[103.151.123.187\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-08-29 05:58:54 |