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

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.28.46.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26518
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;149.28.46.48.			IN	A

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

;; Query time: 133 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 14:46:22 CST 2022
;; MSG SIZE  rcvd: 105
Host info
48.46.28.149.in-addr.arpa domain name pointer 149.28.46.48.vultr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
48.46.28.149.in-addr.arpa	name = 149.28.46.48.vultr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
94.11.130.1 attackspambots
DATE:2020-02-21 14:15:24, IP:94.11.130.1, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-02-22 00:23:04
139.162.110.42 attackbotsspam
suspicious action Fri, 21 Feb 2020 10:16:34 -0300
2020-02-22 00:54:40
2.32.72.117 attackbotsspam
Feb 21 14:16:57 debian-2gb-nbg1-2 kernel: \[4550225.782698\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=2.32.72.117 DST=195.201.40.59 LEN=40 TOS=0x08 PREC=0x00 TTL=48 ID=26608 PROTO=TCP SPT=39150 DPT=81 WINDOW=1460 RES=0x00 SYN URGP=0
2020-02-22 00:42:01
196.52.43.56 attack
firewall-block, port(s): 6001/tcp
2020-02-22 00:39:17
190.129.47.148 attack
Feb 21 15:39:25 cp sshd[16708]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.129.47.148
2020-02-22 00:29:19
122.51.81.247 attack
suspicious action Fri, 21 Feb 2020 10:16:22 -0300
2020-02-22 01:02:03
216.218.209.9 attackspambots
Unauthorized connection attempt detected from IP address 216.218.209.9 to port 3389
2020-02-22 00:26:28
95.110.229.194 attackspam
Feb 21 14:16:53 vmd17057 sshd[26823]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.110.229.194 
Feb 21 14:16:55 vmd17057 sshd[26823]: Failed password for invalid user student from 95.110.229.194 port 38984 ssh2
...
2020-02-22 00:44:18
190.145.224.18 attackspam
SSH/22 MH Probe, BF, Hack -
2020-02-22 00:37:27
54.200.182.16 attackspambots
02/21/2020-17:53:31.550968 54.200.182.16 Protocol: 6 SURICATA TLS invalid record/traffic
2020-02-22 00:58:52
202.29.33.74 attackspambots
Automatic report - Banned IP Access
2020-02-22 01:02:36
222.186.175.23 attackspambots
Feb 21 13:41:39 firewall sshd[4791]: Failed password for root from 222.186.175.23 port 43867 ssh2
Feb 21 13:41:42 firewall sshd[4791]: Failed password for root from 222.186.175.23 port 43867 ssh2
Feb 21 13:41:44 firewall sshd[4791]: Failed password for root from 222.186.175.23 port 43867 ssh2
...
2020-02-22 00:42:41
45.143.220.212 attackbots
Port scan on 3 port(s): 15060 25060 54600
2020-02-22 00:56:42
185.209.0.74 attackbots
RDP Bruteforce
2020-02-22 01:07:19
134.209.18.220 attackbotsspam
Feb 21 15:48:09 plex sshd[12196]: Invalid user ftp from 134.209.18.220 port 50772
2020-02-22 00:46:51

Recently Reported IPs

149.255.230.23 149.3.73.242 149.28.183.149 149.72.125.130
149.56.108.97 149.56.10.120 149.56.7.190 149.56.78.144
149.72.128.32 149.72.194.53 149.72.207.42 149.34.22.195
149.56.242.170 149.72.37.212 149.81.166.139 15.152.1.230
15.152.106.11 15.152.111.183 15.152.105.109 15.152.110.70