From c18f5cf4561192d2a33c43cd7d80b777fb05ed64 Mon Sep 17 00:00:00 2001
From: MaratMussabekov <48041687+MaratMussabekov@users.noreply.github.com>
Date: Wed, 30 Dec 2020 21:19:53 +0500
Subject: [PATCH] Update indicator-ip-domain.md

---
 .../microsoft-defender-atp/indicator-ip-domain.md             | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md b/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md
index 800f2e0f16..8578ea6865 100644
--- a/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md
+++ b/windows/security/threat-protection/microsoft-defender-atp/indicator-ip-domain.md
@@ -53,8 +53,8 @@ It's important to understand the following prerequisites prior to creating indic
 > NOTE:
 >- IP is supported for all three protocols
 >- Only single IP addresses are supported (no CIDR blocks or IP ranges)
->- Encrypted URLs (full path) can only be blocked on first party browsers
->- Encrypted URLS (FQDN only) can be blocked outside of first party browsers
+>- Encrypted URLs (full path) can only be blocked on first party browsers (Internet Explorer, Edge)
+>- Encrypted URLS (FQDN only) can be blocked outside of first party browsers (Internet Explorer, Edge)
 >- Full URL path blocks can be applied on the domain level and all unencrypted URLs
  
 >[!NOTE]