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: United States of America (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 <<>> 149.125.146.80
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19218
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;149.125.146.80.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 10:37:40 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 80.146.125.149.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 149.125.146.80.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
188.190.70.110 attackbots
scan z
2019-12-02 01:48:25
177.85.3.69 attackbots
Fail2Ban Ban Triggered
2019-12-02 01:51:21
3.115.189.184 attack
Message ID	
Created at:	Sun, Dec 1, 2019 at 8:37 AM (Delivered after -2409 seconds)
From:	Alert 
Subject:	(08) Your account will be closed in 10 Hours
SPF:	PASS with IP 3.115.189.184
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: best guess record for domain of uwbqoczr@n2vs6---n2vs6----us-west-2.compute.amazonaws.com designates 3.115.189.184 as permitted sender) smtp.mailfrom=UwBQOcZr@n2vs6---n2vs6----us-west-2.compute.amazonaws.com
Return-Path: 
Received: from cyborganic.com (ec2-3-115-189-184.ap-northeast-1.compute.amazonaws.com. [3.115.189.184])
        by mx.google.com with ESMTP id t142si9144246oih.242.2019.12.01.05.57.37
2019-12-02 01:53:56
192.144.225.150 attack
5x Failed Password
2019-12-02 02:01:09
104.236.61.100 attack
2019-11-30 20:30:47 server sshd[29921]: Failed password for invalid user arsenia from 104.236.61.100 port 42289 ssh2
2019-12-02 01:56:43
49.149.103.196 attack
Unauthorised access (Dec  1) SRC=49.149.103.196 LEN=52 TTL=117 ID=6555 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-02 02:23:19
203.115.99.150 attackspambots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-02 02:20:41
177.69.118.197 attack
Dec  1 18:05:39 pkdns2 sshd\[32955\]: Invalid user dopke from 177.69.118.197Dec  1 18:05:40 pkdns2 sshd\[32955\]: Failed password for invalid user dopke from 177.69.118.197 port 50976 ssh2Dec  1 18:09:20 pkdns2 sshd\[33085\]: Invalid user changeme from 177.69.118.197Dec  1 18:09:22 pkdns2 sshd\[33085\]: Failed password for invalid user changeme from 177.69.118.197 port 42269 ssh2Dec  1 18:12:42 pkdns2 sshd\[33217\]: Invalid user 123123 from 177.69.118.197Dec  1 18:12:44 pkdns2 sshd\[33217\]: Failed password for invalid user 123123 from 177.69.118.197 port 33809 ssh2
...
2019-12-02 02:03:37
52.37.208.6 attackspambots
As always with amazon web services
2019-12-02 02:20:22
168.232.198.18 attack
Dec  1 18:04:44 icinga sshd[22996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.198.18
Dec  1 18:04:46 icinga sshd[22996]: Failed password for invalid user t from 168.232.198.18 port 33908 ssh2
...
2019-12-02 02:04:09
118.24.104.152 attackspambots
2019-12-01T08:23:10.9852631495-001 sshd\[64536\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.104.152
2019-12-01T08:23:12.6034131495-001 sshd\[64536\]: Failed password for invalid user admin from 118.24.104.152 port 56306 ssh2
2019-12-01T09:26:14.0674991495-001 sshd\[1820\]: Invalid user messreni from 118.24.104.152 port 42866
2019-12-01T09:26:14.0744811495-001 sshd\[1820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.104.152
2019-12-01T09:26:15.8378791495-001 sshd\[1820\]: Failed password for invalid user messreni from 118.24.104.152 port 42866 ssh2
2019-12-01T09:30:25.0397771495-001 sshd\[1967\]: Invalid user misael from 118.24.104.152 port 45738
...
2019-12-02 02:13:51
104.236.31.227 attack
SSH Brute Force, server-1 sshd[9451]: Failed password for invalid user Carolina@321 from 104.236.31.227 port 41920 ssh2
2019-12-02 02:21:11
147.50.3.30 attackbots
Dec  1 08:01:41 hpm sshd\[8767\]: Invalid user server from 147.50.3.30
Dec  1 08:01:41 hpm sshd\[8767\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.50.3.30
Dec  1 08:01:43 hpm sshd\[8767\]: Failed password for invalid user server from 147.50.3.30 port 15807 ssh2
Dec  1 08:05:37 hpm sshd\[9138\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=147.50.3.30  user=root
Dec  1 08:05:39 hpm sshd\[9138\]: Failed password for root from 147.50.3.30 port 32743 ssh2
2019-12-02 02:17:55
181.177.250.9 attack
12/01/2019-09:41:12.248641 181.177.250.9 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-02 02:20:56
110.11.227.225 attack
Port 1433 Scan
2019-12-02 02:01:52

Recently Reported IPs

66.71.117.208 29.171.240.207 62.91.178.86 36.108.111.38
39.249.32.141 54.155.215.73 63.92.114.68 127.194.102.7
135.246.255.96 76.129.153.51 126.37.9.36 249.161.177.117
129.190.161.123 187.5.130.217 29.215.67.72 229.152.253.27
185.31.48.161 152.130.19.217 89.115.100.136 123.93.199.50