DNS & HTTP Analysis for rt.com

Details
Category: Tool Processing Reports

Processing Domain rt.com on 05/08/2020 09:24:23


  • This tool is available free to use at GENSupport
  • Help and Support for your DNS or HTTP issues available on our Forum
  • Whenever you see a clicking on it will take you to more help
  • The version of the data model that was used in this report is 1.008
  • The version that produced this report is 1.023b

Processing DNS Records

Basic Checks

Here we check the basic functioning and security of your DNS

  • Zone Queries 6 Record Types and 40 Records Found
  • Zone Transfer Failed
  • Zone Dump
    • TXT
      • _dmarc.rt.com. TTL 300 "v=DMARC1;p=quarantine;sp=reject;adkim=s;aspf=s;pct=100;rua=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it.;ruf=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it."
      • rt.com. TTL 300 "v=spf1 include:_spf.google.com ~all"
    • A
      • ns0.rt.com. TTL 300 207.244.80.161
      • ns1.rt.com. TTL 300 82.202.190.84
      • ns2.rt.com. TTL 300 207.244.80.162
      • ns4.rt.com. TTL 300 185.79.236.249
      • ns5.rt.com. TTL 300 37.48.108.98
      • rt.com. TTL 300 207.244.80.166
      • rt.com. TTL 300 82.202.190.90
      • rt.com. TTL 300 82.202.190.91
    • AAAA
      • ns0.rt.com. TTL 300 2604:9a00:2100:a017:0:0:0:16a
      • ns2.rt.com. TTL 300 2604:9a00:2100:a017:0:0:0:16b
      • ns5.rt.com. TTL 300 2001:1af8:4700:b220:0:0:0:9b
      • rt.com. TTL 300 2001:1af8:4700:b220:0:0:0:112
      • rt.com. TTL 300 2604:9a00:2100:a017:0:0:0:166
    • MX
      • rt.com. TTL 300 10 aspmx.l.google.com.
      • rt.com. TTL 300 20 alt1.aspmx.l.google.com.
      • rt.com. TTL 300 20 alt2.aspmx.l.google.com.
      • rt.com. TTL 300 30 aspmx2.googlemail.com.
      • rt.com. TTL 300 30 aspmx3.googlemail.com.
      • rt.com. TTL 300 30 aspmx4.googlemail.com.
      • rt.com. TTL 300 30 aspmx5.googlemail.com.
    • NS
      • rt.com. TTL 300 ns1.rttv.ru.
      • rt.com. TTL 300 ns2.rttv.ru.
      • rt.com. TTL 300 ns3.rttv.ru.
      • rt.com. TTL 300 ns31.cloudns.net.
      • rt.com. TTL 300 ns32.cloudns.net.
      • rt.com. TTL 300 ns33.cloudns.net.
      • rt.com. TTL 300 ns34.cloudns.net.
      • rt.com. TTL 300 ns4.rttv.ru.
      • rt.com. TTL 300 pns31.cloudns.net.
      • rt.com. TTL 300 pns32.cloudns.net.
      • rt.com. TTL 300 pns33.cloudns.net.
      • rt.com. TTL 300 pns34.cloudns.net.
      • wpc.en.rt.com. TTL 300 ns0.rt.com.
      • wpc.en.rt.com. TTL 300 ns1.rt.com.
      • wpc.en.rt.com. TTL 300 ns2.rt.com.
      • wpc.en.rt.com. TTL 300 ns4.rt.com.
      • wpc.en.rt.com. TTL 300 ns5.rt.com.
    • CNAME
      • www.rt.com. TTL 300 wpc.en.rt.com.

Nameservers

Here we check the setup of your nameservers. All nameservers on your domain should be listed in the zone and returned in an ANY query along with corresponding A and/or AAAA records resolving their address.

  • ns32.cloudns.net 209.58.140.85 Found and Match. (Missing from Zone Address Records )
  • pns34.cloudns.net 185.136.99.66 Found and Match. (Missing from Zone Address Records )
  • pns33.cloudns.net 185.136.98.66 Found and Match. (Missing from Zone Address Records )
  • pns31.cloudns.net 185.136.96.66 Found and Match. (Missing from Zone Address Records )
  • ns33.cloudns.net 54.36.26.145 Found and Match. (Missing from Zone Address Records )
  • ns34.cloudns.net 185.206.180.104 Found and Match. (Missing from Zone Address Records )
  • ns1.rttv.ru 109.73.15.35 Found and Match. (Missing from Zone Address Records )
  • ns1.rttv.ru Found and Match. (Missing from Zone Address Records )
  • pns32.cloudns.net 185.136.97.66 Found and Match. (Missing from Zone Address Records )
  • ns31.cloudns.net 109.201.133.111 Found and Match. (Missing from Zone Address Records )
  • ns4.rttv.ru 91.217.20.1 Found and Match. (Missing from Zone Address Records )
  • ns4.rttv.ru Found and Match. (Missing from Zone Address Records )
  • ns2.rttv.ru 185.79.236.245 Found and Match. (Missing from Zone Address Records )
  • ns2.rttv.ru Found and Match. (Missing from Zone Address Records )
  • ns3.rttv.ru 91.217.21.1 Found and Match. (Missing from Zone Address Records )
  • ns3.rttv.ru Found and Match. (Missing from Zone Address Records )
  • All Name Servers SHOULD BE on Different Subnets

Processing 2 TXT Records

DMARC Record:

The DMARC Record defines how MTA's should response when parsing DKIM and SPF records

  • v=dmarc1 (The Version of this record)
  • p=quarantine (The Policy to implement on FAIL)
  • sp=reject (The Policy to implement for subdomains on FAIL)
  • adkim=s (Alignment mode for DKIM)
  • aspf=s (Alignment mode for SPF)
  • pct=100 (The Percentage of Messages subject to filtering)
  • rua=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it. (Reporting URI of aggregate reports)
  • ruf=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it. (Reporting URI for forensic reports)

SPF Record:

The SPF Record defines which IP addresses are permitted to send email on this domain's behalf

  • v=spf1 (The SPF Format Version Number)
  • include:_spf.google.com (An Include - Additional look-ups required, some server's won't bother.)
  • ~all (Permit other hosts but take note)

Processing 7 MX (Mail Exchanger) Records

These Records determine the servers (mail servers) responsible for handling your incomming email. Each service is given a priority and they will be used in that order. If all the priorities are the same then they will be used in a round-robin fashion

  • Priority 10 handled by host aspmx.l.google.com. [173.194.76.26] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 20 handled by host alt1.aspmx.l.google.com. [209.85.233.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 20 handled by host alt2.aspmx.l.google.com. [142.250.4.26] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 30 handled by host aspmx2.googlemail.com. [209.85.233.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 30 handled by host aspmx3.googlemail.com. [142.250.4.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 30 handled by host aspmx4.googlemail.com. [108.177.97.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 30 handled by host aspmx5.googlemail.com. [74.125.28.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open

Processing 1 CNAME (Alias) Records

These records are aliases making one hostname relate to another. These are often used to match hosts back to clusters or internal referencs that may change.

  • www.rt.com. wpc.en.rt.com.

Processing 8 A (IPv4 Address) Records

These records define the IP Addresse(s) of the servers responsible for hosting your webiste and other resouces on your domain. The www record is the most common one and will be used to identify your website address

  • Host: ns0.rt.com. = IP: [207.244.80.161] Valid Reachable (78.7ms)
  • Host: ns1.rt.com. = IP: [82.202.190.84] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: ns2.rt.com. = IP: [207.244.80.162] Valid Reachable (78.781ms)
  • Host: ns4.rt.com. = IP: [185.79.236.249] Valid Reachable (48.524ms)
  • Host: ns5.rt.com. = IP: [37.48.108.98] Valid Reachable (17.172ms)
  • Host: rt.com. = IP: [207.244.80.166] Valid Reachable (78.712ms)
  • Host: rt.com. = IP: [82.202.190.90] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: rt.com. = IP: [82.202.190.91] Valid Unreachable TX:1 RX:0 LOSS:100%

Processing AAAA (IPv6 Address) Records

These records define the IP Addresse(s) of the servers responsible for hosting your webiste and other resouces on your domain

  • Host: ns0.rt.com. = IP: [2604:9a00:2100:a017:0:0:0:16a] Valid
  • Host: ns2.rt.com. = IP: [2604:9a00:2100:a017:0:0:0:16b] Valid
  • Host: ns5.rt.com. = IP: [2001:1af8:4700:b220:0:0:0:9b] Valid
  • Host: rt.com. = IP: [2001:1af8:4700:b220:0:0:0:112] Valid
  • Host: rt.com. = IP: [2604:9a00:2100:a017:0:0:0:166] Valid

Processing Domain Public Records

    Domain Name WHOIS Information - rt.com

    • Domain Name RT.COM
    • Registry Domain ID 195281_DOMAIN_COM-VRSN
    • Registrar WHOIS Server whois.nic.ru
    • Registrar URL: http://nic.ru
    • Updated Date: 2019-08-20T07:48:14Z
    • Creation Date: 1991-09-23T04:00:00Z
    • Registry Expiry Date: 2025-09-22T04:00:00Z
    • Registrar Regional Network Information Center, JSC dba RU-CENTER
    • Registrar IANA ID 463
    • Registrar Abuse Contact Email This email address is being protected from spambots. You need JavaScript enabled to view it.
    • Registrar Abuse Contact Phone +7 (495) 994-46-01
    • Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
    • Name Server NS1.RTTV.RU
    • Name Server NS2.RTTV.RU
    • Name Server NS3.RTTV.RU
    • Name Server NS31.CLOUDNS.NET
    • Name Server NS32.CLOUDNS.NET
    • Name Server NS33.CLOUDNS.NET
    • Name Server NS34.CLOUDNS.NET
    • Name Server NS4.RTTV.RU
    • Name Server PNS31.CLOUDNS.NET
    • Name Server PNS32.CLOUDNS.NET
    • Name Server PNS33.CLOUDNS.NET
    • Name Server PNS34.CLOUDNS.NET
    • DNSSEC unsigned
    • URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

    Website Hosting WHOIS Information - 207.244.80.161

    • Tacticom, Inc. NET-109286 (NET-207-244-80-0-1) 207.244.80.0 - 207.244.80.255
    • Leaseweb USA, Inc. LEASEWEB-USA-WDC-01 (NET-207-244-64-0-1) 207.244.64.0 - 207.244.127.255

Processing Website

    Website Headers for www.rt.com

    We will obtain the headers from your website and parse them for validity

    • Web Server is nginx
    • Server header does not contain version information
    • Request Response HTTP/1.1 200 OK OK
    • SSL is available and enabled
        • /C=RU/L=Moscow/O=ANO TV-Novosti/OU=IT/CN=*.rt.comRU
      • Locality Moscow
      • Organisation ANO TV-Novosti
      • Certificate Scope *.rt.com
      Certificate Issuer
      • Country US
      • Organisation DigiCert Inc
      • Certificate Scope GeoTrust RSA CA 2018
      Certificate Validity
      • Valid From 200225000000Z
      • Valid To 210526120000Z
      Certificate Ciphers
      • SN RSA-SHA256
      • LN sha256WithRSAEncryption
      Certificate Extensions
      • Alternative Hostnames DNS:*.rt.com, DNS:rt.com
      • Key Usage TLS Web Server Authentication, TLS Web Client Authentication
  • There was a redirect to https://www.rt.com/

    • General

    • allow Valid methods for a specified resource after a 405 : Missing
    • location For Redirects specifies the target : Missing
    • connection Control options for the current connection [keep-alive]
    • x-powered-by Specifies Technology in use - Security Risk : Missing
    • x-aspnet-version Specifies the ASP.net version - Security Risk : Missing
    • accept-ranges To advertise its support of partial requests : Missing
    • link Used to express typed relationship with another resource : Missing
    • upgrade HTTP/2 (The latest and faster version of HTTP is available : Missing

    Security

    • referrer-policy Modifies the algorithm used to populate the Referer Header : Missing
    • x-xss-protection Prevents pages loading when XSS is detected : Missing
    • feature-policy Allow or Deny the use of browser features : Missing
    • p3p Platform for Privacy Preferences : Missing
    • content-security-policy CSP Content Security Policy : Missing
    • x-frame-options Can we open this response in an iframe : Missing

    Cross Origin

    • access-control-allow-origin Can we share the response with the given origin : Missing
    • access-control-allow-credentials Tells Browsers whether to expose the response to frontend JavaScript : Missing
    • access-control-expose-headers Indicates which headers can be exposed as part of the Response : Missing
    • access-control-max-age Indicates how long the results of a preflight request can be stored : Missing
    • access-control-allow-methods Methods allowed when accessing the resource in response to a preflight request : Missing
    • access-control-allow-headers Indicates which headers can be used during the actual request : Missing

    Content

    • content-language The natural language or languages of the intended audience : Missing
    • transfer-encoding The form of encoding used : Missing
    • content-length The length of the response body : Missing
    • content-type The Media type of the Response Body [text/html; charset=UTF-8]
    • date The date and time of generation [Wed, 05 Aug 2020 09:20:12 GMT]
    • content-disposition An opportunity to raise a File Download dialogue box : Missing
    • content-encoding The type of encoding/compression used on the Response : Missing
    • content-location An alternate location for the returned data : Missing
    • content-range Where in a full body message this partial message belongs : Missing
    • etag An identifier for a specific version of a resource : Missing
    • vary how to match future request headers : Missing
    • x-content-type-options Types in Content-Type should NOT be changed : Missing

    Cache

    • cache-control Tells caches whether they may cache this object [no-cache,no-store,max-age=0]
    • expires Gives the date/time after which the response is considered stale : Missing
    • last-modified The last modified date for the requested object : Missing
    • pragma Implementation-specific fields for caching : Missing
    • x-cache-action From an Intermediate cache : Missing
    • x-cache-hits Intermediate Cache Hits count : Missing
    • x-cache-age Intermediate Cache Content Age : Missing
    • via Informs the client of proxies through which the response was sent : Missing
    • age The Age this page has been cached in a proxy : Missing
    • x-served-by The Cache that served this response : Missing
    • x-cache Indicates if the cache served cached content : Missing
    • x-via-fastly Specific headers from Fastly : Missing

    Strict Transport Security (HSTS) Policy

    • strict-transport-security A HSTS Policy for the client with scope [max-age=31536000; includeSubDomains; preload]

    Cookies and Fragments

    • set-cookie Cookie Data to store locally : Missing

    Other

    • x-backend-server Identifies the backend server providing this response : Missing
    • x-robots-tag Search engine Robot Directive : Missing
    • gen Used by some of the GEN Tools to verify zone ownership : Missing
    • cf-cache-status Cloudflare Specific Header indicating cache status for this response : Missing
    • x-aspnetmvc-version ASP MVC Version Number - Security Risk : Missing

    Not Profiled

    • x-4vcta [H39247N]

Robots.txt

  • You have a robots.txt file and it appears to be valid
    • Allow Entries (9) - Specific Allow
      • Disallow Entries (45) - Specific Disallow
        • Sitemap Entries (2) - Sitemaps
          • https://www.rt.com/sitemap.xml
          • https://www.rt.com/newssitemap.xml
        • Other Entries (3)

      Processing Website Profile Data

        Website Render for www.rt.com

        Technology Profile rt.com

        We will check for fingerprints of common website technologies

          • Failed to succesfully profile the website, it is likely either custom or plain HTML.

        MOZ Rank Profile https://www.rt.com/

        We will retrieve your Ranking Profile from Moz.com

        • 3092746 The number of external, equity links
        • 4734854 The number of internal and external equity and non-equity links
        • 94 The Domain Authority (DA) ( 0->100 )
        • 71 The Page Authority (PA) ( 0->100 )
        • 7.099999905 The MozRank of the Domain ( 0->10 )

        Google Safe Browsing https://www.rt.com/

        We will retrieve Safe Browsing Status from Google

        • This site is NOT listed as being unsafe by Google

        PhishTank Lookup https://www.rt.com/

        We will check PhishTank to see if your site is listed

        • This site is NOT listed as being unsafe by PhishTank

        Alexa Rank Profile https://www.rt.com/

        We will retrieve your Ranking Profile from Alexa.com

        • The number of external in links
        • Un-Ranked Your Alexa Rank

        Meta Profile https://www.rt.com/

        We will check the entire body for metadata

        • yandex-verification : 02996a62e1a9c158
        • pocket-site-verification : 23a18549cf0481f5cbfd0579b6f2bb
        • msvalidate_01 : 36879475773792950F4872586A371571
        • google-site-verification : VQLbsaWKiXW2-Vt4lP7MevnhMES537NO4fQjfGgLcbI
        • apple-mobile-web-app-capable : no
        • format-detection : telephone=yes
        • viewport : width=device-width, initial-scale=1.0, user-scalable=yes
        • handheldfriendly : true
        • mobileoptimzied : width
        • navigation : tabbed
        • description : RT is the first Russian 24/7 English-language news channel which brings the Russian view on global news.
        • article:author : Russia Today
        • twitter:card : summary_large_image
        • twitter:site : @RT_com
        • twitter:creator : @RT_com
        • twitter:title : RT - Breaking news, shows, podcasts
        • twitter:description : RT is the first Russian 24/7 English-language news channel which brings the Russian view on global news.

      Processing Completed

      • Performance Profile
        • DNS Lookups : 5.46 seconds
        • DNS Folding/Unfolding : 0.00 seconds
        • DNS Nameserver Checks : 0.00 seconds
        • DNS TXT Records : 0.00 seconds
        • DNS MX Records : 1.16 seconds
        • DNS CNAME : 0.00 seconds
        • DNS Address : 30.37 seconds
        • WHOIS Lookups : 0.51 seconds
        • First CURL : 0.16 seconds
        • Second CURL : 0.08 seconds
        • SSL Lookup : 0.21 seconds
        • Header Parsing : 0.00 seconds
        • Robots.txt Parsing : 0.08 seconds
        • Website Profile : 6.23 seconds
        • Website MozData : 0.41 seconds
        • Safe Browsing : 0.08 seconds
        • PhishTank : 0.07 seconds
        • Website Alexa : 0.68 seconds
        • Website META : 0.11 seconds

      The process is now completed and the results are shown above. The raw processing data is available HERE. Please take a moment to consider each test and its response. DNS, SMTP and HTTP are not simple protocols and it is way beyond the scope of this tool to suggest improvements, but you are welcome to request assistance via our Forum.