城市(city): unknown
省份(region): unknown
国家(country): None
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 94.209.142.125
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17420
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;94.209.142.125. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 18:13:28 CST 2025
;; MSG SIZE rcvd: 107
125.142.209.94.in-addr.arpa domain name pointer 94-209-142-125.cable.dynamic.v4.ziggo.nl.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
125.142.209.94.in-addr.arpa name = 94-209-142-125.cable.dynamic.v4.ziggo.nl.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 183.166.170.133 | attackspam | Oct 2 22:30:45 srv01 postfix/smtpd\[1755\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:34:11 srv01 postfix/smtpd\[6490\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:37:37 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:41:03 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 2 22:41:14 srv01 postfix/smtpd\[11183\]: warning: unknown\[183.166.170.133\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-10-03 12:28:54 |
| 1.255.48.197 | attack | (From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call. $24.99/mo Flat Fee Credit Card Processing (Unlimited) 1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware? New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019. Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees. 2) You're legally able to demand this new option. Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options? We repre |
2020-10-03 12:17:46 |
| 27.151.115.81 | attackbots | port scan and connect, tcp 1433 (ms-sql-s) |
2020-10-03 12:13:57 |
| 47.113.87.53 | attack | Unauthorized admin access - /admin/login.php |
2020-10-03 12:33:13 |
| 52.191.166.171 | attackbots | Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Invalid user ftpuser1 from 52.191.166.171 Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 Oct 2 21:41:38 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Failed password for invalid user ftpuser1 from 52.191.166.171 port 36892 ssh2 Oct 2 22:41:04 Ubuntu-1404-trusty-64-minimal sshd\[619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 user=git Oct 2 22:41:06 Ubuntu-1404-trusty-64-minimal sshd\[619\]: Failed password for git from 52.191.166.171 port 60674 ssh2 |
2020-10-03 12:36:47 |
| 122.14.228.229 | attack | Oct 2 21:00:27 corona-Z97-D3H sshd[68326]: Invalid user ems from 122.14.228.229 port 52596 ... |
2020-10-03 12:34:47 |
| 81.68.123.185 | attackbots | $f2bV_matches |
2020-10-03 12:46:02 |
| 114.67.254.244 | attackbots | pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.254.244 Failed password for invalid user mani from 114.67.254.244 port 38272 ssh2 pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.254.244 |
2020-10-03 12:09:33 |
| 60.174.248.244 | attackspambots | Fail2Ban Ban Triggered |
2020-10-03 12:26:41 |
| 34.120.202.146 | attackbots | RU spamvertising, health fraud - From: GlucaFIX |
2020-10-03 12:06:19 |
| 122.155.223.59 | attackbots | sshguard |
2020-10-03 12:06:50 |
| 89.233.112.6 | attackbots | port scan and connect, tcp 23 (telnet) |
2020-10-03 12:13:36 |
| 45.148.121.92 | attackspam | 45.148.121.92 was recorded 5 times by 4 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 5, 11, 60 |
2020-10-03 12:12:41 |
| 167.172.36.232 | attack | Oct 2 21:28:00 email sshd\[633\]: Invalid user unifi from 167.172.36.232 Oct 2 21:28:00 email sshd\[633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.36.232 Oct 2 21:28:01 email sshd\[633\]: Failed password for invalid user unifi from 167.172.36.232 port 46238 ssh2 Oct 2 21:31:17 email sshd\[1223\]: Invalid user walter from 167.172.36.232 Oct 2 21:31:17 email sshd\[1223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.36.232 ... |
2020-10-03 12:10:22 |
| 80.20.14.250 | attackbots | SSH Brute-force |
2020-10-03 12:42:02 |