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: Amsterdam

Region: Noord Holland

Country: The Netherlands

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       45.139.136.0 - 45.150.51.255
CIDR:           45.139.192.0/18, 45.139.136.0/21, 45.150.0.0/19, 45.139.144.0/20, 45.150.32.0/20, 45.140.0.0/14, 45.148.0.0/15, 45.144.0.0/14, 45.139.160.0/19, 45.150.48.0/22
NetName:        RIPE
NetHandle:      NET-45-139-136-0-1
Parent:         NET45 (NET-45-0-0-0-0)
NetType:        Early Registrations, Transferred to RIPE NCC
OriginAS:       
Organization:   RIPE Network Coordination Centre (RIPE)
RegDate:        2014-05-22
Updated:        2025-04-14
Comment:        These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref:            https://rdap.arin.net/registry/ip/45.139.136.0

ResourceLink:  https://apps.db.ripe.net/db-web-ui/query
ResourceLink:  whois.ripe.net


OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:      
PostalCode:     1001EB
Country:        NL
RegDate:        
Updated:        2013-07-29
Ref:            https://rdap.arin.net/registry/entity/RIPE

ReferralServer:  whois.ripe.net
ResourceLink:  https://apps.db.ripe.net/db-web-ui/query

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444 
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    https://rdap.arin.net/registry/entity/RNO29-ARIN

OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName:   Abuse Contact
OrgAbusePhone:  +31205354444 
OrgAbuseEmail:  abuse@ripe.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE3850-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.140.222.144
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8669
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.140.222.144.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Apr 11 09:00:38 CST 2026
;; MSG SIZE  rcvd: 107
Host info
144.222.140.45.in-addr.arpa domain name pointer security.criminalip.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
144.222.140.45.in-addr.arpa	name = security.criminalip.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
104.203.102.245 attackspam
(From eric@talkwithwebvisitor.com) Hi, Eric here with a quick thought about your website neighborhoodchiropractic.net...

I’m on the internet a lot and I look at a lot of business websites.

Like yours, many of them have great content. 

But all too often, they come up short when it comes to engaging and connecting with anyone who visits.

I get it – it’s hard.  Studies show 7 out of 10 people who land on a site, abandon it in moments without leaving even a trace.  You got the eyeball, but nothing else.

Here’s a solution for you…

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  You’ll know immediately they’re interested and you can call them directly to talk with them literally while they’re still on the web looking at your site.

CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works.

It could be huge for your business – and beca
2020-06-11 07:47:04
54.37.136.213 attackspam
2020-06-10T21:56:55.001472server.espacesoutien.com sshd[4624]: Invalid user had from 54.37.136.213 port 43448
2020-06-10T21:56:55.012923server.espacesoutien.com sshd[4624]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.136.213
2020-06-10T21:56:55.001472server.espacesoutien.com sshd[4624]: Invalid user had from 54.37.136.213 port 43448
2020-06-10T21:56:56.686705server.espacesoutien.com sshd[4624]: Failed password for invalid user had from 54.37.136.213 port 43448 ssh2
...
2020-06-11 07:41:07
64.225.58.121 attack
Jun 10 23:24:02 MainVPS sshd[29593]: Invalid user gitlab from 64.225.58.121 port 35012
Jun 10 23:24:02 MainVPS sshd[29593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.225.58.121
Jun 10 23:24:02 MainVPS sshd[29593]: Invalid user gitlab from 64.225.58.121 port 35012
Jun 10 23:24:04 MainVPS sshd[29593]: Failed password for invalid user gitlab from 64.225.58.121 port 35012 ssh2
Jun 10 23:27:11 MainVPS sshd[344]: Invalid user admin from 64.225.58.121 port 36618
...
2020-06-11 07:49:57
79.107.92.141 attack
Automatic report - Banned IP Access
2020-06-11 07:56:20
186.236.22.41 attack
Automatic report - Port Scan Attack
2020-06-11 07:58:56
212.115.53.107 attackbots
Jun 10 21:14:25 h1745522 sshd[22188]: Invalid user admin from 212.115.53.107 port 40892
Jun 10 21:14:25 h1745522 sshd[22188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.115.53.107
Jun 10 21:14:25 h1745522 sshd[22188]: Invalid user admin from 212.115.53.107 port 40892
Jun 10 21:14:26 h1745522 sshd[22188]: Failed password for invalid user admin from 212.115.53.107 port 40892 ssh2
Jun 10 21:18:18 h1745522 sshd[22413]: Invalid user bge from 212.115.53.107 port 39636
Jun 10 21:18:18 h1745522 sshd[22413]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.115.53.107
Jun 10 21:18:18 h1745522 sshd[22413]: Invalid user bge from 212.115.53.107 port 39636
Jun 10 21:18:21 h1745522 sshd[22413]: Failed password for invalid user bge from 212.115.53.107 port 39636 ssh2
Jun 10 21:22:13 h1745522 sshd[22656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.115.53.107  user
...
2020-06-11 07:53:46
184.168.27.111 attackbots
Automatic report - XMLRPC Attack
2020-06-11 08:12:02
78.128.113.114 attack
2020-06-11 01:31:50 dovecot_plain authenticator failed for \(ip-113-114.4vendeta.com.\) \[78.128.113.114\]: 535 Incorrect authentication data \(set_id=info@opso.it\)
2020-06-11 01:31:58 dovecot_plain authenticator failed for \(ip-113-114.4vendeta.com.\) \[78.128.113.114\]: 535 Incorrect authentication data
2020-06-11 01:32:08 dovecot_plain authenticator failed for \(ip-113-114.4vendeta.com.\) \[78.128.113.114\]: 535 Incorrect authentication data
2020-06-11 01:32:14 dovecot_plain authenticator failed for \(ip-113-114.4vendeta.com.\) \[78.128.113.114\]: 535 Incorrect authentication data
2020-06-11 01:32:27 dovecot_plain authenticator failed for \(ip-113-114.4vendeta.com.\) \[78.128.113.114\]: 535 Incorrect authentication data
2020-06-11 07:35:50
175.24.107.68 attackspam
Jun 11 01:03:15 minden010 sshd[11170]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.107.68
Jun 11 01:03:17 minden010 sshd[11170]: Failed password for invalid user kynaa from 175.24.107.68 port 60408 ssh2
Jun 11 01:08:46 minden010 sshd[12847]: Failed password for root from 175.24.107.68 port 44858 ssh2
...
2020-06-11 07:52:23
46.38.150.188 attackbots
Jun 11 01:55:07 srv01 postfix/smtpd\[2216\]: warning: unknown\[46.38.150.188\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 11 01:55:42 srv01 postfix/smtpd\[2216\]: warning: unknown\[46.38.150.188\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 11 01:55:43 srv01 postfix/smtpd\[9532\]: warning: unknown\[46.38.150.188\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 11 01:55:43 srv01 postfix/smtpd\[2215\]: warning: unknown\[46.38.150.188\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jun 11 01:56:44 srv01 postfix/smtpd\[7773\]: warning: unknown\[46.38.150.188\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-06-11 08:07:51
54.160.125.46 attack
Jun 11 02:58:47 our-server-hostname sshd[8214]: Invalid user ssbot from 54.160.125.46
Jun 11 02:58:47 our-server-hostname sshd[8214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-54-160-125-46.compute-1.amazonaws.com 
Jun 11 02:58:49 our-server-hostname sshd[8214]: Failed password for invalid user ssbot from 54.160.125.46 port 34038 ssh2
Jun 11 03:17:34 our-server-hostname sshd[11956]: Invalid user test from 54.160.125.46
Jun 11 03:17:34 our-server-hostname sshd[11956]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-54-160-125-46.compute-1.amazonaws.com 
Jun 11 03:17:36 our-server-hostname sshd[11956]: Failed password for invalid user test from 54.160.125.46 port 54288 ssh2
Jun 11 03:20:04 our-server-hostname sshd[12437]: Invalid user 1415926 from 54.160.125.46
Jun 11 03:20:04 our-server-hostname sshd[12437]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=........
-------------------------------
2020-06-11 07:55:08
185.74.4.110 attackspambots
Jun 10 23:59:34 fhem-rasp sshd[18979]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.74.4.110  user=root
Jun 10 23:59:36 fhem-rasp sshd[18979]: Failed password for root from 185.74.4.110 port 36816 ssh2
...
2020-06-11 07:54:15
178.62.214.85 attackbots
Jun 10 21:22:33 vmi345603 sshd[17793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.214.85
Jun 10 21:22:34 vmi345603 sshd[17793]: Failed password for invalid user jqd from 178.62.214.85 port 43240 ssh2
...
2020-06-11 07:40:22
5.34.183.113 attack
2020-06-10T23:49:25.316924Z a12cc27c3534 New connection: 5.34.183.113:48836 (172.17.0.3:2222) [session: a12cc27c3534]
2020-06-11T00:00:36.995490Z 738e72c32b74 New connection: 5.34.183.113:35618 (172.17.0.3:2222) [session: 738e72c32b74]
2020-06-11 08:04:16
185.220.101.204 attackspambots
SSH Invalid Login
2020-06-11 08:12:48

Recently Reported IPs

47.128.122.93 121.234.219.183 2606:4700:10::6816:367 2606:4700:10::6816:4546
2606:4700:10::6816:443d 2606:4700:10::6814:4960 2606:4700:10::6816:1808 195.140.214.23
147.185.133.157 147.185.132.16 8.216.5.206 198.176.55.171
14.207.194.38 2606:4700:10::ac43:1618 2606:4700:10::6814:9029 2606:4700:10::6814:4416
55.107.223.175 13.235.54.224 112.121.183.130 163.32.18.254