City: unknown
Region: unknown
Country: Norway
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 92.220.161.113
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31456
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;92.220.161.113. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012300 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 19:50:15 CST 2025
;; MSG SIZE rcvd: 107113.161.220.92.in-addr.arpa domain name pointer 113.92-220-161.customer.lyse.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
113.161.220.92.in-addr.arpa name = 113.92-220-161.customer.lyse.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 180.168.76.222 | attackspam | frenzy |
2019-10-30 18:17:12 |
| 139.217.234.68 | attackspambots | Oct 30 06:19:13 server sshd\[3699\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.217.234.68 user=root Oct 30 06:19:15 server sshd\[3699\]: Failed password for root from 139.217.234.68 port 40486 ssh2 Oct 30 06:43:51 server sshd\[9645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.217.234.68 user=root Oct 30 06:43:53 server sshd\[9645\]: Failed password for root from 139.217.234.68 port 41480 ssh2 Oct 30 06:48:25 server sshd\[10786\]: Invalid user odoo from 139.217.234.68 ... |
2019-10-30 18:31:50 |
| 91.121.67.107 | attack | Oct 30 11:16:02 legacy sshd[570]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.67.107 Oct 30 11:16:04 legacy sshd[570]: Failed password for invalid user shriram from 91.121.67.107 port 36390 ssh2 Oct 30 11:19:42 legacy sshd[667]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.67.107 ... |
2019-10-30 18:30:29 |
| 103.14.33.229 | attack | Automatic report - Banned IP Access |
2019-10-30 18:50:58 |
| 78.128.113.120 | attackbots | 2019-10-30T11:18:26.266535mail01 postfix/smtpd[4780]: warning: unknown[78.128.113.120]: SASL PLAIN authentication failed: 2019-10-30T11:18:33.301948mail01 postfix/smtpd[4784]: warning: unknown[78.128.113.120]: SASL PLAIN authentication failed: 2019-10-30T11:18:36.239995mail01 postfix/smtpd[1132]: warning: unknown[78.128.113.120]: SASL PLAIN authentication failed: |
2019-10-30 18:27:58 |
| 101.110.45.156 | attackbotsspam | Oct 30 06:46:30 server sshd\[25931\]: User root from 101.110.45.156 not allowed because listed in DenyUsers Oct 30 06:46:30 server sshd\[25931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.110.45.156 user=root Oct 30 06:46:32 server sshd\[25931\]: Failed password for invalid user root from 101.110.45.156 port 40844 ssh2 Oct 30 06:50:44 server sshd\[7718\]: Invalid user 13 from 101.110.45.156 port 59858 Oct 30 06:50:44 server sshd\[7718\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.110.45.156 |
2019-10-30 18:21:30 |
| 51.75.254.196 | attackbotsspam | Oct 30 06:07:08 server sshd\[27441\]: Invalid user slam from 51.75.254.196 port 25375 Oct 30 06:07:08 server sshd\[27441\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.254.196 Oct 30 06:07:10 server sshd\[27441\]: Failed password for invalid user slam from 51.75.254.196 port 25375 ssh2 Oct 30 06:10:50 server sshd\[3562\]: Invalid user Pa55word from 51.75.254.196 port 63827 Oct 30 06:10:50 server sshd\[3562\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.254.196 |
2019-10-30 18:19:31 |
| 45.227.253.140 | attackspam | Oct 30 10:06:49 heicom postfix/smtpd\[12761\]: warning: unknown\[45.227.253.140\]: SASL LOGIN authentication failed: authentication failure Oct 30 10:07:07 heicom postfix/smtpd\[12759\]: warning: unknown\[45.227.253.140\]: SASL LOGIN authentication failed: authentication failure Oct 30 10:07:10 heicom postfix/smtpd\[12761\]: warning: unknown\[45.227.253.140\]: SASL LOGIN authentication failed: authentication failure Oct 30 10:35:36 heicom postfix/smtpd\[13539\]: warning: unknown\[45.227.253.140\]: SASL LOGIN authentication failed: authentication failure Oct 30 10:35:38 heicom postfix/smtpd\[13539\]: warning: unknown\[45.227.253.140\]: SASL LOGIN authentication failed: authentication failure ... |
2019-10-30 18:46:58 |
| 104.236.142.200 | attack | Automatic report - Banned IP Access |
2019-10-30 18:47:49 |
| 124.74.110.230 | attackbots | Unauthorized connection attempt from IP address 124.74.110.230 on Port 445(SMB) |
2019-10-30 18:39:39 |
| 54.38.36.210 | attackbots | Oct 29 20:26:05 tdfoods sshd\[10759\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.36.210 user=root Oct 29 20:26:07 tdfoods sshd\[10759\]: Failed password for root from 54.38.36.210 port 41566 ssh2 Oct 29 20:30:04 tdfoods sshd\[11087\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.36.210 user=root Oct 29 20:30:06 tdfoods sshd\[11087\]: Failed password for root from 54.38.36.210 port 51652 ssh2 Oct 29 20:34:01 tdfoods sshd\[11394\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.36.210 user=root |
2019-10-30 18:38:25 |
| 182.61.40.17 | attackbotsspam | Oct 30 04:41:13 vps sshd[25061]: Failed password for root from 182.61.40.17 port 57820 ssh2 Oct 30 04:47:40 vps sshd[25323]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.17 Oct 30 04:47:41 vps sshd[25323]: Failed password for invalid user india from 182.61.40.17 port 47196 ssh2 ... |
2019-10-30 18:50:37 |
| 114.5.221.142 | attackbots | [Wed Oct 30 10:48:27.264476 2019] [:error] [pid 7559:tid 140145034290944] [client 114.5.221.142:6521] [client 114.5.221.142] ModSecurity: Access denied with code 403 (phase 4). Pattern match "^5\\\\d{2}$" at RESPONSE_STATUS. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/RESPONSE-950-DATA-LEAKAGES.conf"] [line "118"] [id "950100"] [msg "The Application Returned a 500-Level Status Code"] [data "Matched Data: 503 found within RESPONSE_STATUS: 503"] [severity "ERROR"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-disclosure"] [tag "WASCTC/WASC-13"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.6"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/profil/peta-instrumentasi"] [unique_id "XbkIC48ZrE8Gf@6lZT6dTQAAAAE"], referer: https://karangploso.jatim.bmkg.go.id/
... |
2019-10-30 18:28:28 |
| 1.186.45.250 | attackbotsspam | 2019-10-28 07:53:10,216 fail2ban.actions \[1516\]: NOTICE \[sshd\] Ban 1.186.45.250 2019-10-28 08:25:47,185 fail2ban.actions \[1516\]: NOTICE \[sshd\] Ban 1.186.45.250 2019-10-28 08:58:40,463 fail2ban.actions \[1516\]: NOTICE \[sshd\] Ban 1.186.45.250 2019-10-28 09:31:47,021 fail2ban.actions \[1516\]: NOTICE \[sshd\] Ban 1.186.45.250 2019-10-28 10:05:16,388 fail2ban.actions \[1516\]: NOTICE \[sshd\] Ban 1.186.45.250 ... |
2019-10-30 18:21:46 |
| 185.183.185.175 | attackspambots | Automatic report - XMLRPC Attack |
2019-10-30 18:22:57 |