City: unknown
Region: unknown
Country: Romania
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '80.94.92.0 - 80.94.92.255'
% Abuse contact for '80.94.92.0 - 80.94.92.255' is 'dmzhostabuse@gmail.com'
inetnum: 80.94.92.0 - 80.94.92.255
org: ORG-TSL73-RIPE
netname: DMZHOST
descr: https://dmzhost.co
country: NL
admin-c: AD18161-RIPE
tech-c: AD18161-RIPE
mnt-routes: TECHOFF-MNT
mnt-lower: TECHOFF-MNT
mnt-domains: TECHOFF-MNT
status: ASSIGNED PA
mnt-by: ro-btel2-1-mnt
mnt-by: TECHOFF-MNT
created: 2020-07-15T22:20:31Z
last-modified: 2024-11-21T09:38:42Z
source: RIPE
organisation: ORG-TSL73-RIPE
org-name: TECHOFF SRV LIMITED
country: GB
reg-nr: 16090235
org-type: OTHER
address: 35 Firs Avenue, London N11 3NE
abuse-c: AD18161-RIPE
mnt-ref: TECHOFF-MNT
mnt-ref: MNT-NETERRA
mnt-by: TECHOFF-MNT
created: 2024-11-20T13:01:40Z
last-modified: 2026-05-13T05:55:49Z
source: RIPE # Filtered
role: ABUSE DEP
address: 35 Firs Avenue, London N11 3NE
abuse-mailbox: dmzhostabuse@gmail.com
nic-hdl: AD18161-RIPE
mnt-by: TECHOFF-MNT
created: 2024-11-20T13:00:28Z
last-modified: 2024-11-21T09:45:52Z
source: RIPE # Filtered
% Information related to '80.94.92.0/24AS35478'
route: 80.94.92.0/24
origin: AS35478
mnt-by: ro-btel2-1-mnt
created: 2020-07-31T19:36:59Z
last-modified: 2020-07-31T19:36:59Z
source: RIPE
% Information related to '80.94.92.0/24AS47890'
route: 80.94.92.0/24
origin: AS47890
mnt-by: UNMANAGED
mnt-by: ro-btel2-1-mnt
created: 2022-08-06T20:29:26Z
last-modified: 2022-08-06T20:29:26Z
source: RIPE
% Information related to '80.94.92.0/24AS48090'
route: 80.94.92.0/24
origin: AS48090
mnt-by: UNMANAGED
mnt-by: ro-btel2-1-mnt
created: 2021-03-30T10:00:28Z
last-modified: 2021-03-30T10:00:28Z
source: RIPE
% This query was served by the RIPE Database Query Service version 1.124.1 (ABERDEEN); <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.94.92.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31126
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;80.94.92.20. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026103101 1800 900 604800 86400
;; Query time: 93 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 01 12:00:09 CST 2026
;; MSG SIZE rcvd: 104Host 20.92.94.80.in-addr.arpa not found: 2(SERVFAIL)
server can't find 80.94.92.20.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 23.231.34.42 | attack | (From eric@talkwithcustomer.com) Hello lifesourcefamilychiro.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website lifesourcefamilychiro.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website lifesourcefamilychiro.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Ti |
2019-07-12 00:32:58 |
| 159.65.153.163 | attackbots | Jul 2 22:15:32 server sshd\[137990\]: Invalid user wpyan from 159.65.153.163 Jul 2 22:15:32 server sshd\[137990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.153.163 Jul 2 22:15:34 server sshd\[137990\]: Failed password for invalid user wpyan from 159.65.153.163 port 51754 ssh2 ... |
2019-07-12 00:00:58 |
| 159.65.111.89 | attackspam | May 21 10:13:20 server sshd\[45030\]: Invalid user jsserver from 159.65.111.89 May 21 10:13:20 server sshd\[45030\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.111.89 May 21 10:13:22 server sshd\[45030\]: Failed password for invalid user jsserver from 159.65.111.89 port 58912 ssh2 ... |
2019-07-12 00:25:15 |
| 159.65.148.241 | attackspam | Apr 21 18:52:44 server sshd\[13730\]: Invalid user clamav1 from 159.65.148.241 Apr 21 18:52:44 server sshd\[13730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.148.241 Apr 21 18:52:46 server sshd\[13730\]: Failed password for invalid user clamav1 from 159.65.148.241 port 40214 ssh2 ... |
2019-07-12 00:03:15 |
| 159.65.188.247 | attack | Jun 26 18:59:02 server sshd\[125741\]: Invalid user bran from 159.65.188.247 Jun 26 18:59:02 server sshd\[125741\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.188.247 Jun 26 18:59:03 server sshd\[125741\]: Failed password for invalid user bran from 159.65.188.247 port 38646 ssh2 ... |
2019-07-11 23:53:46 |
| 36.250.234.33 | attack | May 1 11:12:41 server sshd\[190492\]: Invalid user pokemon from 36.250.234.33 May 1 11:12:41 server sshd\[190492\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.250.234.33 May 1 11:12:43 server sshd\[190492\]: Failed password for invalid user pokemon from 36.250.234.33 port 38499 ssh2 ... |
2019-07-12 00:50:21 |
| 159.65.137.23 | attackspambots | Jul 7 07:15:08 server sshd\[38228\]: Invalid user raja from 159.65.137.23 Jul 7 07:15:08 server sshd\[38228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.137.23 Jul 7 07:15:10 server sshd\[38228\]: Failed password for invalid user raja from 159.65.137.23 port 43744 ssh2 ... |
2019-07-12 00:15:16 |
| 185.35.64.227 | attackbotsspam | Paket-Lieferank�ndigung, Geliefert |
2019-07-12 00:40:34 |
| 157.230.39.61 | attackbots | Apr 22 18:51:36 server sshd\[48523\]: Invalid user jesus from 157.230.39.61 Apr 22 18:51:36 server sshd\[48523\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.39.61 Apr 22 18:51:39 server sshd\[48523\]: Failed password for invalid user jesus from 157.230.39.61 port 54090 ssh2 ... |
2019-07-12 01:06:12 |
| 158.69.192.147 | attackbots | May 13 21:11:38 server sshd\[170085\]: Invalid user ar from 158.69.192.147 May 13 21:11:38 server sshd\[170085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=158.69.192.147 May 13 21:11:40 server sshd\[170085\]: Failed password for invalid user ar from 158.69.192.147 port 46432 ssh2 ... |
2019-07-12 00:55:37 |
| 220.186.159.69 | attack | Brute force SMTP login attempts. |
2019-07-12 00:26:30 |
| 181.118.122.40 | attackbots | Caught in portsentry honeypot |
2019-07-12 00:54:59 |
| 46.4.84.115 | attack | Jul 11 14:15:36 MK-Soft-VM4 sshd\[16933\]: Invalid user cent from 46.4.84.115 port 42556 Jul 11 14:15:36 MK-Soft-VM4 sshd\[16933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.4.84.115 Jul 11 14:15:39 MK-Soft-VM4 sshd\[16933\]: Failed password for invalid user cent from 46.4.84.115 port 42556 ssh2 ... |
2019-07-12 00:08:42 |
| 159.65.147.154 | attackbots | Jun 16 22:37:37 server sshd\[48294\]: Invalid user lu from 159.65.147.154 Jun 16 22:37:37 server sshd\[48294\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.147.154 Jun 16 22:37:39 server sshd\[48294\]: Failed password for invalid user lu from 159.65.147.154 port 55800 ssh2 ... |
2019-07-12 00:04:49 |
| 101.20.252.53 | attackbotsspam | D-Link DSL-2750B Remote Command Execution Vulnerability |
2019-07-12 00:21:07 |