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

;; QUESTION SECTION:
;45.48.154.56.			IN	A

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

;; Query time: 166 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 23 03:43:59 CST 2022
;; MSG SIZE  rcvd: 105
Host info
56.154.48.45.in-addr.arpa domain name pointer cpe-45-48-154-56.socal.res.rr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
56.154.48.45.in-addr.arpa	name = cpe-45-48-154-56.socal.res.rr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
123.179.7.126 attackspambots
Unauthorized connection attempt detected from IP address 123.179.7.126 to port 8080 [J]
2020-01-22 08:08:26
65.98.111.218 botsattack
Jan 22 00:03:35 s2 sshd[30879]: reverse mapping checking getaddrinfo for atalanta.umpi.edu [65.98.111.218] failed - POSSIBLE BREAK-IN ATTEMPT!
Jan 22 00:03:35 s2 sshd[30879]: Invalid user twintown from 65.98.111.218
Jan 22 00:03:35 s2 sshd[30879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=65.98.111.218
Jan 22 00:03:37 s2 sshd[30879]: Failed password for invalid user twintown from 65.98.111.218 port 43018 ssh2
Jan 22 00:03:37 s2 sshd[30879]: Received disconnect from 65.98.111.218: 11: Bye Bye [preauth]
2020-01-22 08:07:08
78.187.174.135 attackbots
Unauthorized connection attempt detected from IP address 78.187.174.135 to port 80 [J]
2020-01-22 07:52:01
1.244.109.199 attackspambots
Unauthorized connection attempt detected from IP address 1.244.109.199 to port 2220 [J]
2020-01-22 07:57:47
197.35.12.149 attackbotsspam
Unauthorized connection attempt detected from IP address 197.35.12.149 to port 23 [J]
2020-01-22 08:00:44
111.224.234.121 attack
Unauthorized connection attempt detected from IP address 111.224.234.121 to port 3389 [J]
2020-01-22 08:10:27
150.109.170.192 attack
Unauthorized connection attempt detected from IP address 150.109.170.192 to port 6103 [J]
2020-01-22 08:06:49
112.26.44.112 attackbots
Unauthorized connection attempt detected from IP address 112.26.44.112 to port 2220 [J]
2020-01-22 07:46:35
124.88.112.133 attackbotsspam
Unauthorized connection attempt detected from IP address 124.88.112.133 to port 9999 [T]
2020-01-22 08:07:46
190.98.70.51 attack
Unauthorized connection attempt detected from IP address 190.98.70.51 to port 22 [J]
2020-01-22 07:36:42
122.116.11.86 attackspambots
Unauthorized connection attempt detected from IP address 122.116.11.86 to port 4567 [J]
2020-01-22 07:45:06
109.165.234.24 attackspam
Unauthorized connection attempt detected from IP address 109.165.234.24 to port 1433 [J]
2020-01-22 07:47:54
104.52.29.49 attackspam
Unauthorized connection attempt detected from IP address 104.52.29.49 to port 4567 [J]
2020-01-22 08:12:21
150.116.35.4 attackspambots
Unauthorized connection attempt detected from IP address 150.116.35.4 to port 23 [J]
2020-01-22 08:06:34
182.138.137.253 attackspam
Unauthorized connection attempt detected from IP address 182.138.137.253 to port 8118 [J]
2020-01-22 07:39:15

Recently Reported IPs

104.18.28.40 104.18.28.8 104.18.29.133 104.18.29.185
104.18.29.36 104.18.29.8 104.18.3.103 104.18.3.111
104.18.3.24 192.27.8.126 104.18.3.46 104.18.30.187
104.18.30.223 104.18.30.41 212.155.60.85 104.18.30.56
104.18.30.88 104.18.31.187 104.18.31.223 104.18.31.41