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: Korea (the Republic of)

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

;; QUESTION SECTION:
;3.38.63.42.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 08:41:22 CST 2025
;; MSG SIZE  rcvd: 103
Host info
42.63.38.3.in-addr.arpa domain name pointer ec2-3-38-63-42.ap-northeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
42.63.38.3.in-addr.arpa	name = ec2-3-38-63-42.ap-northeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
109.194.54.126 attackbotsspam
Invalid user service from 109.194.54.126 port 42108
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.194.54.126
Failed password for invalid user service from 109.194.54.126 port 42108 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.194.54.126  user=root
Failed password for root from 109.194.54.126 port 43504 ssh2
2020-01-19 22:17:11
87.103.114.48 attackbots
Honeypot attack, port: 445, PTR: 48.114.103.87.rev.vodafone.pt.
2020-01-19 22:44:56
218.241.154.197 attackspambots
Unauthorized connection attempt detected from IP address 218.241.154.197 to port 1126
2020-01-19 22:56:00
120.70.99.15 attackbotsspam
Unauthorized connection attempt detected from IP address 120.70.99.15 to port 2220 [J]
2020-01-19 22:16:30
179.109.175.181 attack
Unauthorized connection attempt detected from IP address 179.109.175.181 to port 82 [J]
2020-01-19 22:37:17
178.34.186.50 attackbots
Jan 19 13:58:20 debian-2gb-nbg1-2 kernel: \[1697988.486253\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=178.34.186.50 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=16547 DF PROTO=TCP SPT=9602 DPT=23 WINDOW=14600 RES=0x00 SYN URGP=0
2020-01-19 22:23:53
218.92.0.164 attackspam
$f2bV_matches
2020-01-19 22:23:02
111.230.249.77 attack
$f2bV_matches
2020-01-19 22:52:57
220.130.178.36 attackbotsspam
Unauthorized connection attempt detected from IP address 220.130.178.36 to port 2220 [J]
2020-01-19 22:39:21
186.154.213.42 attackbots
Honeypot attack, port: 445, PTR: mail2.clinicanogales.com.
2020-01-19 22:57:51
60.166.119.59 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2020-01-19 22:50:21
219.77.126.69 attackbots
Honeypot attack, port: 5555, PTR: n219077126069.netvigator.com.
2020-01-19 22:47:02
106.8.85.11 attack
Unauthorized connection attempt detected from IP address 106.8.85.11 to port 23 [J]
2020-01-19 22:54:14
154.93.5.53 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-19 22:36:24
203.218.98.91 attackspam
Honeypot attack, port: 5555, PTR: pcd308091.netvigator.com.
2020-01-19 23:00:58

Recently Reported IPs

6.28.141.134 2.5.239.138 128.229.149.219 175.254.56.227
79.146.175.191 67.162.88.186 63.252.123.248 161.99.93.57
65.225.61.134 144.186.219.84 184.25.90.150 114.248.1.126
235.219.254.175 12.86.125.14 247.104.243.81 219.93.159.27
135.171.82.80 177.24.129.217 124.20.207.4 190.98.53.159