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

;; QUESTION SECTION:
;219.104.114.212.		IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 02 07:02:24 CST 2022
;; MSG SIZE  rcvd: 108
Host info
212.114.104.219.in-addr.arpa domain name pointer nthrsm095212.hrsm.nt.ngn.ppp.infoweb.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.114.104.219.in-addr.arpa	name = nthrsm095212.hrsm.nt.ngn.ppp.infoweb.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
74.121.190.26 attack
\[2019-11-28 15:53:39\] SECURITY\[2765\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-28T15:53:39.224-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="0048627490012",SessionID="0x7f26c4a61d98",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/74.121.190.26/49802",ACLName="no_extension_match"
\[2019-11-28 15:54:36\] SECURITY\[2765\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-28T15:54:36.003-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="00048627490012",SessionID="0x7f26c4a61d98",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/74.121.190.26/49903",ACLName="no_extension_match"
\[2019-11-28 15:55:32\] SECURITY\[2765\] res_security_log.c: SecurityEvent="FailedACL",EventTV="2019-11-28T15:55:32.630-0500",Severity="Error",Service="SIP",EventVersion="1",AccountID="48627490012",SessionID="0x7f26c445f668",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/74.121.190.26/53401",ACLName="no_extension_
2019-11-29 05:06:53
54.70.160.40 attackspambots
Exploit Attempt
2019-11-29 05:10:57
83.151.132.131 attack
Nov 29 03:03:50 webhost01 sshd[10171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.151.132.131
Nov 29 03:03:52 webhost01 sshd[10171]: Failed password for invalid user user from 83.151.132.131 port 34198 ssh2
...
2019-11-29 05:06:27
182.52.90.164 attackspam
Invalid user chocs from 182.52.90.164 port 33942
2019-11-29 05:02:30
5.25.223.4 attackbotsspam
Automatic report - Port Scan Attack
2019-11-29 05:13:29
69.70.67.146 attackspam
Nov 28 17:51:06 firewall sshd[22556]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.70.67.146  user=root
Nov 28 17:51:08 firewall sshd[22556]: Failed password for root from 69.70.67.146 port 24811 ssh2
Nov 28 17:54:04 firewall sshd[22676]: Invalid user kriese from 69.70.67.146
...
2019-11-29 05:22:58
51.83.98.177 attackbots
xmlrpc attack
2019-11-29 05:28:48
89.248.168.202 attackspambots
firewall-block, port(s): 3554/tcp, 3583/tcp, 3595/tcp, 3599/tcp
2019-11-29 05:36:47
180.104.6.189 attackspambots
Brute force attempt
2019-11-29 05:20:17
220.163.116.198 attackspam
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-29 05:07:05
110.36.238.98 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-29 05:07:40
140.143.200.251 attackspam
tried to login illegally to my server.
2019-11-29 05:10:11
193.32.163.44 attackspambots
2019-11-28T20:46:26.929587+01:00 lumpi kernel: [260351.557857] INPUT:DROP:SPAMHAUS_EDROP:IN=eth0 OUT= MAC=52:54:a2:01:a5:04:d2:74:7f:6e:37:e3:08:00 SRC=193.32.163.44 DST=78.46.199.189 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=3836 PROTO=TCP SPT=57310 DPT=33890 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-29 05:19:31
93.189.204.125 attack
19/11/28@09:26:23: FAIL: IoT-Telnet address from=93.189.204.125
...
2019-11-29 05:26:39
58.56.32.238 attackspambots
Tried sshing with brute force.
2019-11-29 05:34:16

Recently Reported IPs

168.254.89.231 204.162.123.115 215.46.178.202 141.197.40.97
196.212.58.97 51.222.173.249 26.4.77.69 110.76.65.224
142.147.39.196 74.182.129.56 88.182.165.219 55.70.6.211
126.141.127.50 55.149.196.144 41.220.118.252 112.197.137.62
148.215.47.20 192.222.65.164 151.79.9.20 151.201.171.216