Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Netherlands (the)

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 46.145.138.31
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63280
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;46.145.138.31.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025021701 1800 900 604800 86400

;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 07:25:48 CST 2025
;; MSG SIZE  rcvd: 106
Host info
31.138.145.46.in-addr.arpa domain name pointer 46-145-138-31.biz.kpn.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
31.138.145.46.in-addr.arpa	name = 46-145-138-31.biz.kpn.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
189.210.53.176 attackspambots
Automatic report - Port Scan Attack
2019-12-31 18:56:14
103.4.67.142 attack
Honeypot attack, port: 445, PTR: 103-4-67-142.aamranetworks.com.
2019-12-31 18:49:50
192.81.220.234 attack
Dec 31 09:56:14 debian-2gb-nbg1-2 kernel: \[41909.189889\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=192.81.220.234 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=54321 PROTO=TCP SPT=35866 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0
2019-12-31 19:16:28
113.87.139.249 attack
Scanning
2019-12-31 19:13:02
49.88.112.63 attackbotsspam
Dec 31 10:54:22 hcbbdb sshd\[27464\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.63  user=root
Dec 31 10:54:24 hcbbdb sshd\[27464\]: Failed password for root from 49.88.112.63 port 56359 ssh2
Dec 31 10:54:40 hcbbdb sshd\[27490\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.63  user=root
Dec 31 10:54:42 hcbbdb sshd\[27490\]: Failed password for root from 49.88.112.63 port 25233 ssh2
Dec 31 10:54:45 hcbbdb sshd\[27490\]: Failed password for root from 49.88.112.63 port 25233 ssh2
2019-12-31 18:56:35
110.191.247.91 attack
Scanning
2019-12-31 18:51:10
112.85.42.227 attackbotsspam
Dec 31 05:35:11 TORMINT sshd\[18527\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.227  user=root
Dec 31 05:35:13 TORMINT sshd\[18527\]: Failed password for root from 112.85.42.227 port 12152 ssh2
Dec 31 05:36:18 TORMINT sshd\[18552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.227  user=root
...
2019-12-31 19:17:41
178.116.236.42 attackbotsspam
Dec 31 09:11:14 pkdns2 sshd\[15017\]: Invalid user giacomini from 178.116.236.42Dec 31 09:11:16 pkdns2 sshd\[15017\]: Failed password for invalid user giacomini from 178.116.236.42 port 47038 ssh2Dec 31 09:11:46 pkdns2 sshd\[15024\]: Failed password for root from 178.116.236.42 port 49052 ssh2Dec 31 09:12:19 pkdns2 sshd\[15057\]: Invalid user kjs from 178.116.236.42Dec 31 09:12:22 pkdns2 sshd\[15057\]: Failed password for invalid user kjs from 178.116.236.42 port 51096 ssh2Dec 31 09:12:49 pkdns2 sshd\[15066\]: Invalid user vhost from 178.116.236.42
...
2019-12-31 18:59:11
200.133.39.24 attackbotsspam
Automatic report - Banned IP Access
2019-12-31 18:47:56
182.84.125.15 attack
Dec 30 20:33:02 kmh-wmh-003-nbg03 sshd[7205]: Invalid user pi from 182.84.125.15 port 46016
Dec 30 20:33:02 kmh-wmh-003-nbg03 sshd[7203]: Invalid user pi from 182.84.125.15 port 46014
Dec 30 20:33:02 kmh-wmh-003-nbg03 sshd[7205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.84.125.15
Dec 30 20:33:02 kmh-wmh-003-nbg03 sshd[7203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.84.125.15
Dec 30 20:33:04 kmh-wmh-003-nbg03 sshd[7205]: Failed password for invalid user pi from 182.84.125.15 port 46016 ssh2
Dec 30 20:33:05 kmh-wmh-003-nbg03 sshd[7203]: Failed password for invalid user pi from 182.84.125.15 port 46014 ssh2
Dec 30 20:33:05 kmh-wmh-003-nbg03 sshd[7205]: Connection closed by 182.84.125.15 port 46016 [preauth]
Dec 30 20:33:05 kmh-wmh-003-nbg03 sshd[7203]: Connection closed by 182.84.125.15 port 46014 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=182.84
2019-12-31 18:50:07
123.128.92.241 attackspambots
[portscan] tcp/21 [FTP]
[scan/connect: 3 time(s)]
*(RWIN=65535)(12311301)
2019-12-31 19:17:15
174.108.22.16 attackbotsspam
Honeypot attack, port: 5555, PTR: cpe-174-108-22-16.carolina.res.rr.com.
2019-12-31 18:46:37
159.89.194.160 attack
Invalid user oracle from 159.89.194.160 port 48220
2019-12-31 19:03:36
178.62.108.111 attackbots
1079/tcp 1078/tcp 1077/tcp...⊂ [1045/tcp,1079/tcp]
[2019-12-01/30]98pkt,33pt.(tcp)
2019-12-31 19:05:33
94.232.136.126 attackbotsspam
Invalid user nagios from 94.232.136.126 port 3443
2019-12-31 19:11:57

Recently Reported IPs

212.84.102.26 40.16.43.229 37.12.1.55 151.10.16.84
63.53.57.175 189.10.227.153 131.251.74.38 206.74.225.114
48.16.123.147 68.116.38.233 188.164.129.125 43.180.72.140
83.128.20.84 51.83.212.108 57.238.108.94 194.157.39.49
160.210.26.55 88.9.215.35 16.140.226.235 171.45.192.147