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

;; QUESTION SECTION:
;148.72.254.242.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:45:27 CST 2022
;; MSG SIZE  rcvd: 107
Host info
242.254.72.148.in-addr.arpa domain name pointer ip-148-72-254-242.ip.secureserver.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
242.254.72.148.in-addr.arpa	name = ip-148-72-254-242.ip.secureserver.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
199.195.251.227 attackspambots
Dec 15 12:22:53 tdfoods sshd\[2304\]: Invalid user rieder from 199.195.251.227
Dec 15 12:22:53 tdfoods sshd\[2304\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.251.227
Dec 15 12:22:55 tdfoods sshd\[2304\]: Failed password for invalid user rieder from 199.195.251.227 port 59292 ssh2
Dec 15 12:29:42 tdfoods sshd\[2939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.195.251.227  user=root
Dec 15 12:29:44 tdfoods sshd\[2939\]: Failed password for root from 199.195.251.227 port 38886 ssh2
2019-12-16 06:48:31
181.48.29.35 attack
SSH Brute Force, server-1 sshd[20386]: Failed password for invalid user alma01 from 181.48.29.35 port 55974 ssh2
2019-12-16 07:03:03
116.255.190.144 attackbots
1433/tcp 1433/tcp 1433/tcp...
[2019-10-27/12-15]5pkt,1pt.(tcp)
2019-12-16 07:07:29
87.246.7.34 attack
Dec 15 23:48:03 webserver postfix/smtpd\[4267\]: warning: unknown\[87.246.7.34\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 15 23:48:32 webserver postfix/smtpd\[4267\]: warning: unknown\[87.246.7.34\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 15 23:49:03 webserver postfix/smtpd\[4220\]: warning: unknown\[87.246.7.34\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 15 23:49:34 webserver postfix/smtpd\[4267\]: warning: unknown\[87.246.7.34\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 15 23:50:03 webserver postfix/smtpd\[4267\]: warning: unknown\[87.246.7.34\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-16 07:02:15
157.230.119.200 attackbotsspam
$f2bV_matches
2019-12-16 06:57:47
184.105.139.87 attackspambots
389/tcp 30005/tcp 4786/tcp...
[2019-10-14/12-15]13pkt,9pt.(tcp),1pt.(udp)
2019-12-16 06:42:39
121.7.25.86 attack
5432/tcp 5432/tcp 5432/tcp
[2019-10-22/12-15]3pkt
2019-12-16 06:58:04
51.159.59.241 attack
51.159.59.241 was recorded 17 times by 17 hosts attempting to connect to the following ports: 5683. Incident counter (4h, 24h, all-time): 17, 59, 426
2019-12-16 06:35:04
49.233.153.194 attackspam
Dec 16 00:03:26 vps647732 sshd[21527]: Failed password for root from 49.233.153.194 port 52042 ssh2
...
2019-12-16 07:16:53
188.166.5.84 attackbotsspam
Dec 15 22:10:53 game-panel sshd[18172]: Failed password for sync from 188.166.5.84 port 53846 ssh2
Dec 15 22:15:55 game-panel sshd[18316]: Failed password for root from 188.166.5.84 port 33314 ssh2
Dec 15 22:20:49 game-panel sshd[18504]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.5.84
2019-12-16 06:32:31
72.52.128.192 attackbots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2019-12-16 06:47:59
45.55.136.206 attackbots
Invalid user emc from 45.55.136.206 port 33328
2019-12-16 06:46:03
192.64.86.92 attack
192.64.86.92 was recorded 5 times by 3 hosts attempting to connect to the following ports: 5060,9060. Incident counter (4h, 24h, all-time): 5, 39, 390
2019-12-16 06:47:07
41.207.182.133 attack
Invalid user malaclypse from 41.207.182.133 port 43730
2019-12-16 07:02:49
149.56.100.237 attack
Dec 15 23:47:33 ovpn sshd\[4412\]: Invalid user petrillo from 149.56.100.237
Dec 15 23:47:33 ovpn sshd\[4412\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.100.237
Dec 15 23:47:35 ovpn sshd\[4412\]: Failed password for invalid user petrillo from 149.56.100.237 port 45812 ssh2
Dec 15 23:53:01 ovpn sshd\[5681\]: Invalid user shanay from 149.56.100.237
Dec 15 23:53:01 ovpn sshd\[5681\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.100.237
2019-12-16 07:00:09

Recently Reported IPs

148.72.254.110 148.72.255.122 148.72.255.147 148.72.255.181
148.72.255.108 148.72.26.239 148.72.255.167 148.72.27.189
148.72.26.62 148.72.27.234 148.72.27.83 148.72.27.238
148.72.27.89 148.72.28.110 148.72.3.23 148.72.29.66
148.72.31.143 148.72.30.176 148.72.48.93 148.72.3.78