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

;; QUESTION SECTION:
;122.19.137.13.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 11:37:13 CST 2025
;; MSG SIZE  rcvd: 106
Host info
13.137.19.122.in-addr.arpa domain name pointer p1168013-ipngn2101hiraide.tochigi.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
13.137.19.122.in-addr.arpa	name = p1168013-ipngn2101hiraide.tochigi.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.189.12.120 attackbotsspam
Automated report (2020-09-01T20:35:18+08:00). Faked user agent detected.
2020-09-01 20:36:48
171.237.98.135 attackbotsspam
Attempted connection to port 445.
2020-09-01 20:24:57
203.171.29.162 attackspam
Unauthorized connection attempt from IP address 203.171.29.162 on Port 445(SMB)
2020-09-01 20:33:30
79.138.8.4 attackbotsspam
Port Scan detected!
...
2020-09-01 20:41:31
82.177.52.73 attackspam
(smtpauth) Failed SMTP AUTH login from 82.177.52.73 (PL/Poland/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-01 08:15:15 plain authenticator failed for ([82.177.52.73]) [82.177.52.73]: 535 Incorrect authentication data (set_id=info@atlaspumpsepahan.com)
2020-09-01 20:31:53
134.236.3.88 attack
Attempted connection to port 445.
2020-09-01 20:25:20
188.124.111.121 attack
Attempted connection to port 445.
2020-09-01 20:20:55
213.33.226.118 attack
malicious Brute-Force reported by https://www.patrick-binder.de
...
2020-09-01 20:17:03
5.57.33.65 attack
20/9/1@01:19:44: FAIL: Alarm-Intrusion address from=5.57.33.65
...
2020-09-01 20:11:07
192.140.28.183 attackbotsspam
(smtpauth) Failed SMTP AUTH login from 192.140.28.183 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-09-01 08:15:22 plain authenticator failed for ([192.140.28.183]) [192.140.28.183]: 535 Incorrect authentication data (set_id=info)
2020-09-01 20:30:47
80.211.59.121 attackbotsspam
Sep  1 14:04:30 markkoudstaal sshd[18691]: Failed password for root from 80.211.59.121 port 40612 ssh2
Sep  1 14:08:36 markkoudstaal sshd[19794]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.59.121
Sep  1 14:08:38 markkoudstaal sshd[19794]: Failed password for invalid user rajeev from 80.211.59.121 port 46138 ssh2
...
2020-09-01 20:21:23
185.74.4.189 attack
2020-09-01T14:44:37+0200 Failed SSH Authentication/Brute Force Attack. (Server 9)
2020-09-01 20:46:13
161.35.140.204 attack
Sep  1 14:35:53 mellenthin sshd[19325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.35.140.204
Sep  1 14:35:55 mellenthin sshd[19325]: Failed password for invalid user hj from 161.35.140.204 port 36540 ssh2
2020-09-01 20:37:04
198.71.239.29 attack
Brute Force
2020-09-01 20:45:03
93.94.223.70 attack
Attempted connection to port 8080.
2020-09-01 20:09:36

Recently Reported IPs

42.120.165.150 241.120.80.71 157.186.49.177 202.214.31.162
155.2.246.228 214.172.106.31 185.162.9.0 192.192.247.25
90.163.104.158 188.193.174.242 185.247.167.101 167.226.246.132
206.8.241.216 122.190.168.221 5.38.123.1 66.253.52.97
122.137.169.224 157.113.9.108 48.148.96.246 222.214.30.15