DNS & HTTP Analysis for outlook.com

Processing Domain outlook.com on 30/03/2019 21:21:27


  • 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.004
  • The version that produced this report is 1.015b

Processing DNS Records

Basic Checks

Here we check the basic functioning and security of your DNS

  • Zone Queries 7 Record Types and 27 Records Found
  • Zone Transfer Failed
  • Zone Dump
    • TXT
      • _dmarc.outlook.com. TTL 3600 "v=DMARC1; p=none; sp=quarantine; 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.; fo=1"
      • outlook.com. TTL 300 "google-site-verification=0iLWhIMhXEkeWwWfFU4ursTn-_OvoOjaA0Lr7Pg1sEM"
      • outlook.com. TTL 300 "google-site-verification=DC2uC-T8kD33lINhNzfo0bNBrw-vrCXs5BPF5BXY56g"
      • outlook.com. TTL 300 "v=spf1 include:spf-a.outlook.com include:spf-b.outlook.com ip4:157.55.9.128/25 include:spf.protection.outlook.com include:spf-a.hotmail.com include:_spf-ssg-b.microsoft.com include:_spf-ssg-c.microsoft.com ~all"
    • A
      • ns1.msft.net. TTL 300 208.84.0.53
      • ns2.msft.net. TTL 172800 208.84.2.53
      • ns3.msft.net. TTL 300 193.221.113.53
      • ns4.msft.net. TTL 172800 208.76.45.53
      • outlook.com. TTL 300 40.97.116.82
      • outlook.com. TTL 300 40.97.128.194
      • outlook.com. TTL 300 40.97.148.226
      • outlook.com. TTL 300 40.97.153.146
      • outlook.com. TTL 300 40.97.156.114
      • outlook.com. TTL 300 40.97.160.2
      • outlook.com. TTL 300 40.97.161.50
      • outlook.com. TTL 300 40.97.164.146
    • AAAA
      • ns1.msft.net. TTL 300 2620:0:30:0:0:0:0:53
      • ns2.msft.net. TTL 172800 2620:0:32:0:0:0:0:53
      • ns3.msft.net. TTL 300 2620:0:34:0:0:0:0:53
      • ns4.msft.net. TTL 172800 2620:0:37:0:0:0:0:53
    • NS
      • outlook.com. TTL 172800 ns1.msft.net.
      • outlook.com. TTL 172800 ns2.msft.net.
      • outlook.com. TTL 172800 ns3.msft.net.
      • outlook.com. TTL 172800 ns4.msft.net.
    • MX
      • outlook.com. TTL 300 5 outlook-com.olc.protection.outlook.com.
    • SOA
      • outlook.com. TTL 300 sn2mgt0101dc121.prdmgt01.prod.exchangelabs.com. msnhst.microsoft.com. 2014269565 300 900 2419200 300
    • CNAME
      • www.outlook.com. TTL 300 outlook.office365.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.

  • ns1.msft.net 208.84.0.53 Found and Match. (Found in Address Records)
  • ns3.msft.net 193.221.113.53 Found and Match. (Found in Address Records)
  • ns2.msft.net 208.84.2.53 Found and Match. (Found in Address Records)
  • ns4.msft.net 208.76.45.53 Found and Match. (Found in Address Records)

Processing 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=none (The Policy to implement on FAIL)
  • sp=quarantine (The Policy to implement for subdomains 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)
  • ruf=mailto:This email address is being protected from spambots. You need JavaScript enabled to view it. (Reporting URI for forensic reports)
  • fo=1 (Dictates what type of authentication/alignment vulnerabilities are reported)

Google Domain Verification Record

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

  • google-site-verification=0ilwhimhxekewwwffu4urstn-_ovoojaa0lr7pg1sem

Google Domain Verification Record

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

  • google-site-verification=dc2uc-t8kd33linhnzfo0bnbrw-vrcxs5bpf5bxy56g

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-a.outlook.com (The SPF Record listed here should be used - Additional look-ups required)
  • include:spf-b.outlook.com (The SPF Record listed here should be used - Additional look-ups required)
  • ip4:157.55.9.128/25 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • include:spf.protection.outlook.com (The SPF Record listed here should be used - Additional look-ups required)
  • include:spf-a.hotmail.com (The SPF Record listed here should be used - Additional look-ups required)
  • include:_spf-ssg-b.microsoft.com (The SPF Record listed here should be used - Additional look-ups required)
  • include:_spf-ssg-c.microsoft.com (The SPF Record listed here should be used - Additional look-ups required)
  • ~all (Permit servers listed in A records - Not a great idea)

Processing 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 5 handled by host outlook-com.olc.protection.outlook.com. [104.47.10.33] Valid
    • Email Handled By Microsoft Corporation
    • Port 25 (smtp) : Open

Processing 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.outlook.com. outlook.office365.com.

Processing 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: ns1.msft.net. = IP: [208.84.0.53] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: ns2.msft.net. = IP: [208.84.2.53] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: ns3.msft.net. = IP: [193.221.113.53] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: ns4.msft.net. = IP: [208.76.45.53] Valid Reachable (20.118ms)
  • Host: outlook.com. = IP: [40.97.116.82] Valid Reachable (156.043ms)
  • Host: outlook.com. = IP: [40.97.128.194] Valid Reachable (119.429ms)
  • Host: outlook.com. = IP: [40.97.148.226] Valid Reachable (134.183ms)
  • Host: outlook.com. = IP: [40.97.153.146] Valid Reachable (92.135ms)
  • Host: outlook.com. = IP: [40.97.156.114] Valid Reachable (133.815ms)
  • Host: outlook.com. = IP: [40.97.160.2] Valid Reachable (155.654ms)
  • Host: outlook.com. = IP: [40.97.161.50] Valid Reachable (155.195ms)
  • Host: outlook.com. = IP: [40.97.164.146] Valid Reachable (120.073ms)

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: ns1.msft.net. = IP: [2620:0:30:0:0:0:0:53] Valid
  • Host: ns2.msft.net. = IP: [2620:0:32:0:0:0:0:53] Valid
  • Host: ns3.msft.net. = IP: [2620:0:34:0:0:0:0:53] Valid
  • Host: ns4.msft.net. = IP: [2620:0:37:0:0:0:0:53] Valid

Processing Domain Public Records

    Domain Name WHOIS Information - outlook.com

    • Domain Name OUTLOOK.COM
    • Registry Domain ID 2019401_DOMAIN_COM-VRSN
    • Registrar WHOIS Server whois.markmonitor.com
    • Registrar URL: http://www.markmonitor.com
    • Updated Date: 2018-07-16T09:30:46Z
    • Creation Date: 1994-08-18T04:00:00Z
    • Registry Expiry Date: 2019-08-17T04: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 NS1.MSFT.NET
    • Name Server NS1A.O365FILTERING.COM
    • Name Server NS2.MSFT.NET
    • Name Server NS2A.O365FILTERING.COM
    • Name Server NS3.MSFT.NET
    • Name Server NS4.MSFT.NET
    • Name Server NS4A.O365FILTERING.COM
    • DNSSEC unsigned
    • URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

    Website Hosting WHOIS Information - 208.84.0.53

    • NetRange 208.84.0.0 - 208.84.7.255
    • CIDR 208.84.0.0/21
    • NetHandle NET-208-84-0-0-1
    • Parent NET208 (NET-208-0-0-0-0)
    • NetType Direct Assignment
    • OriginAS
    • Organization Microsoft Corporation (MSFT)
    • RegDate 2007-10-23
    • Updated 2017-01-13
    • Ref: https://rdap.arin.net/registry/ip/208.84.0.0
    • OrgName Microsoft Corporation
    • OrgId MSFT
    • Address One Microsoft Way
    • City Redmond
    • StateProv WA
    • PostalCode 98052
    • Country US
    • RegDate 1998-07-09
    • Updated 2017-01-28
    • Ref: https://rdap.arin.net/registry/entity/MSFT
    • OrgTechHandle MRPD-ARIN
    • OrgTechName Microsoft Routing, Peering, and DNS
    • OrgTechPhone +1-425-882-8080
    • OrgTechEmail This email address is being protected from spambots. You need JavaScript enabled to view it.
    • OrgTechRef: https://rdap.arin.net/registry/entity/MRPD-ARIN
    • OrgAbuseHandle MAC74-ARIN
    • OrgAbuseName Microsoft Abuse Contact
    • OrgAbusePhone +1-425-882-8080
    • OrgAbuseEmail This email address is being protected from spambots. You need JavaScript enabled to view it.
    • OrgAbuseRef: https://rdap.arin.net/registry/entity/MAC74-ARIN

Processing Website

    Website Headers for www.outlook.com

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

    • Web Server is Microsoft-IIS/10.0
    • Request Response HTTP/1.1 301 Moved Permanently Moved Permanently
    • SSL is available and enabled
      • Certificate Name /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=outlook.com
      • Certificate Issued To
        • Country US
        • City Washington
        • Locality Redmond
        • Organisation Microsoft Corporation
        • Certificate Scope outlook.com
        Certificate Issuer
        • Country US
        • Organisation DigiCert Inc
        • Certificate Scope DigiCert Cloud Services CA-1
        Certificate Validity
        • Valid From 180801000000Z
        • Valid To 200801120000Z
        Certificate Ciphers
        • SN RSA-SHA256
        • LN sha256WithRSAEncryption
        Certificate Extensions
        • Alternative Hostnames DNS:*.clo.footprintdns.com, DNS:*.nrb.footprintdns.com, DNS:*.hotmail.com, DNS:*.internal.outlook.com, DNS:*.live.com, DNS:*.office.com, DNS:*.office365.com, DNS:*.outlook.com, DNS:*.outlook.office365.com, DNS:attachment.outlook.live.net, DNS:attachment.outlook.office.net, DNS:attachment.outlook.officeppe.net, DNS:ccs.login.microsoftonline.com, DNS:ccs-sdf.login.microsoftonline.com, DNS:hotmail.com, DNS:mail.services.live.com, DNS:office365.com, DNS:outlook.com, DNS:outlook.office.com, DNS:substrate.office.com, DNS:substrate-sdf.office.com, DNS:attachments.office.net
        • Key Usage TLS Web Server Authentication, TLS Web Client Authentication
    • There was a redirect to http://outlook.live.com/
    • There was a SECOND redirect https://outlook.live.com/
    • General

      • allow Valid methods for a specified resource after a 405 Missing
      • location For Redirects specifies the target [https://outlook.live.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

      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 [0]
      • content-type The Media type of the Response Body Missing
      • date The date and time of generation [Sat, 30 Mar 2019 21:18:18 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 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 Missing

      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

      Not Profiled

      • x-msedge-ref [Ref A]

    Robots.txt

    • You have a robots.txt file and it appears to be valid
      • Allow Entries (0) - Specific Allow
        • Disallow Entries (0) - Specific Disallow
          • Sitemap Entries (0) - Sitemaps
            • Other Entries (10)

        Processing Website Profile Data

          Website Render for www.outlook.com

          Technology Profile outlook.com

          We will check for fingerprints of common website technologies

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

          Meta Profile http://outlook.live.com/

          We will check the entire body for metadata

          • robots : none
          • pageid : i5030
          • siteid : 292841
          • reqlc : 1033
          • loclc : 1033
          • viewport : width=device-width, initial-scale=1.0, maximum-scale=2.0, minimum-scale=1.0, user-scalable=yes

        Processing Completed

        • Performance Profile
          • DNS Lookups : 0.36 seconds
          • DNS Folding/Unfolding : 0.00 seconds
          • DNS Nameserver Checks : 0.00 seconds
          • DNS TXT Records : 0.00 seconds
          • DNS MX Records : 0.14 seconds
          • DNS CNAME : 0.00 seconds
          • DNS Address : 31.21 seconds
          • WHOIS Lookups : 0.44 seconds
          • First CURL : 0.09 seconds
          • Second CURL : 0.09 seconds
          • SSL Lookup : 1.17 seconds
          • Header Parsing : 0.00 seconds
          • Robots.txt Parsing : 0.45 seconds
          • Website Profile : 4.68 seconds
          • Website META : 0.99 seconds

        The process is now completed and the results are shown above. 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.