192.168.2.131 - IPInfo

Basic Info

City: unknown

Region: unknown

Country: IANA Special-Purpose Address

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
192.168.2.136	proxynormal	cdn-p1-lm.soilinktaobao.com	2026-01-12 02:42:16
192.168.2.136	proxynormal	cdn-p1-lm.soilinktaobao.com	2026-01-12 02:42:15
192.168.2.210	normal	k	2025-09-14 12:42:31
192.168.2.210	normal	k	2025-09-14 12:42:26
192.168.2.76	spambotsattackproxynormal	想打人	2025-07-12 13:30:47
192.168.2.216	spambotsattacknormal	15263298866	2024-11-06 20:28:21
192.168.2.216	spambotsattacknormal	15263298866	2024-11-06 20:28:14
192.168.2.176	normal	。	2023-04-22 20:49:44
192.168.2.176	normal	。	2023-04-22 20:49:44
192.168.2.176	normal	。	2023-04-22 20:49:44
192.168.200.16	spambotsattackproxynormal	韦海楼	2022-11-25 17:44:46
192.168.2.55	spambotsattackproxynormal	ho is this ip	2022-09-13 07:36:54
192.168.2.55	spambotsattackproxynormal	deteils	2022-09-13 07:36:31
192.168.2.55	spambotsattackproxynormal	deteils	2022-09-13 07:36:18
192.168.2.55	spambotsattackproxynormal	deteils	2022-09-13 07:36:14

Whois info:

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       192.168.0.0 - 192.168.255.255
CIDR:           192.168.0.0/16
NetName:        PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
NetHandle:      NET-192-168-0-0-1
Parent:         NET192 (NET-192-0-0-0-0)
NetType:        IANA Special Use
OriginAS:       
Organization:   Internet Assigned Numbers Authority (IANA)
RegDate:        1994-03-15
Updated:        2024-05-24
Comment:        These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices.  They are only intended for use within a private context  and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:        
Comment:        These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry.  The traffic from these addresses does not come from ICANN or IANA.  We are not the source of activity you may see on logs or in e-mail records.  Please refer to http://www.iana.org/abuse/answers
Comment:        
Comment:        These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment:        http://datatracker.ietf.org/doc/rfc1918
Ref:            https://rdap.arin.net/registry/ip/192.168.0.0



OrgName:        Internet Assigned Numbers Authority
OrgId:          IANA
Address:        12025 Waterfront Drive
Address:        Suite 300
City:           Los Angeles
StateProv:      CA
PostalCode:     90292
Country:        US
RegDate:        
Updated:        2024-05-24
Ref:            https://rdap.arin.net/registry/entity/IANA


OrgTechHandle: IANA-IP-ARIN
OrgTechName:   ICANN
OrgTechPhone:  +1-310-301-5820 
OrgTechEmail:  abuse@iana.org
OrgTechRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   ICANN
OrgAbusePhone:  +1-310-301-5820 
OrgAbuseEmail:  abuse@iana.org
OrgAbuseRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.168.2.131
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56890
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;192.168.2.131.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 18 10:35:51 CST 2026
;; MSG SIZE  rcvd: 106

Host info

Host 131.2.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 131.2.168.192.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
51.137.134.191	attack	Jul 6 06:55:52 onepixel sshd[2523572]: Invalid user flf from 51.137.134.191 port 57444 Jul 6 06:55:52 onepixel sshd[2523572]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.137.134.191 Jul 6 06:55:52 onepixel sshd[2523572]: Invalid user flf from 51.137.134.191 port 57444 Jul 6 06:55:54 onepixel sshd[2523572]: Failed password for invalid user flf from 51.137.134.191 port 57444 ssh2 Jul 6 06:59:16 onepixel sshd[2525327]: Invalid user crl from 51.137.134.191 port 55766	2020-07-06 15:08:17
222.186.42.136	attackbots	Unauthorized connection attempt detected from IP address 222.186.42.136 to port 22	2020-07-06 15:09:24
51.38.179.113	attack	Automatic Fail2ban report - Trying login SSH	2020-07-06 14:54:47
209.141.47.92	attackbotsspam	Jul 6 08:17:18 OPSO sshd\[8290\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.47.92 user=root Jul 6 08:17:20 OPSO sshd\[8290\]: Failed password for root from 209.141.47.92 port 45558 ssh2 Jul 6 08:20:14 OPSO sshd\[8945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.47.92 user=root Jul 6 08:20:16 OPSO sshd\[8945\]: Failed password for root from 209.141.47.92 port 32860 ssh2 Jul 6 08:22:58 OPSO sshd\[9259\]: Invalid user telnet from 209.141.47.92 port 48392 Jul 6 08:22:58 OPSO sshd\[9259\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.141.47.92	2020-07-06 14:32:12
80.82.77.33	attackspam	TCP (SYN) 80.82.77.33:20012 -> port 311, len 44	2020-07-06 14:53:52
101.51.208.55	attackspam	TCP (SYN) 101.51.208.55:26959 -> port 23, len 44	2020-07-06 14:30:19
218.78.105.98	attack	Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-07-06T03:41:19Z and 2020-07-06T03:52:27Z	2020-07-06 14:52:45
88.199.127.122	attackbots	(smtpauth) Failed SMTP AUTH login from 88.199.127.122 (PL/Poland/88-199-127-122.tktelekom.pl): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-07-06 08:22:21 plain authenticator failed for 88-199-127-122.tktelekom.pl [88.199.127.122]: 535 Incorrect authentication data (set_id=ar.davoudi@sunirco.ir)	2020-07-06 14:57:56
222.186.15.246	attackspam	Jul 6 10:04:01 www4 sshd\[16654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.246 user=root Jul 6 10:04:02 www4 sshd\[16654\]: Failed password for root from 222.186.15.246 port 49851 ssh2 Jul 6 10:06:05 www4 sshd\[17074\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.246 user=root ...	2020-07-06 15:06:51
192.241.248.102	attackbots	Long Request	2020-07-06 15:09:49
186.18.102.39	attackspambots	Attempts against non-existent wp-login	2020-07-06 15:07:24
203.195.152.113	attackspam	Unauthorized connection attempt detected from IP address 203.195.152.113 to port 443	2020-07-06 15:03:05
114.29.237.161	attackspam	Currently 7 failed/unauthorized logins attempts via SMTP/IMAP whostnameh 7 different usernames and wrong password: 2020-07-06T05:36:01+02:00 x@x 2020-07-03T05:56:00+02:00 x@x 2020-06-05T13:59:44+02:00 x@x 2020-06-05T06:51:29+02:00 x@x 2020-05-26T07:42:17+02:00 x@x 2020-05-21T10:18:58+02:00 x@x 2020-05-09T19:26:12+02:00 x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=114.29.237.161	2020-07-06 14:42:37
95.187.138.216	attackbots	Unauthorized connection attempt from IP address 95.187.138.216 on Port 445(SMB)	2020-07-06 14:39:26
61.43.242.88	attack	Jul 6 06:42:43 h2779839 sshd[25339]: Invalid user rabbitmq from 61.43.242.88 port 34142 Jul 6 06:42:43 h2779839 sshd[25339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.43.242.88 Jul 6 06:42:43 h2779839 sshd[25339]: Invalid user rabbitmq from 61.43.242.88 port 34142 Jul 6 06:42:46 h2779839 sshd[25339]: Failed password for invalid user rabbitmq from 61.43.242.88 port 34142 ssh2 Jul 6 06:44:42 h2779839 sshd[25345]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.43.242.88 user=root Jul 6 06:44:44 h2779839 sshd[25345]: Failed password for root from 61.43.242.88 port 56798 ssh2 Jul 6 06:48:21 h2779839 sshd[25414]: Invalid user oracle from 61.43.242.88 port 51598 Jul 6 06:48:21 h2779839 sshd[25414]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.43.242.88 Jul 6 06:48:21 h2779839 sshd[25414]: Invalid user oracle from 61.43.242.88 port 51598 Jul 6 06 ...	2020-07-06 14:59:55

Recently Reported IPs

2606:4700:10::6814:7534	62.210.142.213	66.132.195.95	20.64.106.19
74.7.241.34	112.201.160.207	91.196.152.108	2606:4700:10::6814:8129
123.139.168.232	165.140.238.74	10.6.3.222	44.223.12.109
143.198.69.160	136.116.188.252	112.40.146.203	110.78.158.71
103.129.196.3	66.132.186.170	172.237.126.190	2606:4700:10::6814:8517