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: None

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

;; QUESTION SECTION:
;106.124.138.65.			IN	A

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

;; Query time: 72 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 06:52:04 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 65.138.124.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 65.138.124.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.38.140.6 attack
Automatic report - Port Scan Attack
2020-04-29 02:29:52
81.183.155.83 attackspambots
Honeypot attack, port: 81, PTR: 51B79B53.dsl.pool.telekom.hu.
2020-04-29 02:00:37
42.91.149.44 attack
Honeypot attack, port: 445, PTR: PTR record not found
2020-04-29 02:31:24
182.75.216.190 attackbotsspam
Apr 28 17:46:24 ovpn sshd\[4336\]: Invalid user vince from 182.75.216.190
Apr 28 17:46:24 ovpn sshd\[4336\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.216.190
Apr 28 17:46:26 ovpn sshd\[4336\]: Failed password for invalid user vince from 182.75.216.190 port 51214 ssh2
Apr 28 18:01:00 ovpn sshd\[7910\]: Invalid user harry from 182.75.216.190
Apr 28 18:01:00 ovpn sshd\[7910\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.216.190
2020-04-29 02:14:44
51.158.115.56 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-04-29 02:08:03
170.106.33.94 attack
SSH Brute-Force Attack
2020-04-29 02:01:07
14.18.78.175 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2020-04-29 02:11:07
183.89.214.158 attack
IMAP/SMTP Authentication Failure
2020-04-29 02:05:00
14.241.234.55 attackspam
20/4/28@08:09:17: FAIL: Alarm-Network address from=14.241.234.55
...
2020-04-29 02:27:56
5.45.107.204 attackbots
Apr 28 15:27:45 ns381471 sshd[15971]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.45.107.204
Apr 28 15:27:47 ns381471 sshd[15971]: Failed password for invalid user sysgames from 5.45.107.204 port 51229 ssh2
2020-04-29 02:15:46
51.38.188.101 attackspam
Apr 28 18:43:20 vmd26974 sshd[24769]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.188.101
Apr 28 18:43:22 vmd26974 sshd[24769]: Failed password for invalid user jj from 51.38.188.101 port 41956 ssh2
...
2020-04-29 02:27:42
45.125.218.10 attack
Port probing on unauthorized port 1433
2020-04-29 02:18:29
1.170.88.21 attackbotsspam
Port probing on unauthorized port 23
2020-04-29 01:57:09
177.80.234.51 attack
$f2bV_matches
2020-04-29 02:24:03
180.109.241.216 attackspambots
Brute Force - Postfix
2020-04-29 02:03:38

Recently Reported IPs

106.124.138.3 106.125.246.204 106.14.119.84 106.14.12.32
106.14.145.68 106.14.149.40 135.69.66.94 106.14.152.185
106.14.159.56 106.14.177.72 106.14.182.205 106.14.205.108
106.14.209.64 106.14.21.35 106.14.244.27 106.14.249.159
106.14.5.116 106.14.5.249 106.14.6.60 106.14.6.98