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

;; QUESTION SECTION:
;42.124.158.44.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 04:56:15 CST 2025
;; MSG SIZE  rcvd: 106
Host info
44.158.124.42.in-addr.arpa domain name pointer ftth-158.44.dws.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.158.124.42.in-addr.arpa	name = ftth-158.44.dws.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
51.255.35.41 attackspam
SSH Brute Force
2020-05-03 05:39:06
103.242.56.174 attack
May  2 21:42:09 scw-6657dc sshd[9313]: Failed password for root from 103.242.56.174 port 57535 ssh2
May  2 21:42:09 scw-6657dc sshd[9313]: Failed password for root from 103.242.56.174 port 57535 ssh2
May  2 21:46:55 scw-6657dc sshd[9482]: Invalid user wol from 103.242.56.174 port 34463
...
2020-05-03 05:51:05
201.48.4.86 attack
SSH Brute Force
2020-05-03 05:41:16
104.194.11.42 attackbots
[MK-VM3] Blocked by UFW
2020-05-03 06:06:24
183.61.109.230 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:00:12
118.70.216.153 attack
May  2 22:58:31 tor-proxy-02 sshd\[1196\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
May  2 22:58:32 tor-proxy-02 sshd\[1198\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
May  2 22:58:33 tor-proxy-02 sshd\[1200\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
...
2020-05-03 05:34:18
162.243.138.34 attackspambots
ET SCAN Suspicious inbound to Oracle SQL port 1521 - port: 1521 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:02:19
146.185.130.101 attackspam
SSH Brute Force
2020-05-03 05:32:53
27.78.14.83 attack
May  2 23:55:41 home sshd[2612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.78.14.83
May  2 23:55:43 home sshd[2612]: Failed password for invalid user support from 27.78.14.83 port 57570 ssh2
May  2 23:55:51 home sshd[2636]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.78.14.83
...
2020-05-03 05:56:36
85.172.98.94 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 73 - port: 8089 proto: TCP cat: Misc Attack
2020-05-03 06:12:17
186.225.11.163 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 05:58:05
103.145.12.88 attackbotsspam
ET SCAN Sipvicious User-Agent Detected (friendly-scanner) - port: 5060 proto: UDP cat: Attempted Information Leak
2020-05-03 06:07:20
95.217.121.67 attackbotsspam
SSH Brute Force
2020-05-03 05:36:23
128.199.107.111 attack
SSH Brute Force
2020-05-03 05:33:51
162.125.35.135 attackspambots
ET POLICY Dropbox.com Offsite File Backup in Use - port: 16618 proto: TCP cat: Potential Corporate Privacy Violation
2020-05-03 06:03:09

Recently Reported IPs

56.42.105.1 143.91.158.31 74.80.23.53 91.86.213.34
247.118.109.168 162.126.154.243 16.229.132.233 155.181.200.100
118.241.237.160 218.219.201.172 147.237.18.64 211.212.7.95
152.220.34.166 96.82.183.49 3.63.254.219 217.87.135.39
169.119.57.187 246.0.83.99 63.51.186.222 233.92.100.185