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

;; QUESTION SECTION:
;153.148.40.13.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 18:22:41 CST 2025
;; MSG SIZE  rcvd: 106
Host info
13.40.148.153.in-addr.arpa domain name pointer p361013-omed01.tokyo.ocn.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
13.40.148.153.in-addr.arpa	name = p361013-omed01.tokyo.ocn.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.173.226 attack
Jan3115:34:20server6sshd[9490]:refusedconnectfrom222.186.173.226\(222.186.173.226\)Jan3115:34:20server6sshd[9491]:refusedconnectfrom222.186.173.226\(222.186.173.226\)Jan3115:34:21server6sshd[9492]:refusedconnectfrom222.186.173.226\(222.186.173.226\)Jan3115:34:21server6sshd[9493]:refusedconnectfrom222.186.173.226\(222.186.173.226\)Jan3116:07:00server6sshd[11971]:refusedconnectfrom222.186.173.226\(222.186.173.226\)
2020-01-31 23:07:56
1.179.185.50 attackspam
Invalid user info from 1.179.185.50 port 32926
2020-01-31 23:26:10
93.171.235.248 attack
TCP Port Scanning
2020-01-31 23:21:28
104.236.250.88 attackspambots
Invalid user jia from 104.236.250.88 port 43672
2020-01-31 23:07:00
106.12.193.169 attackspambots
Invalid user mit from 106.12.193.169 port 50176
2020-01-31 23:46:51
209.95.136.194 attackbotsspam
DATE:2020-01-31 12:10:44, IP:209.95.136.194, PORT:ssh SSH brute force auth on honeypot server (epe-honey1-hq)
2020-01-31 23:31:01
49.146.40.183 attackspam
20/1/31@06:16:07: FAIL: Alarm-Network address from=49.146.40.183
...
2020-01-31 23:12:03
1.161.11.55 attack
TCP Port Scanning
2020-01-31 23:10:05
188.190.221.7 attackbots
Lines containing failures of 188.190.221.7
Jan 31 09:30:06 MAKserver06 sshd[29418]: Invalid user admin from 188.190.221.7 port 7678
Jan 31 09:30:06 MAKserver06 sshd[29418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.190.221.7 
Jan 31 09:30:08 MAKserver06 sshd[29418]: Failed password for invalid user admin from 188.190.221.7 port 7678 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=188.190.221.7
2020-01-31 23:27:09
196.64.229.38 attackspam
Jan 31 08:43:01 ns sshd[25229]: Connection from 196.64.229.38 port 57244 on 134.119.39.98 port 22
Jan 31 08:43:01 ns sshd[25229]: Invalid user admin1 from 196.64.229.38 port 57244
Jan 31 08:43:01 ns sshd[25229]: Failed password for invalid user admin1 from 196.64.229.38 port 57244 ssh2
Jan 31 08:43:02 ns sshd[25229]: Connection closed by 196.64.229.38 port 57244 [preauth]
Jan 31 08:43:05 ns sshd[25545]: Connection from 196.64.229.38 port 58009 on 134.119.39.98 port 22
Jan 31 08:43:05 ns sshd[25545]: Invalid user admin1 from 196.64.229.38 port 58009
Jan 31 08:43:06 ns sshd[25545]: Failed password for invalid user admin1 from 196.64.229.38 port 58009 ssh2
Jan 31 08:43:06 ns sshd[25545]: Connection closed by 196.64.229.38 port 58009 [preauth]
Jan 31 08:43:09 ns sshd[25722]: Connection from 196.64.229.38 port 58659 on 134.119.39.98 port 22
Jan 31 08:43:09 ns sshd[25722]: Invalid user admin1 from 196.64.229.38 port 58659
Jan 31 08:43:09 ns sshd[25722]: Failed password for in........
-------------------------------
2020-01-31 23:04:17
174.138.40.214 attackbots
xmlrpc attack
2020-01-31 23:04:29
1.53.207.12 attackbots
Jan 31 09:27:58 mxgate1 postfix/postscreen[11466]: CONNECT from [1.53.207.12]:38875 to [176.31.12.44]:25
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11471]: addr 1.53.207.12 listed by domain zen.spamhaus.org as 127.0.0.10
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11471]: addr 1.53.207.12 listed by domain zen.spamhaus.org as 127.0.0.3
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11471]: addr 1.53.207.12 listed by domain zen.spamhaus.org as 127.0.0.4
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11468]: addr 1.53.207.12 listed by domain cbl.abuseat.org as 127.0.0.2
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11467]: addr 1.53.207.12 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11469]: addr 1.53.207.12 listed by domain bl.spamcop.net as 127.0.0.2
Jan 31 09:27:58 mxgate1 postfix/dnsblog[11470]: addr 1.53.207.12 listed by domain b.barracudacentral.org as 127.0.0.2
Jan 31 09:28:04 mxgate1 postfix/postscreen[11466]: DNSBL rank 6 for [1.53.207.12]:38875
........
-------------------------------
2020-01-31 23:22:10
81.22.45.133 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 79 - port: 37165 proto: TCP cat: Misc Attack
2020-01-31 23:06:27
142.4.209.40 attack
Jan 31 15:56:18 wordpress wordpress(www.ruhnke.cloud)[15578]: Blocked authentication attempt for admin from ::ffff:142.4.209.40
2020-01-31 23:43:19
114.67.82.150 attackspambots
SSH bruteforce (Triggered fail2ban)
2020-01-31 23:38:18

Recently Reported IPs

75.253.137.56 74.224.191.70 79.205.136.102 73.175.86.231
12.113.119.203 208.105.40.226 53.131.32.55 168.21.207.9
217.190.11.219 78.141.223.161 137.123.9.53 234.136.83.4
66.31.12.179 228.211.158.196 85.86.152.90 213.233.191.232
246.87.29.124 253.205.91.251 226.91.12.238 234.75.78.160