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

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

;; QUESTION SECTION:
;178.29.149.48.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 14:55:55 CST 2025
;; MSG SIZE  rcvd: 106
Host info
48.149.29.178.in-addr.arpa domain name pointer c-b21d9530-74736162.cust.telenor.se.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
48.149.29.178.in-addr.arpa	name = c-b21d9530-74736162.cust.telenor.se.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
182.122.72.68 attackspambots
Sep  2 00:35:08 ns382633 sshd\[8103\]: Invalid user atul from 182.122.72.68 port 5170
Sep  2 00:35:08 ns382633 sshd\[8103\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.122.72.68
Sep  2 00:35:11 ns382633 sshd\[8103\]: Failed password for invalid user atul from 182.122.72.68 port 5170 ssh2
Sep  2 00:42:52 ns382633 sshd\[9643\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.122.72.68  user=root
Sep  2 00:42:54 ns382633 sshd\[9643\]: Failed password for root from 182.122.72.68 port 46430 ssh2
2020-09-02 06:50:52
224.0.0.252 botsattackproxy
there are unmediated big problems with this ip range still, in someway utilising bt tv stream packets unbeknowing to bt home hub wifi customers. devices become host servers and use of US at&t proxy ip's on some home hub locations routing other traffic. BT do not use proxy's on home hub connections
2020-09-02 06:23:55
184.105.139.89 spambotsattackproxy
malware
https://freetexthost.net/wEReKhz
2020-09-02 06:29:16
112.206.78.249 attack
"XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES:
2020-09-02 06:38:11
69.119.85.43 attackspam
(sshd) Failed SSH login from 69.119.85.43 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  1 21:26:31 server sshd[22265]: Invalid user admin from 69.119.85.43
Sep  1 21:26:33 server sshd[22265]: Failed password for invalid user admin from 69.119.85.43 port 48878 ssh2
Sep  1 21:31:03 server sshd[22753]: Failed password for ftp from 69.119.85.43 port 45744 ssh2
Sep  1 21:34:37 server sshd[23143]: Invalid user ftp-user from 69.119.85.43
Sep  1 21:34:39 server sshd[23143]: Failed password for invalid user ftp-user from 69.119.85.43 port 34062 ssh2
2020-09-02 06:30:13
184.168.131.241 spamattack
makware host
2020-09-02 06:25:17
103.96.220.115 attackbots
Sep  1 23:59:12 ns382633 sshd\[1812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.96.220.115  user=root
Sep  1 23:59:14 ns382633 sshd\[1812\]: Failed password for root from 103.96.220.115 port 55696 ssh2
Sep  2 00:02:34 ns382633 sshd\[2502\]: Invalid user logger from 103.96.220.115 port 40842
Sep  2 00:02:34 ns382633 sshd\[2502\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.96.220.115
Sep  2 00:02:35 ns382633 sshd\[2502\]: Failed password for invalid user logger from 103.96.220.115 port 40842 ssh2
2020-09-02 06:27:52
159.65.142.192 attackbots
Sep  1 22:18:43 rush sshd[6985]: Failed password for root from 159.65.142.192 port 37160 ssh2
Sep  1 22:22:24 rush sshd[7047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.142.192
Sep  1 22:22:26 rush sshd[7047]: Failed password for invalid user ljq from 159.65.142.192 port 37954 ssh2
...
2020-09-02 06:32:20
85.215.2.227 attack
3306
2020-09-02 06:43:11
218.92.0.224 attack
Failed password for root from 218.92.0.224 port 29862 ssh2
Failed password for root from 218.92.0.224 port 29862 ssh2
Failed password for root from 218.92.0.224 port 29862 ssh2
Failed password for root from 218.92.0.224 port 29862 ssh2
2020-09-02 06:16:16
51.79.86.177 attack
Sep  1 23:28:46 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2
Sep  1 23:28:46 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2
Sep  1 23:28:48 cp sshd[4119]: Failed password for root from 51.79.86.177 port 60240 ssh2
2020-09-02 06:21:09
37.194.122.6 attack
port scan and connect, tcp 1433 (ms-sql-s)
2020-09-02 06:31:03
105.107.151.28 attackspam
"XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES:
2020-09-02 06:32:08
119.167.182.18 attackbots
Attempted connection to port 3306.
2020-09-02 06:31:53
103.254.198.67 attackspambots
Jun 27 04:13:24 server sshd[18952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.198.67
Jun 27 04:13:26 server sshd[18952]: Failed password for invalid user server from 103.254.198.67 port 42932 ssh2
Jun 27 04:28:30 server sshd[19503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.254.198.67  user=root
Jun 27 04:28:32 server sshd[19503]: Failed password for invalid user root from 103.254.198.67 port 43894 ssh2
2020-09-02 06:17:56

Recently Reported IPs

88.42.140.1 167.219.245.206 194.13.216.130 3.177.139.160
243.68.149.76 222.33.53.134 139.82.16.85 82.124.169.152
95.199.87.181 204.88.111.50 25.31.209.53 252.7.13.251
140.246.105.86 237.182.114.62 103.177.165.68 221.21.132.227
75.60.41.39 152.127.167.23 203.217.60.129 53.149.99.197