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

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

;; QUESTION SECTION:
;40.99.50.48.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 26 15:17:50 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 48.50.99.40.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 48.50.99.40.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
164.132.111.76 attackspambots
Invalid user XiaB from 164.132.111.76 port 53922
2020-03-11 10:15:41
46.17.175.21 attackbots
WordPress wp-login brute force :: 46.17.175.21 0.068 BYPASS [10/Mar/2020:18:08:11  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2252 "-" "-"
2020-03-11 10:14:05
46.101.174.188 attackbots
SSH_scan
2020-03-11 09:43:03
46.174.191.31 attackbotsspam
Scanning random ports - tries to find possible vulnerable services
2020-03-11 09:54:38
198.108.67.56 attackspam
8819/tcp 8854/tcp 3056/tcp...
[2020-01-11/03-09]102pkt,96pt.(tcp)
2020-03-11 10:07:25
220.166.161.99 attackspambots
Unauthorized connection attempt detected from IP address 220.166.161.99 to port 445
2020-03-11 10:08:28
143.208.135.240 attackspambots
Mar 10 19:08:46 lnxded64 sshd[30382]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=143.208.135.240
2020-03-11 09:45:01
45.227.255.119 attack
Mar1103:15:50server6sshd[19172]:refusedconnectfrom45.227.255.119\(45.227.255.119\)Mar1103:15:55server6sshd[19178]:refusedconnectfrom45.227.255.119\(45.227.255.119\)Mar1103:16:00server6sshd[19185]:refusedconnectfrom45.227.255.119\(45.227.255.119\)Mar1103:16:06server6sshd[19205]:refusedconnectfrom45.227.255.119\(45.227.255.119\)Mar1103:16:11server6sshd[19215]:refusedconnectfrom45.227.255.119\(45.227.255.119\)
2020-03-11 10:25:02
92.118.37.74 attackbots
Mar 11 00:32:08 debian-2gb-nbg1-2 kernel: \[6142273.885377\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.118.37.74 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=3428 PROTO=TCP SPT=58558 DPT=6231 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-11 09:53:52
45.143.223.222 attackspam
Brute force attack stopped by firewall
2020-03-11 09:50:48
111.93.4.174 attackbots
Mar 11 02:07:01 sip sshd[16457]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.4.174
Mar 11 02:07:03 sip sshd[16457]: Failed password for invalid user acadmin from 111.93.4.174 port 41214 ssh2
Mar 11 02:20:11 sip sshd[19802]: Failed password for root from 111.93.4.174 port 36210 ssh2
2020-03-11 09:55:40
110.10.174.179 attackspambots
IP blocked
2020-03-11 09:45:30
82.130.211.206 attackbots
Unauthorized connection attempt detected from IP address 82.130.211.206 to port 80
2020-03-11 09:49:43
36.229.97.147 attack
Unauthorized connection attempt from IP address 36.229.97.147 on Port 445(SMB)
2020-03-11 10:22:57
49.232.146.216 attack
Too many connections or unauthorized access detected from Arctic banned ip
2020-03-11 09:50:14

Recently Reported IPs

142.192.252.111 196.231.244.168 8.106.34.231 204.131.73.94
49.129.37.141 193.209.73.126 160.215.240.50 227.19.116.152
180.223.133.221 98.126.5.209 179.102.60.116 202.139.143.64
164.149.67.47 229.47.237.163 129.82.206.133 118.193.58.20
142.189.150.177 169.67.121.193 132.108.168.21 13.81.131.235