城市(city): unknown
省份(region): unknown
国家(country): Germany
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.104.245.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64593
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.104.245.124. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022703 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 07:38:52 CST 2025
;; MSG SIZE rcvd: 108
Host 124.245.104.134.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 124.245.104.134.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.81.231.161 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.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 s |
2020-02-26 23:13:18 |
| 132.232.53.105 | attack | Feb 26 16:07:47 MK-Soft-VM8 sshd[2973]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.53.105 Feb 26 16:07:49 MK-Soft-VM8 sshd[2973]: Failed password for invalid user scan from 132.232.53.105 port 51370 ssh2 ... |
2020-02-26 23:10:23 |
| 122.252.238.220 | attack | Unauthorised access (Feb 26) SRC=122.252.238.220 LEN=52 TTL=118 ID=6420 DF TCP DPT=445 WINDOW=8192 SYN |
2020-02-26 23:16:38 |
| 167.71.91.151 | attackbots | DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks node-superagent/4.1.0 |
2020-02-26 22:53:28 |
| 213.141.130.168 | attackspambots | $f2bV_matches |
2020-02-26 23:16:07 |
| 213.60.165.77 | attackspam | $f2bV_matches |
2020-02-26 22:38:40 |
| 14.63.223.226 | attackspambots | Feb 26 15:53:32 vps647732 sshd[30486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.63.223.226 Feb 26 15:53:34 vps647732 sshd[30486]: Failed password for invalid user cashier from 14.63.223.226 port 35140 ssh2 ... |
2020-02-26 23:12:19 |
| 213.138.73.250 | attackspam | $f2bV_matches |
2020-02-26 23:19:05 |
| 213.190.31.77 | attack | $f2bV_matches |
2020-02-26 23:00:30 |
| 113.110.224.72 | attackbotsspam | suspicious action Wed, 26 Feb 2020 10:37:30 -0300 |
2020-02-26 23:11:44 |
| 213.135.70.227 | attackspam | $f2bV_matches |
2020-02-26 23:21:31 |
| 178.128.150.158 | attackspambots | Feb 26 15:38:16 vps647732 sshd[29940]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.150.158 Feb 26 15:38:19 vps647732 sshd[29940]: Failed password for invalid user GTX from 178.128.150.158 port 37534 ssh2 ... |
2020-02-26 22:43:41 |
| 107.158.84.6 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.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 s |
2020-02-26 23:19:50 |
| 106.12.215.238 | attackbots | (sshd) Failed SSH login from 106.12.215.238 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 26 15:52:51 amsweb01 sshd[18716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=root Feb 26 15:52:53 amsweb01 sshd[18716]: Failed password for root from 106.12.215.238 port 51792 ssh2 Feb 26 15:54:47 amsweb01 sshd[18878]: User mysql from 106.12.215.238 not allowed because not listed in AllowUsers Feb 26 15:54:47 amsweb01 sshd[18878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=mysql Feb 26 15:54:48 amsweb01 sshd[18878]: Failed password for invalid user mysql from 106.12.215.238 port 39108 ssh2 |
2020-02-26 22:59:08 |
| 124.113.219.74 | attackspambots | Feb 26 14:37:41 grey postfix/smtpd\[19375\]: NOQUEUE: reject: RCPT from unknown\[124.113.219.74\]: 554 5.7.1 Service unavailable\; Client host \[124.113.219.74\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[124.113.219.74\]\; from=\ |
2020-02-26 22:56:22 |