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

No discussion about this subnet yet..

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:       100.64.0.0 - 100.127.255.255
CIDR:           100.64.0.0/10
NetName:        SHARED-ADDRESS-SPACE-RFC6598-IANA-RESERVED
NetHandle:      NET-100-64-0-0-1
Parent:         NET100 (NET-100-0-0-0-0)
NetType:        IANA Special Use
OriginAS:       
Organization:   Internet Assigned Numbers Authority (IANA)
RegDate:        2012-03-13
Updated:        2024-05-24
Comment:        This block is used as Shared Address Space. Traffic from these addresses does not come from IANA. IANA has simply reserved these numbers in its database and does not use or operate them. 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/ 
Comment:        
Comment:        Shared Address Space can only be used in Service Provider networks or on routing equipment that is able to do address translation across router interfaces when addresses are identical on two different interfaces. 
Comment:        
Comment:        This block was assigned by the IETF in the Best Current Practice document, 
Comment:        RFC 6598 which can be found at: 
Comment:        http://tools.ietf.org/html/rfc6598
Ref:            https://rdap.arin.net/registry/ip/100.64.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 <<>> 100.101.1.136
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51698
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;100.101.1.136.			IN	A

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

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

Host info

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

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

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

Related IP info:

Related comments:

IP	Type	Details	Datetime
84.228.157.213	attackspam	Feb 10 23:26:00 yesfletchmain sshd\[25720\]: Invalid user xtl from 84.228.157.213 port 59738 Feb 10 23:26:00 yesfletchmain sshd\[25720\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.228.157.213 Feb 10 23:26:02 yesfletchmain sshd\[25720\]: Failed password for invalid user xtl from 84.228.157.213 port 59738 ssh2 Feb 10 23:31:35 yesfletchmain sshd\[25873\]: Invalid user bgq from 84.228.157.213 port 44061 Feb 10 23:31:35 yesfletchmain sshd\[25873\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.228.157.213 ...	2020-02-11 08:27:39
176.215.252.1	attackbotsspam	Feb 10 23:10:51 debian-2gb-nbg1-2 kernel: \[3631885.652811\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=176.215.252.1 DST=195.201.40.59 LEN=40 TOS=0x10 PREC=0x60 TTL=246 ID=45673 PROTO=TCP SPT=58098 DPT=40079 WINDOW=1024 RES=0x00 SYN URGP=0	2020-02-11 08:47:17
116.111.82.142	attack	Feb 11 07:38:29 webhost01 sshd[13298]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.111.82.142 Feb 11 07:38:31 webhost01 sshd[13298]: Failed password for invalid user xiu from 116.111.82.142 port 43064 ssh2 ...	2020-02-11 09:06:52
87.246.7.9	attackbots	2020-02-10 17:55:35 dovecot_login authenticator failed for (1vkeh0Lxo) [87.246.7.9]:51385 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chrish@lerctr.org) 2020-02-10 17:55:52 dovecot_login authenticator failed for (kcsObS) [87.246.7.9]:53942 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chrish@lerctr.org) 2020-02-10 17:56:13 dovecot_login authenticator failed for (BWCzJk6t) [87.246.7.9]:57317 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=chrish@lerctr.org) ...	2020-02-11 08:31:21
185.143.223.161	attack	Feb 11 01:47:57 relay postfix/smtpd\[30886\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.161\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[185.143.223.97\]\> Feb 11 01:47:57 relay postfix/smtpd\[30886\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.161\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[185.143.223.97\]\> Feb 11 01:47:57 relay postfix/smtpd\[30886\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.161\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[185.143.223.97\]\> Feb 11 01:47:57 relay postfix/smtpd\[30886\]: NOQUEUE: reject: RCPT from unknown\[185.143.223.161\]: 554 5.7.1 \: Relay access denied\; from=\ to=\	2020-02-11 09:08:15
87.222.97.100	attack	$f2bV_matches	2020-02-11 08:33:09
77.222.40.21	attackspam	[munged]::443 77.222.40.21 - - [11/Feb/2020:00:08:46 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:01 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:01 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:17 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:17 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:33 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:33 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:49 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-" [munged]::443 77.222.40.21 - - [11/Feb/2020:00:09:49 +0100] "POST /[munged]: HTTP/1.1" 200 5655 "-" "-"	2020-02-11 08:36:43
106.13.32.199	attack	Feb 11 01:04:16 serwer sshd\[3329\]: Invalid user ixm from 106.13.32.199 port 37948 Feb 11 01:04:16 serwer sshd\[3329\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.32.199 Feb 11 01:04:18 serwer sshd\[3329\]: Failed password for invalid user ixm from 106.13.32.199 port 37948 ssh2 ...	2020-02-11 08:45:48
112.85.42.182	attack	Feb 11 01:33:53 minden010 sshd[12105]: Failed password for root from 112.85.42.182 port 14533 ssh2 Feb 11 01:33:56 minden010 sshd[12105]: Failed password for root from 112.85.42.182 port 14533 ssh2 Feb 11 01:34:00 minden010 sshd[12105]: Failed password for root from 112.85.42.182 port 14533 ssh2 Feb 11 01:34:03 minden010 sshd[12105]: Failed password for root from 112.85.42.182 port 14533 ssh2 ...	2020-02-11 08:40:37
180.183.249.157	attack	IDS	2020-02-11 08:45:17
179.52.137.86	attack	Feb 10 12:11:13 php1 sshd\[17545\]: Invalid user pi from 179.52.137.86 Feb 10 12:11:13 php1 sshd\[17543\]: Invalid user pi from 179.52.137.86 Feb 10 12:11:13 php1 sshd\[17545\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.52.137.86 Feb 10 12:11:13 php1 sshd\[17543\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.52.137.86 Feb 10 12:11:15 php1 sshd\[17545\]: Failed password for invalid user pi from 179.52.137.86 port 45470 ssh2	2020-02-11 08:33:52
189.78.152.192	attack	Honeypot attack, port: 445, PTR: 189-78-152-192.dsl.telesp.net.br.	2020-02-11 08:27:58
190.39.36.68	attackspam	Honeypot attack, port: 445, PTR: 190-39-36-68.dyn.dsl.cantv.net.	2020-02-11 08:35:45
201.192.179.24	attack	Honeypot attack, port: 81, PTR: PTR record not found	2020-02-11 08:29:47
66.70.142.220	attackbots	Scanned 3 times in the last 24 hours on port 22	2020-02-11 08:27:03

Recently Reported IPs

39.100.82.83	176.65.148.71	45.205.1.65	14.128.130.5
194.187.178.57	194.187.178.3	183.208.3.154	2606:4700:10::6814:8441
206.119.168.94	199.45.154.152	2606:4700:10::6814:8272	59.218.53.82
20.12.173.235	2606:4700:10::6816:405	206.168.239.169	168.126.63.2
192.168.111.185	121.14.126.80	1.162.184.196	198.18.1.30