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 Kingdom of Great Britain and Northern Ireland (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 <<>> 157.125.143.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22922
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;157.125.143.42.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 24 07:32:15 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 42.143.125.157.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 42.143.125.157.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.232.34.254 attackbotsspam
445/tcp 445/tcp 445/tcp...
[2019-05-19/07-19]21pkt,1pt.(tcp)
2019-07-20 02:20:26
38.83.102.90 attackspambots
445/tcp 445/tcp 445/tcp...
[2019-05-23/07-19]6pkt,1pt.(tcp)
2019-07-20 02:21:45
217.128.185.234 attack
Jul 15 19:16:46 sanyalnet-awsem3-1 sshd[17239]: Connection from 217.128.185.234 port 36340 on 172.30.0.184 port 22
Jul 15 19:17:26 sanyalnet-awsem3-1 sshd[17239]: Invalid user shashi from 217.128.185.234
Jul 15 19:17:28 sanyalnet-awsem3-1 sshd[17239]: Failed password for invalid user shashi from 217.128.185.234 port 36340 ssh2
Jul 15 19:17:28 sanyalnet-awsem3-1 sshd[17239]: Received disconnect from 217.128.185.234: 11: Bye Bye [preauth]
Jul 15 21:11:27 sanyalnet-awsem3-1 sshd[30088]: Connection from 217.128.185.234 port 46624 on 172.30.0.184 port 22
Jul 15 21:11:45 sanyalnet-awsem3-1 sshd[30088]: Invalid user muhammad from 217.128.185.234
Jul 15 21:11:48 sanyalnet-awsem3-1 sshd[30088]: Failed password for invalid user muhammad from 217.128.185.234 port 46624 ssh2
Jul 15 21:11:48 sanyalnet-awsem3-1 sshd[30088]: Received disconnect from 217.128.185.234: 11: Bye Bye [preauth]
Jul 15 21:12:15 sanyalnet-awsem3-1 sshd[30107]: Connection from 217.128.185.234 port 49814 on 172.........
-------------------------------
2019-07-20 01:39:45
84.58.20.33 attack
Brute-force attack to non-existent web resources
2019-07-20 01:40:04
46.229.168.149 attackbotsspam
Malicious Traffic/Form Submission
2019-07-20 01:35:09
94.191.48.165 attack
2019-07-19T17:17:51.934625abusebot.cloudsearch.cf sshd\[22640\]: Invalid user oracle from 94.191.48.165 port 35944
2019-07-20 01:32:09
183.146.209.68 attack
19.07.2019 16:48:02 SSH access blocked by firewall
2019-07-20 01:55:07
118.89.240.179 attackbots
22/tcp 22/tcp 22/tcp
[2019-07-17/19]3pkt
2019-07-20 01:53:04
86.3.164.248 attackspambots
2019-07-19T22:15:11.509181ns1.unifynetsol.net webmin\[3735\]: Invalid login as root from 86.3.164.248
2019-07-19T22:15:17.978485ns1.unifynetsol.net webmin\[3737\]: Invalid login as root from 86.3.164.248
2019-07-19T22:15:24.480189ns1.unifynetsol.net webmin\[3747\]: Invalid login as root from 86.3.164.248
2019-07-19T22:15:31.957792ns1.unifynetsol.net webmin\[3754\]: Invalid login as root from 86.3.164.248
2019-07-19T22:15:39.464105ns1.unifynetsol.net webmin\[3757\]: Invalid login as root from 86.3.164.248
2019-07-20 02:16:02
104.248.117.234 attackbots
Jul 19 18:48:41 microserver sshd[16254]: Invalid user test from 104.248.117.234 port 43486
Jul 19 18:48:41 microserver sshd[16254]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.117.234
Jul 19 18:48:43 microserver sshd[16254]: Failed password for invalid user test from 104.248.117.234 port 43486 ssh2
Jul 19 18:53:32 microserver sshd[16913]: Invalid user amal from 104.248.117.234 port 41890
Jul 19 18:53:32 microserver sshd[16913]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.117.234
Jul 19 19:07:36 microserver sshd[19038]: Invalid user 123456 from 104.248.117.234 port 37100
Jul 19 19:07:36 microserver sshd[19038]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.117.234
Jul 19 19:07:38 microserver sshd[19038]: Failed password for invalid user 123456 from 104.248.117.234 port 37100 ssh2
Jul 19 19:12:23 microserver sshd[19704]: Invalid user P@ssw0rd from 104.248.117.
2019-07-20 01:50:46
61.8.253.85 attackbots
Triggered by Fail2Ban at Vostok web server
2019-07-20 02:19:41
218.92.0.196 attackbotsspam
Jul 20 00:28:40 webhost01 sshd[27483]: Failed password for root from 218.92.0.196 port 30386 ssh2
...
2019-07-20 01:53:35
97.74.232.69 attackbotsspam
WordPress XMLRPC scan :: 97.74.232.69 0.320 BYPASS [20/Jul/2019:02:45:57  1000] [censored_1] "POST /xmlrpc.php HTTP/1.1" 503 19382 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-07-20 01:58:35
104.248.181.166 attackbots
Jul 19 19:50:34 v22019058497090703 sshd[29502]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.181.166
Jul 19 19:50:36 v22019058497090703 sshd[29502]: Failed password for invalid user info from 104.248.181.166 port 42656 ssh2
Jul 19 19:57:06 v22019058497090703 sshd[29872]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.181.166
...
2019-07-20 02:12:05
46.19.225.236 attackspambots
445/tcp 445/tcp 445/tcp...
[2019-05-24/07-19]11pkt,1pt.(tcp)
2019-07-20 02:14:40

Recently Reported IPs

96.185.86.175 55.212.29.158 167.127.155.56 179.176.212.75
87.38.166.35 62.25.85.219 139.81.84.155 171.242.28.153
216.209.94.162 214.142.246.67 35.1.220.212 198.68.27.111
208.217.113.73 245.24.118.115 41.220.159.100 232.200.135.101
26.168.12.190 49.248.65.104 33.242.118.229 103.21.182.175