City: Hersbruck
Region: Bayern
Country: Germany
Internet Service Provider: Telekom
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.145.44.224
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50935
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;80.145.44.224. IN A
;; AUTHORITY SECTION:
. 488 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2023042401 1800 900 604800 86400
;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Apr 25 07:36:12 CST 2023
;; MSG SIZE rcvd: 106
224.44.145.80.in-addr.arpa domain name pointer p50912ce0.dip0.t-ipconnect.de.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
224.44.145.80.in-addr.arpa name = p50912ce0.dip0.t-ipconnect.de.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
94.237.45.244 | attackspambots | Bruteforce detected by fail2ban |
2020-04-16 07:50:33 |
162.243.132.5 | attack | Port Scan: Events[2] countPorts[2]: 8081 21 .. |
2020-04-16 07:39:29 |
176.226.179.162 | attackspam | W 31101,/var/log/nginx/access.log,-,- |
2020-04-16 07:38:57 |
112.85.42.174 | attackbots | 2020-04-16T01:32:34.885115vps751288.ovh.net sshd\[20821\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.174 user=root 2020-04-16T01:32:37.371995vps751288.ovh.net sshd\[20821\]: Failed password for root from 112.85.42.174 port 51605 ssh2 2020-04-16T01:32:41.090965vps751288.ovh.net sshd\[20821\]: Failed password for root from 112.85.42.174 port 51605 ssh2 2020-04-16T01:32:44.022536vps751288.ovh.net sshd\[20821\]: Failed password for root from 112.85.42.174 port 51605 ssh2 2020-04-16T01:32:47.365652vps751288.ovh.net sshd\[20821\]: Failed password for root from 112.85.42.174 port 51605 ssh2 |
2020-04-16 07:39:53 |
216.180.105.236 | attack | (From lothian.winifred@hotmail.com) If you’ve been online any amount of time, you’re most likely still struggling to make the money you want online… Am I right? Well, we’re confident to say that you’ve come to the right place. You might be thinking… Why are we different from the thousands of so-called “expert marketers” out there? For one, I have the power to read your mind. I know exactly why you’re struggling right now... OK - maybe reading your mind is a bit far fetched. But what I can tell you is this… We’ve worked with over 45,000+ customers. And if they were struggling, we noticed it always came down to ONE important factor… =>> http://bit.ly/UnlTraffic You don't need to work for anyone else. You don't need to take orders from your boss. And you don't need to take permission to take vacation or spend a day with family. And this is not just talk, let me show you real PROOF… =>> http://bit.ly/UnlTraffic Cheers |
2020-04-16 07:31:27 |
106.12.56.143 | attackbotsspam | SSH Invalid Login |
2020-04-16 07:44:51 |
181.48.155.149 | attackspam | Invalid user ubuntu from 181.48.155.149 port 42356 |
2020-04-16 07:45:39 |
190.64.213.155 | attack | Port Scan: Events[2] countPorts[1]: 22 .. |
2020-04-16 07:36:51 |
49.234.16.16 | attackspam | 04/15/2020-16:56:02.342541 49.234.16.16 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-16 07:20:19 |
162.243.133.35 | attackspam | Port Scan: Events[1] countPorts[1]: 179 .. |
2020-04-16 07:32:13 |
203.116.130.164 | attack | Automatic report - Port Scan Attack |
2020-04-16 07:21:31 |
218.92.0.158 | attack | Apr 15 19:41:10 NPSTNNYC01T sshd[20193]: Failed password for root from 218.92.0.158 port 34851 ssh2 Apr 15 19:41:14 NPSTNNYC01T sshd[20193]: Failed password for root from 218.92.0.158 port 34851 ssh2 Apr 15 19:41:16 NPSTNNYC01T sshd[20193]: Failed password for root from 218.92.0.158 port 34851 ssh2 Apr 15 19:41:22 NPSTNNYC01T sshd[20193]: error: maximum authentication attempts exceeded for root from 218.92.0.158 port 34851 ssh2 [preauth] ... |
2020-04-16 07:49:10 |
103.96.232.130 | attackbotsspam | Apr 16 01:26:33 srv01 sshd[976]: Invalid user couchdb from 103.96.232.130 port 59792 Apr 16 01:26:33 srv01 sshd[976]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.96.232.130 Apr 16 01:26:33 srv01 sshd[976]: Invalid user couchdb from 103.96.232.130 port 59792 Apr 16 01:26:35 srv01 sshd[976]: Failed password for invalid user couchdb from 103.96.232.130 port 59792 ssh2 Apr 16 01:27:51 srv01 sshd[1054]: Invalid user felix from 103.96.232.130 port 49054 ... |
2020-04-16 07:46:31 |
213.180.203.2 | attackspam | [Thu Apr 16 03:23:14.156372 2020] [:error] [pid 27072:tid 140327109256960] [client 213.180.203.2:55152] [client 213.180.203.2] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XpdtMtf343qgl4K6QZWtSwAABGY"] ... |
2020-04-16 07:27:41 |
209.17.96.130 | attackspambots | Brute force attack stopped by firewall |
2020-04-16 07:26:51 |