DNS & HTTP Analysis for slack.com

Processing Domain slack.com on 12/08/2020 09:59:56


  • 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 5 Record Types and 19 Records Found
  • Zone Transfer Failed
  • Zone Dump
    • TXT
      • _dmarc.slack.com. TTL 300 "v=DMARC1; p=reject; pct=100; rua=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it.;"
      • slack.com. TTL 3600 "OSSRH-54733"
      • slack.com. TTL 3600 "google-site-verification=2PK67oVPNyEtS1avSlr3PhH5nSiFuticbQv_bT4pM2k"
      • slack.com. TTL 3600 "google-site-verification=KqX3Ngw0XEjz_0GVx_xwFFlCoO-bskhqU_lxv0Q77mk"
      • slack.com. TTL 3600 "google-site-verification=efuXt5-oMr2CdNmVi6A9IO29KMKifpseD1qokxjWwcE"
      • slack.com. TTL 3600 "google-site-verification=kB1KvgpSk9YkHsFmsj1VPI5YmDvfKctPxnplhGjyqtE"
      • slack.com. TTL 3600 "google-site-verification=v-LLB__IhraaI7ZzuE3jvRFIm2vERPLzWoepAEZJtKQ"
      • slack.com. TTL 3600 "v=spf1 ip4:54.240.37.228/31 ip4:54.240.35.24/29 ip4:54.240.35.20/30 ip4:69.169.237.194 ip4:69.169.237.192/31 ip4:69.169.237.184/29 ip4:69.169.237.180/30 ip4:69.169.237.179 include:_spf.qualtrics.com -all"
    • NS
      • slack.com. TTL 172800 ns-1493.awsdns-58.org.
      • slack.com. TTL 172800 ns-166.awsdns-20.com.
      • slack.com. TTL 172800 ns-1901.awsdns-45.co.uk.
      • slack.com. TTL 172800 ns-606.awsdns-11.net.
    • A
      • slack.com. TTL 60 3.10.95.11
    • MX
      • slack.com. TTL 60 1 aspmx.l.google.com.
      • slack.com. TTL 60 10 aspmx2.googlemail.com.
      • slack.com. TTL 60 10 aspmx3.googlemail.com.
      • slack.com. TTL 60 5 alt1.aspmx.l.google.com.
      • slack.com. TTL 60 5 alt2.aspmx.l.google.com.
    • SOA
      • slack.com. TTL 900 ns-1493.awsdns-58.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 300

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.

  • ns-1493.awsdns-58.org 205.251.197.213 Found and Match. (Missing from Zone Address Records )
  • ns-1901.awsdns-45.co.uk 205.251.199.109 Found and Match. (Missing from Zone Address Records )
  • ns-606.awsdns-11.net 205.251.194.94 Found and Match. (Missing from Zone Address Records )
  • ns-166.awsdns-20.com 205.251.192.166 Found and Match. (Missing from Zone Address Records )
  • All Name Servers on Different Subnets

Processing 8 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=reject (The Policy to implement on FAIL)
  • 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)

Unknown Record:

We cannot identify this record. If you know what it is and its no longer needed then remove it

  • ossrh-54733

Google Domain Verification Record

This record is used by Google to validate domain ownership when setting up Google Analytics etc

  • google-site-verification=2pk67ovpnyets1avslr3phh5nsifuticbqv_bt4pm2k

Google Domain Verification Record

This record is used by Google to validate domain ownership when setting up Google Analytics etc

  • google-site-verification=kqx3ngw0xejz_0gvx_xwfflcoo-bskhqu_lxv0q77mk

Google Domain Verification Record

This record is used by Google to validate domain ownership when setting up Google Analytics etc

  • google-site-verification=efuxt5-omr2cdnmvi6a9io29kmkifpsed1qokxjwwce

Google Domain Verification Record

This record is used by Google to validate domain ownership when setting up Google Analytics etc

  • google-site-verification=kb1kvgpsk9ykhsfmsj1vpi5ymdvfkctpxnplhgjyqte

Google Domain Verification Record

This record is used by Google to validate domain ownership when setting up Google Analytics etc

  • google-site-verification=v-llb__ihraai7zzue3jvrfim2verplzwoepaezjtkq

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)
  • ip4:54.240.37.228/31 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:54.240.35.24/29 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:54.240.35.20/30 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:69.169.237.194 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:69.169.237.192/31 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:69.169.237.184/29 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:69.169.237.180/30 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:69.169.237.179 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • include:_spf.qualtrics.com (An Include - Additional look-ups required, some server's won't bother.)
  • -all (Permit ONLY the hosts listed)

Processing 5 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 1 handled by host aspmx.l.google.com. [173.194.76.26] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 10 handled by host aspmx2.googlemail.com. [209.85.233.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 10 handled by host aspmx3.googlemail.com. [142.250.4.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 5 handled by host alt1.aspmx.l.google.com. [209.85.233.26] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open
  • Priority 5 handled by host alt2.aspmx.l.google.com. [142.250.4.27] Valid
    • Email Handled By Google Corporation
    • Port 25 (smtp) : Open

Processing 0 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.

    Processing 1 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: slack.com. = IP: [3.10.95.11] 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

      Processing Domain Public Records

      • We have been unable to find the website IP from the zone
      • Performed an additional out-of-zone lookup to find website host [3.10.95.11]
      • Domain Name WHOIS Information - slack.com

        • Domain Name SLACK.COM
        • Registry Domain ID 900992_DOMAIN_COM-VRSN
        • Registrar WHOIS Server whois.markmonitor.com
        • Registrar URL: http://www.markmonitor.com
        • Updated Date: 2019-09-18T09:14:52Z
        • Creation Date: 1992-10-21T04:00:00Z
        • Registry Expiry Date: 2021-10-20T04:00:00Z
        • Registrar MarkMonitor Inc.
        • Registrar IANA ID 292
        • Registrar Abuse Contact Email This email address is being protected from spambots. You need JavaScript enabled to view it.
        • Registrar Abuse Contact Phone +1.2083895740
        • Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
        • Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
        • Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
        • Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
        • Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
        • Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
        • Name Server NS-1493.AWSDNS-58.ORG
        • Name Server NS-166.AWSDNS-20.COM
        • Name Server NS-1901.AWSDNS-45.CO.UK
        • Name Server NS-606.AWSDNS-11.NET
        • DNSSEC unsigned
        • URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

        Website Hosting WHOIS Information - 3.10.95.11

        • Amazon Technologies Inc. AT-88-Z (NET-3-0-0-0-1) 3.0.0.0 - 3.127.255.255
        • Amazon Data Services UK AMAZON-LHR (NET-3-8-0-0-1) 3.8.0.0 - 3.11.255.255

      Processing Website

        Website Headers for www.slack.com

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

        • Web Server is Apache
        • Server header does not contain version information
        • Request Response HTTP/1.1 302 Found Moved Temporarily
        • SSL is available and enabled
          • /C=US/ST=CA/L=San Francisco/O=Slack Technologies, Inc./CN=slack.comUSCA
          • Locality San Francisco
          • Organisation Slack Technologies, Inc.
          • Certificate Scope slack.com
          Certificate Issuer
          • Country US
          • Organisation DigiCert Inc
          • Certificate Scope DigiCert SHA2 Secure Server CA
          Certificate Validity
          • Valid From 180208000000Z
          • Valid To 210212120000Z
          Certificate Ciphers
          • SN RSA-SHA256
          • LN sha256WithRSAEncryption
          Certificate Extensions
          • Alternative Hostnames DNS:slack.com, DNS:*.slack.com
          • Key Usage TLS Web Server Authentication, TLS Web Client Authentication
      • There was a redirect to https://www.slack.com/
      • There was a SECOND redirect https://slack.com/
      • General

        • allow Valid methods for a specified resource after a 405 : Missing
        • location For Redirects specifies the target [https://slack.com/]
        • connection Control options for the current connection : Missing
        • 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 [no-referrer]
        • 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 [SAMEORIGIN, SAMEORIGIN]

        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]
        • date The date and time of generation [Wed, 12 Aug 2020 09:55:15 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 [Accept-Encoding]
        • x-content-type-options Types in Content-Type should NOT be changed : Missing

        Cache

        • cache-control Tells caches whether they may cache this object : Missing
        • 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-slack-backend [r]
        • x-via [haproxy-www-a4vx,haproxy-edge-lhr-d1up]

      Robots.txt

      • You have a robots.txt file and it appears to be valid
        • Allow Entries (0) - Specific Allow
          • Disallow Entries (4) - Specific Disallow
            • Sitemap Entries (1) - Sitemaps
              • https://slack.com/sitemap.xml
            • Other Entries (1)

          Processing Website Profile Data

            Website Render for www.slack.com

            Technology Profile slack.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.slack.com/

            We will retrieve your Ranking Profile from Moz.com

            • 111568 The number of external, equity links
            • 117100 The number of internal and external equity and non-equity links
            • 89 The Domain Authority (DA) ( 0->100 )
            • 67 The Page Authority (PA) ( 0->100 )
            • 6.699999809 The MozRank of the Domain ( 0->10 )

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

            We will retrieve Safe Browsing Status from Google

            • This site is NOT listed as being unsafe by Google

            PhishTank Lookup https://www.slack.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.slack.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.slack.com/

            We will check the entire body for metadata

            • description : Slack is where work flows. It’s where the people you need, the information you share and the tools you use come together to get things done.
            • twitter:site : @slackhq
            • twitter:card : summary_large_image
            • twitter:title : Where work happens
            • twitter:description : Slack is where work flows. It’s where the people you need, the information you share and the tools you use come together to get things done.
            • twitter:image : https://a.slack-edge.com/68794/marketing/img/homepage/hp-prospect/unfurl/slack-homepage-unfurl.en-GB.jpg
            • superfish : nofish
            • author : Slack
            • viewport : width=device-width, initial-scale=1
            • referrer : same-origin

          Processing Completed

          • Performance Profile
            • DNS Lookups : 0.21 seconds
            • DNS Folding/Unfolding : 0.00 seconds
            • DNS Nameserver Checks : 0.00 seconds
            • DNS TXT Records : 0.00 seconds
            • DNS MX Records : 0.75 seconds
            • DNS CNAME : 0.00 seconds
            • DNS Address : 10.01 seconds
            • WHOIS Lookups : 0.45 seconds
            • First CURL : 0.05 seconds
            • Second CURL : 0.31 seconds
            • SSL Lookup : 0.88 seconds
            • Header Parsing : 0.00 seconds
            • Robots.txt Parsing : 0.18 seconds
            • Website Profile : 8.97 seconds
            • Website MozData : 0.27 seconds
            • Safe Browsing : 0.07 seconds
            • PhishTank : 0.07 seconds
            • Website Alexa : 0.53 seconds
            • Website META : 0.62 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.