City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 215.237.135.3
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 65473
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;215.237.135.3. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022401 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 25 11:40:06 CST 2025
;; MSG SIZE rcvd: 106b'Host 3.135.237.215.in-addr.arpa not found: 2(SERVFAIL)
'server can't find 215.237.135.3.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 162.142.125.34 | attack | Sep 1 21:37:38 www postfix/smtpd\[8066\]: lost connection after EHLO from scanner-04.ch1.censys-scanner.com\[162.142.125.34\] |
2020-09-02 06:48:51 |
| 73.148.174.117 | attack | SSH/22 MH Probe, BF, Hack - |
2020-09-02 06:40:18 |
| 24.214.171.213 | attackspambots | SSH/22 MH Probe, BF, Hack - |
2020-09-02 06:42:31 |
| 92.63.194.104 | attack | IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking. |
2020-09-02 06:58:59 |
| 222.209.247.203 | attackbotsspam | SSH/22 MH Probe, BF, Hack - |
2020-09-02 06:44:43 |
| 51.77.210.201 | attack | Sep 2 00:30:24 pve1 sshd[29213]: Failed password for root from 51.77.210.201 port 45188 ssh2 Sep 2 00:30:27 pve1 sshd[29213]: Failed password for root from 51.77.210.201 port 45188 ssh2 ... |
2020-09-02 06:48:08 |
| 239.255.255.250 | spambotsattackproxy | sparadic proxy on apnic ip |
2020-09-02 06:26:22 |
| 192.3.139.56 | attack | Invalid user hc from 192.3.139.56 port 39418 |
2020-09-02 06:41:46 |
| 103.96.220.115 | attackbots | Sep 1 23:59:12 ns382633 sshd\[1812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.96.220.115 user=root Sep 1 23:59:14 ns382633 sshd\[1812\]: Failed password for root from 103.96.220.115 port 55696 ssh2 Sep 2 00:02:34 ns382633 sshd\[2502\]: Invalid user logger from 103.96.220.115 port 40842 Sep 2 00:02:34 ns382633 sshd\[2502\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.96.220.115 Sep 2 00:02:35 ns382633 sshd\[2502\]: Failed password for invalid user logger from 103.96.220.115 port 40842 ssh2 |
2020-09-02 06:27:52 |
| 87.251.73.238 | attackspam | [H1.VM6] Blocked by UFW |
2020-09-02 06:38:41 |
| 152.32.164.141 | attackspambots | Bruteforce detected by fail2ban |
2020-09-02 06:39:36 |
| 69.119.85.43 | attackspam | (sshd) Failed SSH login from 69.119.85.43 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 1 21:26:31 server sshd[22265]: Invalid user admin from 69.119.85.43 Sep 1 21:26:33 server sshd[22265]: Failed password for invalid user admin from 69.119.85.43 port 48878 ssh2 Sep 1 21:31:03 server sshd[22753]: Failed password for ftp from 69.119.85.43 port 45744 ssh2 Sep 1 21:34:37 server sshd[23143]: Invalid user ftp-user from 69.119.85.43 Sep 1 21:34:39 server sshd[23143]: Failed password for invalid user ftp-user from 69.119.85.43 port 34062 ssh2 |
2020-09-02 06:30:13 |
| 124.160.83.138 | attackspam | Aug 27 23:57:38 server sshd[16040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.160.83.138 Aug 27 23:57:41 server sshd[16040]: Failed password for invalid user dspace from 124.160.83.138 port 42154 ssh2 Aug 28 00:13:23 server sshd[17465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.160.83.138 Aug 28 00:13:26 server sshd[17465]: Failed password for invalid user sn from 124.160.83.138 port 60568 ssh2 |
2020-09-02 06:34:40 |
| 184.105.139.89 | spambotsattackproxy | malware https://freetexthost.net/wEReKhz |
2020-09-02 06:29:16 |
| 224.0.0.252 | botsattackproxy | there are unmediated big problems with this ip range still, in someway utilising bt tv stream packets unbeknowing to bt home hub wifi customers. devices become host servers and use of US at&t proxy ip's on some home hub locations routing other traffic. BT do not use proxy's on home hub connections |
2020-09-02 06:23:55 |