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

;; QUESTION SECTION:
;210.117.74.42.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 25 12:34:25 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 42.74.117.210.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 42.74.117.210.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.82.64.134 attackbots
SSH brute-forcing, ban triggered
2020-02-27 06:25:29
114.32.186.34 attackbots
scan z
2020-02-27 06:41:15
185.234.217.164 attackspambots
Feb  4 10:03:33 mail postfix/smtpd[3212]: warning: unknown[185.234.217.164]: SASL LOGIN authentication failed: authentication failure
2020-02-27 06:29:07
83.1.97.247 attackbotsspam
Automatic report - Port Scan Attack
2020-02-27 06:37:40
223.223.205.114 attackbots
firewall-block, port(s): 1433/tcp
2020-02-27 06:43:13
45.134.179.247 attack
Feb 26 23:22:19 debian-2gb-nbg1-2 kernel: \[5014934.186943\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.247 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=40312 PROTO=TCP SPT=53453 DPT=45120 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-27 06:22:49
101.71.2.165 attackbotsspam
Feb 26 22:38:58 Ubuntu-1404-trusty-64-minimal sshd\[8848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165  user=postfix
Feb 26 22:38:59 Ubuntu-1404-trusty-64-minimal sshd\[8848\]: Failed password for postfix from 101.71.2.165 port 13227 ssh2
Feb 26 22:50:07 Ubuntu-1404-trusty-64-minimal sshd\[15567\]: Invalid user ns2c from 101.71.2.165
Feb 26 22:50:07 Ubuntu-1404-trusty-64-minimal sshd\[15567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.165
Feb 26 22:50:09 Ubuntu-1404-trusty-64-minimal sshd\[15567\]: Failed password for invalid user ns2c from 101.71.2.165 port 13234 ssh2
2020-02-27 06:49:48
222.186.175.169 attackspambots
Feb 26 19:49:07 firewall sshd[27441]: Failed password for root from 222.186.175.169 port 46060 ssh2
Feb 26 19:49:20 firewall sshd[27441]: error: maximum authentication attempts exceeded for root from 222.186.175.169 port 46060 ssh2 [preauth]
Feb 26 19:49:20 firewall sshd[27441]: Disconnecting: Too many authentication failures [preauth]
...
2020-02-27 06:51:49
122.155.174.36 attackspambots
Feb 26 12:24:42 eddieflores sshd\[27033\]: Invalid user mapred from 122.155.174.36
Feb 26 12:24:42 eddieflores sshd\[27033\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.174.36
Feb 26 12:24:43 eddieflores sshd\[27033\]: Failed password for invalid user mapred from 122.155.174.36 port 44686 ssh2
Feb 26 12:31:32 eddieflores sshd\[27560\]: Invalid user sgi from 122.155.174.36
Feb 26 12:31:32 eddieflores sshd\[27560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.155.174.36
2020-02-27 06:34:17
219.85.139.237 attackbotsspam
Automatic report - Port Scan Attack
2020-02-27 06:42:56
41.38.97.118 attackspambots
Automatic report - Banned IP Access
2020-02-27 06:46:05
104.238.36.190 attackspam
[2020-02-26 22:30:45] NOTICE[23721] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '' failed for '104.238.36.190:54500' (callid: 246606734-192116153-1572652886) - Failed to authenticate
[2020-02-26 22:30:45] SECURITY[1911] res_security_log.c: SecurityEvent="ChallengeResponseFailed",EventTV="2020-02-26T22:30:45.114+0100",Severity="Error",Service="PJSIP",EventVersion="1",AccountID="",SessionID="246606734-192116153-1572652886",LocalAddress="IPV4/UDP/185.118.197.148/5060",RemoteAddress="IPV4/UDP/104.238.36.190/54500",Challenge="1582752644/829faa3b96ccb6c1f36096416c29afc3",Response="5c15519ac8b1050e7da1dbd30a4852cd",ExpectedResponse=""
[2020-02-26 22:30:45] NOTICE[11886] res_pjsip/pjsip_distributor.c: Request 'REGISTER' from '' failed for '104.238.36.190:54500' (callid: 246606734-192116153-1572652886) - Failed to authenticate
[2020-02-26 22:30:45] SECURITY[1911] res_security_log.c: SecurityEvent="ChallengeResponseFailed",EventTV="2020-02-26T22:3
2020-02-27 06:31:30
112.85.42.174 attackspambots
Feb 26 19:15:18 firewall sshd[26558]: Failed password for root from 112.85.42.174 port 20258 ssh2
Feb 26 19:15:33 firewall sshd[26558]: error: maximum authentication attempts exceeded for root from 112.85.42.174 port 20258 ssh2 [preauth]
Feb 26 19:15:33 firewall sshd[26558]: Disconnecting: Too many authentication failures [preauth]
...
2020-02-27 06:17:43
185.200.118.66 attackspam
" "
2020-02-27 06:24:58
162.243.133.88 attackspambots
Automatic report - Port Scan Attack
2020-02-27 06:35:21

Recently Reported IPs

220.82.231.103 28.234.186.238 36.13.143.30 131.176.57.15
96.38.169.163 194.159.167.36 255.216.75.230 165.120.62.148
86.139.58.88 121.189.197.184 67.203.123.150 255.238.190.84
220.107.120.123 17.92.144.162 191.138.126.63 48.244.82.238
120.161.135.89 168.207.183.50 191.147.112.239 152.25.132.255