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: United States of America (the)

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

;; QUESTION SECTION:
;138.126.56.1.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 11:29:13 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 1.56.126.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 1.56.126.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
170.239.228.62 attackbotsspam
Port scan and direct access per IP instead of hostname
2019-07-28 15:56:41
177.44.26.40 attack
Jul 27 21:07:52 web1 postfix/smtpd[27874]: warning: unknown[177.44.26.40]: SASL PLAIN authentication failed: authentication failure
...
2019-07-28 15:43:41
41.162.90.68 attack
Automatic report
2019-07-28 16:07:35
157.230.140.180 attackbots
Jul 28 08:54:34 server sshd\[14616\]: Invalid user roger1 from 157.230.140.180 port 59336
Jul 28 08:54:34 server sshd\[14616\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.140.180
Jul 28 08:54:36 server sshd\[14616\]: Failed password for invalid user roger1 from 157.230.140.180 port 59336 ssh2
Jul 28 08:59:59 server sshd\[10057\]: Invalid user huangniu from 157.230.140.180 port 54450
Jul 28 08:59:59 server sshd\[10057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.140.180
2019-07-28 15:38:05
187.131.129.217 attackspambots
19/7/27@21:07:47: FAIL: Alarm-Intrusion address from=187.131.129.217
19/7/27@21:07:47: FAIL: Alarm-Intrusion address from=187.131.129.217
...
2019-07-28 15:48:47
164.52.24.163 attackbotsspam
Port scan and direct access per IP instead of hostname
2019-07-28 16:01:58
141.105.102.155 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 16:12:49
165.22.141.139 attackspam
Jul 28 09:46:11 eventyay sshd[18758]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.141.139
Jul 28 09:46:14 eventyay sshd[18758]: Failed password for invalid user Admin1234 from 165.22.141.139 port 58616 ssh2
Jul 28 09:52:29 eventyay sshd[20213]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.141.139
...
2019-07-28 15:57:43
5.196.131.168 attackbots
Non-stop spam.
2019-07-28 16:10:56
185.104.71.78 attackspambots
Port scan and direct access per IP instead of hostname
2019-07-28 15:19:44
162.243.141.204 attackspam
21482/tcp 119/tcp 5900/tcp...
[2019-05-27/07-27]50pkt,45pt.(tcp),3pt.(udp)
2019-07-28 16:03:57
178.176.13.69 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 15:34:53
178.19.109.66 attackspambots
Automatic report - Banned IP Access
2019-07-28 15:42:27
185.233.245.175 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 15:09:06
103.115.227.2 attack
Jul 28 01:08:01 *** sshd[17893]: User root from 103.115.227.2 not allowed because not listed in AllowUsers
2019-07-28 15:32:52

Recently Reported IPs

94.114.2.207 240.86.232.104 156.120.96.107 104.126.135.42
145.203.115.123 172.5.123.88 242.145.27.252 231.220.185.123
185.142.172.144 159.74.43.151 149.229.2.240 54.57.221.25
175.117.45.86 16.99.131.235 31.60.114.55 139.213.73.171
239.144.221.16 203.121.164.148 144.224.147.144 107.53.203.140