
Microsoft Notification Protocol is a push notification system developed by Microsoft, designed to allow applications to send notifications to users. It's a way for apps to communicate with users outside of the app itself.
The protocol is based on the WNS (Windows Notification Service), which is a cloud-based service that handles the sending and receiving of notifications. WNS provides a scalable and reliable way for apps to send notifications to users.
Microsoft Notification Protocol supports multiple notification types, including toast notifications, tile updates, and badge updates. These notifications can be used to draw the user's attention to new content or events in the app.
Additional reading: What Is G E O S M I N
What Is Msnp
MSNP, or Microsoft Notification Protocol, is a protocol developed by Microsoft to support real-time communication and notifications. It's most famously associated with MSN Messenger, a popular instant messaging service.
The protocol operates over port 1863, which is designated for this specific purpose. This is a unique identifier that helps ensure messages are delivered to the right place.
MSN Messenger, later rebranded as Windows Live Messenger, was a cornerstone of online communication in the early 2000s. It utilized MSNP to manage the exchange of messages, presence information, and other notifications between users.
MSNP runs on both TCP and UDP, which are common internet protocols used for data transfer. This allows for efficient and reliable communication.
The protocol's design emphasizes low latency and efficient message delivery, which are critical for any real-time communication service. This means messages are delivered quickly and users are notified promptly.
Related reading: Microsoft Messenger Service
Technical Details
Microsoft started blocking access to the Messenger service using versions below MSNP8 in October 2003.
This change was made to force users to upgrade to more secure versions of the protocol. Microsoft forces most current users of MSN Messenger to upgrade to Windows Live Messenger 8.1 due to security considerations, starting on September 11, 2007.
The version number of the protocol is incremented by one in the format of MSNP# whenever a major change is made, such as a new command or syntax changes.
Open source implementations of the protocol now have to consider changing to MSNP13-15, which will require lots of work but will also bring many new features of Windows Live Messenger to the open source clients.
Consider reading: Live Search Books
Security Concerns

The Microsoft Notification Protocol has a history of security concerns. A 2007 analysis concluded that its design didn't follow basic principles of secure systems.
Spoofing a user's identity is a real possibility with this protocol. Successfully spoofing a user's identity was demonstrated in a 2007 analysis.
If you're not careful, port 1863 can be exploited by attackers. This could lead to unauthorized access to sensitive information, such as personal messages or contact details.
Ensuring that port 1863 is secured and monitored is crucial. Closing this port using UFW, as explained in our UFW tutorial, is a good first step.
StackChanges can help you monitor if the MSNP port is closed and stays closed. It will send an alert if port 1863 is open again.
You might like: Dns Protocol Port
Msnp Versions
MSNP versions have a rich history, with the first version, MSNP1, being used in the early stages of MSN Messenger 1's development. It was later replaced by MSNP3, which was supported by MSN Messenger 2.0 and introduced a new command for WebTV (MSN TV) Messenger clients.
For another approach, see: Video Call Facebook Messenger Meta Glasses
MSNP3 was also used by MSN Messenger 6.1, which integrated with Hotmail address books. This version was notable for being the first to block earlier versions of the protocol in October 2003.
Here's a brief overview of some notable MSNP versions:
MSNP versions continued to evolve, with later versions introducing new features and improvements.
Msnp1
MSNP1 was a proprietary protocol used in the early stages of MSN Messenger's design and development.
It's believed that MSNP1 was used during the early stages of MSN Messenger 1.
A pre-release version of MSNP1 was made available to developers in 1999 in an Internet Draft.
The production version of MSNP1 differed from the published version in a few subtle ways.
Take a look at this: Fb Messenger Notification
Msnp3
MSNP3 was supported by MSN Messenger 2.0, along with MSNP2.
The first version of the WebTV (MSN TV) Messenger client, released in its Summer 2000 upgrade, also supported MSNP3.
This version introduced a new command, IMS, which allowed clients to block or allow new switchboard sessions with other users while signed in.
Worth a look: Ms Outlook Latest Version

MSNP3 was employed in MSN Messenger 6.1, after Microsoft started blocking earlier versions in October 2003.
The integration with Hotmail address books was the only obvious change in MSNP3 in MSN Messenger 6.1.
MSNP3 was also used by Windows Live Messenger 2011 (Wave 4) and Windows Live Messenger 2012.
By July 2000, MSNP3, 4, and 5 were supported by the Messenger servers, and were used by MSN Messenger 3.0 and 4.0.
A fresh viewpoint: Afghansat 1
Msnp6 and Msnp7
MSNP6 and MSNP7 were used by later versions of MSN Messenger 4.x. MSNP6 was used by these versions.
In 2002, MSN Messenger 5.0 started using MSNP7. This was a significant upgrade at the time.
Here's a brief overview of the versions:
These upgrades improved the overall performance and functionality of the MSN Messenger platform.
Msnp8
MSNP8 was introduced with a different authentication method, sending authorization to Microsoft Passport's secure servers and returning a challenge string. This change made it possible for users to connect to the MSN network with any registered email address.
Version 5.0 of MSN Messenger is the only one that uses MSNP8. Windows Messenger uses MSNP8 as its standard version, including 4.7 up to the latest 5.1.
MSNP8 is the minimum version of the protocol accepted by .NET Messenger Service after Microsoft blocked earlier versions for security reasons. As a result, old and obsolete clients are unable to sign in, forcing users to upgrade clients.
This version of the protocol supports Windows Messenger-to-Windows Messenger webcam and voice capabilities.
For another approach, see: Ioniq 5 Android Auto
Msnp9
MSNP9 was introduced with MSN Messenger 6, adding support for "D type" (data) messages, which are used for transferring display pictures and custom emoticons between clients.
This feature allowed for more personalization and customization of user profiles. MSNP9 also improved NAT traversal for file transfers, making it easier to share files with others.
The improved voice system in MSNP9 enabled better voice quality and more reliable voice calls. MSNP9 was employed in MSN Messenger 6.1, which was released after Microsoft started blocking earlier versions in October 2003.
The update was not a major overhaul, but it did integrate with Hotmail address books, making it easier to manage contacts.
Broaden your view: 6 Ghz Wifi
Msnp13

MSNP13 was employed by Windows Live Messenger 8.0.
This version of MSNP features a lot of changes.
Contact list synchronization has been removed, and clients must instead send a SOAP request to a contacts server.
The client must then send the contacts data to the server for it to send presence information.
This change is also known as "Client goes to ABCH", where ABCH stands for Address Book Clearing House, the address book service behind all MSN and Windows Live services.
The use of SOAP for contact list management and user presence information is a significant change in MSNP13.
MSNP13 was implemented in the public betas of Windows Live Messenger.
Recommended read: OMA Instant Messaging and Presence Service
Msnp15
MSNP15 is a significant update to the Microsoft Notification Protocol, introduced with Windows Live Messenger 8.1 in 2006. It's based on MSNP14 but uses a different authentication mechanism called RPS (Relying Party Suite).
This new authentication mechanism, called SSO (Single Sign-On; RPS), replaces the TWN "Tweener" authentication used in protocol versions 14 and below. MSNP15 also introduces support for user locations in the Personal Status Message, although this feature was later removed from the Windows Live Messenger 8.1 client.
Intriguing read: Windows Live Photos

Here are some key features of MSNP15:
- New authentication mechanism: RPS (Relying Party Suite)
- SSO (Single Sign-On) authentication used instead of TWN "Tweener" authentication
- Support for user locations in Personal Status Message
The introduction of MSNP15 marked a significant shift in the way Microsoft handled user authentication and personalization in Windows Live Messenger. With this new protocol, Microsoft aimed to provide a more seamless and consistent experience for users across different devices and platforms.
Msnp16
MSNP16 was introduced in a pre-release version of Windows Live Messenger 9.0, leaked in December 2007. It featured "Multiple Points of Presence" (MPOP), allowing users to sign in at two places at the same time with chats replicated across all locations.
This protocol version also extended the UUX data to contain Endpoint Data, as well as Signature Sound MSN Object Data. The ability to sign in at multiple locations was a significant improvement, but it was eventually removed from the Windows Live Messenger 9.0 client.
MSNP16 was also compatible with aMSN, a third-party instant messaging client. This compatibility allowed users to access MSNP16 features even if they weren't using the official Windows Live Messenger client.
Here's a quick rundown of the key features and facts about MSNP16:
- Introduced in a pre-release version of Windows Live Messenger 9.0
- Featured "Multiple Points of Presence" (MPOP)
- Extended UUX data to contain Endpoint Data and Signature Sound MSN Object Data
- Compatible with aMSN
- Leaked in December 2007
Msnp17

MSNP17 is identified by Windows Live Messenger servers on messenger.hotmail.com, but unused by any official client released by Microsoft.
It's worth noting that MSNP17 has been detected by servers but not utilized by any official Microsoft clients.
MSNP17 se identifica mediante servidores de Windows Live Messenger en messenger.hotmail.com, pero no utilizado por cualquier cliente oficial publicada por Microsoft.
This suggests that MSNP17 may have been considered for use but ultimately not implemented in any official Microsoft client releases.
Intriguing read: Windows Live Spaces
Msnp18
MSNP18 is used in Windows Live Messenger 2009 (14.0). Its main new addition is the Groups feature, much like persistent grouped conversations.
UUX Data have been extended to include Scene image MSN Object data. This allows for more detailed and engaging conversations.
MSNP18 is supported by MSNP-Sharp, making it a reliable choice for users.
Msnp2
MSNP2 was made available to developers in 1999 as a pre-release version in an Internet Draft.
This was the first and only version of MSNP to have its specifications published by Microsoft's developers in the form of an Internet Draft.
The production version of MSNP2 differed from the published version in a few subtle ways.
MSNP2 is now considered an outdated document, reflecting the evolving nature of the Microsoft Notification Protocol.
Intriguing read: 802.11 Draft N Speed
Frequently Asked Questions
What is Microsoft WNS?
Microsoft WNS (Windows Notification Service) is a service that helps send rich notifications to Windows apps. It's powered by Azure App Registration identities, enabling seamless communication between apps and users.
Featured Images: pexels.com


