<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic If you using the exchange in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096705#M1014992</link>
    <description>&lt;P&gt;If you using the exchange server 2010, follow the process as below:-&lt;/P&gt;
&lt;P&gt;The specific TLD's I am blocking at present are as follows:&lt;/P&gt;
&lt;P&gt;.bar, .bid, .br, .cf, .click, .club, .cn, .cr, .cricket, .date, .eu, .faith, .fr, .ga, .gdn, .gg, .in, .link, .lol, .ml, .ninja, .party, .pw, .racing, .rocks, .rs, .ru, .science, .space, .stream, .tk, .top, .tr, .trade, .us, .wang, .webcam, .website, .win, .work, .xxx, .xyz&lt;/P&gt;
&lt;P&gt;I have accomplished this through the use of Sender Filtering (Exchange Management Console -&amp;gt; &amp;lt;OU&amp;gt; -&amp;gt; Organization Configuration -&amp;gt; Anti-spam -&amp;gt; Sender Filtering) and adding each TLD to the Blocked Senders list as a "Domain (include all subdomains)", as opposed to as an "Individual e-mail address" (sic).&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; line-height: 107%; font-family: 'Calibri',sans-serif;"&gt;#Rate if it helps&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 07 Aug 2017 14:07:32 GMT</pubDate>
    <dc:creator>Farhan Mohamed</dc:creator>
    <dc:date>2017-08-07T14:07:32Z</dc:date>
    <item>
      <title>Blocking Spamhaus Top 10 most abused Top level domains</title>
      <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096704#M1014970</link>
      <description>&lt;P&gt;I've created a test rule to block .study, .accountant, .party, .click, .top, .life, .yokohama, .ml TLD's&lt;/P&gt;
&lt;P&gt;I first created a URL objects and then put them in the group TLD_Top10_abused&lt;/P&gt;
&lt;P&gt;Created a test policy under users with only me with block with reset.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For some reason it dosn't seem to work.&amp;nbsp; When I created the URL objects I named them "irl.study" then put ".study" as the url.&amp;nbsp; Is there a trick to blocking TLD's?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:28:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096704#M1014970</guid>
      <dc:creator>andrew.schiro</dc:creator>
      <dc:date>2019-03-12T13:28:21Z</dc:date>
    </item>
    <item>
      <title>If you using the exchange</title>
      <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096705#M1014992</link>
      <description>&lt;P&gt;If you using the exchange server 2010, follow the process as below:-&lt;/P&gt;
&lt;P&gt;The specific TLD's I am blocking at present are as follows:&lt;/P&gt;
&lt;P&gt;.bar, .bid, .br, .cf, .click, .club, .cn, .cr, .cricket, .date, .eu, .faith, .fr, .ga, .gdn, .gg, .in, .link, .lol, .ml, .ninja, .party, .pw, .racing, .rocks, .rs, .ru, .science, .space, .stream, .tk, .top, .tr, .trade, .us, .wang, .webcam, .website, .win, .work, .xxx, .xyz&lt;/P&gt;
&lt;P&gt;I have accomplished this through the use of Sender Filtering (Exchange Management Console -&amp;gt; &amp;lt;OU&amp;gt; -&amp;gt; Organization Configuration -&amp;gt; Anti-spam -&amp;gt; Sender Filtering) and adding each TLD to the Blocked Senders list as a "Domain (include all subdomains)", as opposed to as an "Individual e-mail address" (sic).&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-size: 11.0pt; line-height: 107%; font-family: 'Calibri',sans-serif;"&gt;#Rate if it helps&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 14:07:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096705#M1014992</guid>
      <dc:creator>Farhan Mohamed</dc:creator>
      <dc:date>2017-08-07T14:07:32Z</dc:date>
    </item>
    <item>
      <title>Farhan,</title>
      <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096706#M1014998</link>
      <description>&lt;P&gt;Farhan,&lt;/P&gt;
&lt;P&gt;While this will block spam from entering our accounts from these Top Level Domains, I want to block all traffic in firesite to and from these TLD's.&amp;nbsp; No legitimate traffic should be occurring from these domains.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For instance, If I try to block t.co (twitter links) it blocks anything ending with "t" in the domain name and part of the .com TLD&lt;/P&gt;
&lt;P&gt;There seems to be a bit of unintentional wildcarding going on in processing of URL's, which is why I want a method of blocking TLD's not just domains.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 14:22:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096706#M1014998</guid>
      <dc:creator>andrew.schiro</dc:creator>
      <dc:date>2017-08-07T14:22:49Z</dc:date>
    </item>
    <item>
      <title>Have you tried or heard about</title>
      <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096707#M1015008</link>
      <description>&lt;P&gt;Have you tried or heard about opendns, if not please check.&amp;nbsp; &lt;EM&gt;OpenDNS can block all Top-Level-Domains (TLDs) except .com. Entering a TLD such as net, cn, ru, and so on, will block all sub-domains that end with that TLD name.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;See&amp;nbsp;&lt;A href="https://support.opendns.com/entries/26514730-Web-Content-Filtering-and-Security" rel="nofollow noreferrer"&gt;https://support.opendns.com/entries/26514730-Web-Content-Filtering-and-Security&lt;/A&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;"&lt;EM&gt;there are limits on how many entries can be added to 'always block' list. In my case it is 25.&lt;/EM&gt;"&lt;/P&gt;
&lt;P&gt;With OpenDNS VIP it is 50.&lt;/P&gt;
&lt;P&gt;"&lt;EM&gt;you can not establish a whitelist of countries that you want to allow and blacklist all others&lt;/EM&gt;"&lt;/P&gt;
&lt;P&gt;You can - easily!&amp;nbsp; You go for OpenDNS VIP, enable the whitelist-only mode, and add the few TLDs you want to allow to the whitelist.&amp;nbsp; 50 should be sufficient, right?&lt;/P&gt;
&lt;P&gt;"&lt;EM&gt;If it is not possible to automatically detect language then don't.&lt;/EM&gt;"&lt;/P&gt;
&lt;P&gt;OpenDNS has nothing to do with websites and their languages.&amp;nbsp; A DNS service deals with domain names only.&lt;/P&gt;
&lt;P&gt;Also check Cisco Umbrella, which is new name for Opendns.&lt;/P&gt;
&lt;P&gt;I can arrange demo if you want to know more about Umbrella?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;#Please rate if it helps.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2017 14:39:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3096707#M1015008</guid>
      <dc:creator>Farhan Mohamed</dc:creator>
      <dc:date>2017-08-07T14:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: Have you tried or heard about</title>
      <link>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3694620#M1015018</link>
      <description>&lt;P&gt;Just to be clear Farhan, your saying FirePower doesnt have a way to block TLD's? we are trying the same thing here and i have not been able to get it working.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Aug 2018 14:38:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/blocking-spamhaus-top-10-most-abused-top-level-domains/m-p/3694620#M1015018</guid>
      <dc:creator>geoces85</dc:creator>
      <dc:date>2018-08-24T14:38:25Z</dc:date>
    </item>
  </channel>
</rss>

