City: Florø
Region: Vestland
Country: Norway
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 '185.174.85.0 - 185.174.85.255'
% Abuse contact for '185.174.85.0 - 185.174.85.255' is 'support@nordfjordnett.no'
inetnum: 185.174.85.0 - 185.174.85.255
netname: Nordfjordnett_LIR_Infrastructure_MIP
country: NO
admin-c: NN2323-RIPE
tech-c: NN2323-RIPE
status: ASSIGNED PA
abuse-c: AR38035-RIPE
mnt-by: no-nordfjordnett-1-mnt
created: 2025-10-01T07:38:52Z
last-modified: 2025-10-01T07:38:52Z
source: RIPE
role: NFN NOC
address: Myrane 14, 6718 Deknepollen
nic-hdl: NN2323-RIPE
admin-c: TS42804-RIPE
tech-c: TS42804-RIPE
tech-c: RA7612-RIPE
abuse-mailbox: infrastruktur@nordfjordnett.no
mnt-by: no-nordfjordnett-1-mnt
created: 2016-10-20T21:21:37Z
last-modified: 2025-10-15T09:24:54Z
source: RIPE # Filtered
% Information related to '185.174.84.0/22AS201098'
route: 185.174.84.0/22
origin: AS201098
mnt-by: no-nordfjordnett-1-mnt
created: 2017-02-07T11:18:42Z
last-modified: 2017-02-07T11:18:42Z
source: RIPE
descr: Nordfjordnett IPv4
% This query was served by the RIPE Database Query Service version 1.121.2 (SHETLAND)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 185.174.85.71
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58862
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;185.174.85.71. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026032101 1800 900 604800 86400
;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 22 15:19:39 CST 2026
;; MSG SIZE rcvd: 106
Host 71.85.174.185.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 71.85.174.185.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 103.218.2.137 | attackspambots | Nov 11 11:58:34 webhost01 sshd[18226]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.218.2.137 Nov 11 11:58:36 webhost01 sshd[18226]: Failed password for invalid user julio from 103.218.2.137 port 35713 ssh2 ... |
2019-11-11 13:28:36 |
| 185.100.87.250 | attackbotsspam | client denied by server configuration: /var/www/html/nmaplowercheck1573420945 client denied by server configuration: /var/www/html/evox client denied by server configuration: /var/www/html/sdk |
2019-11-11 13:22:45 |
| 144.217.84.164 | attackbots | Nov 11 02:58:42 ws12vmsma01 sshd[62368]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.ip-144-217-84.net Nov 11 02:58:42 ws12vmsma01 sshd[62368]: Invalid user bruner from 144.217.84.164 Nov 11 02:58:45 ws12vmsma01 sshd[62368]: Failed password for invalid user bruner from 144.217.84.164 port 39996 ssh2 ... |
2019-11-11 13:05:09 |
| 89.248.174.215 | attackbots | 11/10/2019-23:59:20.226148 89.248.174.215 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 98 |
2019-11-11 13:04:30 |
| 130.61.51.92 | attackbots | Nov 10 23:49:16 ny01 sshd[18350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.61.51.92 Nov 10 23:49:18 ny01 sshd[18350]: Failed password for invalid user fui from 130.61.51.92 port 42605 ssh2 Nov 10 23:58:57 ny01 sshd[19763]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.61.51.92 |
2019-11-11 13:21:04 |
| 183.220.146.252 | attackspambots | Nov 11 05:59:08 lnxded64 sshd[22797]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.220.146.252 |
2019-11-11 13:14:51 |
| 138.97.110.210 | attackbotsspam | 11/10/2019-23:59:03.319758 138.97.110.210 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2019-11-11 13:17:56 |
| 222.186.175.212 | attackspam | Nov 11 05:59:24 dedicated sshd[6476]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212 user=root Nov 11 05:59:26 dedicated sshd[6476]: Failed password for root from 222.186.175.212 port 32520 ssh2 |
2019-11-11 13:02:57 |
| 13.67.35.252 | attackbots | 2019-11-10T23:38:46.1455221495-001 sshd\[4664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.67.35.252 user=root 2019-11-10T23:38:48.3357541495-001 sshd\[4664\]: Failed password for root from 13.67.35.252 port 62910 ssh2 2019-11-10T23:43:34.5612831495-001 sshd\[4869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.67.35.252 user=mysql 2019-11-10T23:43:36.9570531495-001 sshd\[4869\]: Failed password for mysql from 13.67.35.252 port 62910 ssh2 2019-11-10T23:48:29.3501521495-001 sshd\[5009\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.67.35.252 user=root 2019-11-10T23:48:31.5753671495-001 sshd\[5009\]: Failed password for root from 13.67.35.252 port 62910 ssh2 ... |
2019-11-11 13:15:45 |
| 117.5.113.28 | attackspam | failed_logins |
2019-11-11 13:07:54 |
| 81.22.45.219 | attackspam | 81.22.45.219 was recorded 15 times by 2 hosts attempting to connect to the following ports: 63343,29971,35040,51873,8434,23039,36394,28695,34192,46905,15208,23864,7202,59826,43030. Incident counter (4h, 24h, all-time): 15, 88, 120 |
2019-11-11 13:32:17 |
| 68.183.204.162 | attackbots | 2019-11-10 23:58:50,527 fail2ban.actions [1798]: NOTICE [sshd] Ban 68.183.204.162 |
2019-11-11 13:26:57 |
| 159.89.91.214 | attack | A lockdown event has occurred due to too many failed login attempts or invalid username: Username: #profilepage IP Address: 159.89.91.214 |
2019-11-11 11:30:13 |
| 183.103.35.202 | attackbots | Nov 11 00:44:19 XXX sshd[34503]: Invalid user ky from 183.103.35.202 port 57626 |
2019-11-11 09:13:04 |
| 198.1.66.35 | attack | A lockdown event has occurred due to too many failed login attempts or invalid username: Username: #profilepage IP Address: 198.1.66.35 |
2019-11-11 12:56:26 |