Weekly Footprints of Threats
404 error
Oops...We are sorry! This page you're looking for is not available at this moment...
You may check out the below pages alternatively.



Top

Related Articles

6 Comments

  1. 1

    MalwareMustDie

    A very well written explanation why we must deal with .RU malware distrbuted domains. For Russia to fix their system properly before releasing .RU domains into beloved internet.

    Sadly, not even one single Russian I know would notice & try to fix this legendary procedural corrupted scheme, for the anti malware researchers to pay with sweat and tears.

    Good essay, dont let the echo stops!

    You know who we are,

    #MalwareMustDie

    1. 1.1

      R Sachin

      These are the flaws in a business process and takes a herculean effort to change them.
      Rgds
      R Sachin

  2. Pingback: The Professional Web | Welcome to the eScan Blog

  3. 2

    mindego

    Sorry for necroposting, but you are not quite right.
    Clause 9.6.2 IS NOT requires mandatory verification, it is just states the list of data, which is kept in registry. It is similar to 3.3 clause of ICANN’s RAA2013.
    Time-frame for clause 9.3.7 is NOT one year, it is 7 days (compare to 15 days of RAA2013) after registrar’s request to update/confirm data.
    And, of cause, domain is suspended immediately (well, sort of) after request of competent organization (http://cctld.ru/en/registrators/competent/ , but Russian variant http://www.cctld.ru/ru/registrators/competent/ is more populated). Please note, that such complaint should contain proofs (not just – “There are dragons!”-type complaints, which is loved to be used by Spamhaus-like organizations).

    Sorry, my English is little (or not litlle) rusty, so please bear with me.

    1. 2.1

      R Sachin

      Thanks for the comment. Replied via : http://blog.escanav.com/2014/03/18/ru-part-ii/

  4. Pingback: .RU – Part II | Welcome to the eScan Blog

Comments are closed.

Copyright © 2018 MicroWorld Technologies Inc. - Anti-Virus escanav.com