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

Region: Ontario

Country: Canada

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:
#
# 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:       20.150.0.0 - 20.153.255.255
CIDR:           20.150.0.0/15, 20.152.0.0/15
NetName:        MSFT
NetHandle:      NET-20-150-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-10-18
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/20.150.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-ARIN

OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-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 <<>> 20.151.200.100
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30560
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.151.200.100.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jul 14 20:00:04 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 100.200.151.20.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 100.200.151.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.42.136 attack
02.01.2020 08:16:53 SSH access blocked by firewall
2020-01-02 16:24:32
80.255.130.197 attackspam
Jan  2 07:26:17 markkoudstaal sshd[30183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.255.130.197
Jan  2 07:26:19 markkoudstaal sshd[30183]: Failed password for invalid user admin from 80.255.130.197 port 54211 ssh2
Jan  2 07:28:05 markkoudstaal sshd[30347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.255.130.197
2020-01-02 16:49:00
139.59.62.42 attack
Jan  2 00:08:00 mockhub sshd[31604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.62.42
Jan  2 00:08:02 mockhub sshd[31604]: Failed password for invalid user apache from 139.59.62.42 port 43916 ssh2
...
2020-01-02 16:48:18
119.90.61.10 attackspam
Jan  2 08:07:04 silence02 sshd[19990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.90.61.10
Jan  2 08:07:06 silence02 sshd[19990]: Failed password for invalid user http from 119.90.61.10 port 36806 ssh2
Jan  2 08:09:26 silence02 sshd[20081]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.90.61.10
2020-01-02 16:46:41
1.20.207.105 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-02 16:16:49
218.156.28.72 attackbots
Honeypot attack, port: 5555, PTR: PTR record not found
2020-01-02 16:25:34
59.144.137.134 attackspam
<6 unauthorized SSH connections
2020-01-02 16:15:01
115.98.172.19 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-02 16:40:53
167.114.98.229 attack
Jan  2 02:57:32 plusreed sshd[8586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.98.229  user=root
Jan  2 02:57:33 plusreed sshd[8586]: Failed password for root from 167.114.98.229 port 54208 ssh2
...
2020-01-02 16:11:14
218.92.0.164 attackbots
Jan  2 09:32:30 srv01 sshd[628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164  user=root
Jan  2 09:32:32 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:36 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:30 srv01 sshd[628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164  user=root
Jan  2 09:32:32 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:36 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:30 srv01 sshd[628]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.164  user=root
Jan  2 09:32:32 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:36 srv01 sshd[628]: Failed password for root from 218.92.0.164 port 19430 ssh2
Jan  2 09:32:
...
2020-01-02 16:36:33
83.198.121.77 attack
Honeypot attack, port: 23, PTR: lfbn-reu-1-27-77.w83-198.abo.wanadoo.fr.
2020-01-02 16:14:44
36.65.100.18 attack
Host Scan
2020-01-02 16:35:14
103.48.83.128 attack
01/02/2020-01:28:18.784544 103.48.83.128 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2020-01-02 16:39:34
183.97.104.15 attack
Jan  2 09:38:34 site2 sshd\[33823\]: Invalid user diodoro from 183.97.104.15Jan  2 09:38:36 site2 sshd\[33823\]: Failed password for invalid user diodoro from 183.97.104.15 port 52702 ssh2Jan  2 09:42:16 site2 sshd\[34327\]: Invalid user server from 183.97.104.15Jan  2 09:42:18 site2 sshd\[34327\]: Failed password for invalid user server from 183.97.104.15 port 55776 ssh2Jan  2 09:45:59 site2 sshd\[34410\]: Invalid user sianna from 183.97.104.15
...
2020-01-02 16:11:59
31.208.74.177 attack
Jan  1 14:56:55 server sshd\[25091\]: Failed password for invalid user pi from 31.208.74.177 port 35034 ssh2
Jan  1 14:56:55 server sshd\[25092\]: Failed password for invalid user pi from 31.208.74.177 port 35036 ssh2
Jan  2 11:13:53 server sshd\[24557\]: Invalid user pi from 31.208.74.177
Jan  2 11:13:53 server sshd\[24559\]: Invalid user pi from 31.208.74.177
Jan  2 11:13:54 server sshd\[24557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31-208-74-177.cust.bredband2.com 
Jan  2 11:13:54 server sshd\[24559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31-208-74-177.cust.bredband2.com 
...
2020-01-02 16:41:12

Recently Reported IPs

2606:4700:10::6816:4569 2606:4700:10::6816:2632 101.255.70.186 178.62.249.191
174.138.6.242 62.210.142.171 2606:4700:10::6814:9250 2606:4700:10::6816:1007
139.135.9.173 47.237.131.50 47.84.121.143 47.84.108.134
47.84.110.194 91.231.89.223 2606:4700:10::6816:3812 2606:4700:10::6814:6631
199.237.71.60 45.117.11.89 162.144.121.110 111.181.63.174