DNS & HTTP Analysis for toyota.co.uk

Details
Category: Tool Processing Reports

Processing Domain toyota.co.uk on 31/03/2019 15:48: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.004
  • The version that produced this report is 1.016b

Processing DNS Records

Basic Checks

Here we check the basic functioning and security of your DNS

  • Zone Queries 6 Record Types and 14 Records Found
  • Zone Transfer Failed
  • Zone Dump
    • A
      • mailhub1.toyota.co.uk. TTL 60 81.144.233.140
      • mailhub2.toyota.co.uk. TTL 60 81.144.233.141
      • toyota.co.uk. TTL 300 149.126.74.207
    • NS
      • toyota.co.uk. TTL 172800 ns-1196.awsdns-21.org.
      • toyota.co.uk. TTL 172800 ns-1618.awsdns-10.co.uk.
      • toyota.co.uk. TTL 172800 ns-414.awsdns-51.com.
      • toyota.co.uk. TTL 172800 ns-774.awsdns-32.net.
    • TXT
      • toyota.co.uk. TTL 300 "jhaqieeie5v8ti3a71glnms160"
      • toyota.co.uk. TTL 300 "ms=ms28502731"
      • toyota.co.uk. TTL 300 "v=spf1 mx a:*.service-now.com ip4:94.193.108.177 ip4:64.78.151.128/26 ip4:207.126.144.0/20 ip4:216.241.183.0/20 include:spf.protection.outlook.com include:spf.mtasv.net include:msgfocus.com" " ip4:70.42.85.62 ip4:70.42.85.67 ip4:70.42.85.68 ip4:38.109.192.17 ip4:213.106.243.14 include:thewg.com include:thewarrantygroup.com a:*.itccompliance.co.uk include:spf-001c1001.pphosted.com -all"
    • MX
      • toyota.co.uk. TTL 3600 10 mailhub2.toyota.co.uk.
      • toyota.co.uk. TTL 3600 20 mailhub1.toyota.co.uk.
    • SOA
      • toyota.co.uk. TTL 900 ns-1618.awsdns-10.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
    • CNAME
      • www.toyota.co.uk. TTL 300 4vrns.x.incapdns.net.

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-1196.awsdns-21.org 205.251.196.172 Found and Match. (Missing from Zone Address Records )
  • ns-1618.awsdns-10.co.uk 205.251.198.82 Found and Match. (Missing from Zone Address Records )
  • ns-414.awsdns-51.com 205.251.193.158 Found and Match. (Missing from Zone Address Records )
  • ns-774.awsdns-32.net 205.251.195.6 Found and Match. (Missing from Zone Address Records )

Processing TXT Records

Unknown Record:

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

  • jhaqieeie5v8ti3a71glnms160

Microsoft Office 365 Verification Record

This record is used to identify this domain as an Office 365 domain

  • ms=ms28502731

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)
  • mx (Permit servers listed in MX records - Not a great idea)
  • a:*.service-now.com (Permit servers listed in A records - Not a great idea)
  • ip4:94.193.108.177 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:64.78.151.128/26 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:207.126.144.0/20 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:216.241.183.0/20 (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.mtasv.net (The SPF Record listed here should be used - Additional look-ups required)
  • include:msgfocus.com (The SPF Record listed here should be used - Additional look-ups required)
  • ip4:70.42.85.62 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:70.42.85.67 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:70.42.85.68 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:38.109.192.17 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • ip4:213.106.243.14 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • include:thewg.com (The SPF Record listed here should be used - Additional look-ups required)
  • include:thewarrantygroup.com (The SPF Record listed here should be used - Additional look-ups required)
  • a:*.itccompliance.co.uk (Permit servers listed in A records - Not a great idea)
  • include:spf-001c1001.pphosted.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 10 handled by host mailhub2.toyota.co.uk. [81.144.233.141] Valid
    • Email Handled Locally
    • Forward DNS 81.144.233.141 mailhub2.toyota.co.uk
      • Reverse DNS mailhub2.toyota.co.uk 81.144.233.141
    • Port 25 (smtp) : Open
      • Not Listed in any blacklists
  • Priority 20 handled by host mailhub1.toyota.co.uk. [81.144.233.140] Valid
    • Email Handled Locally
    • Forward DNS 81.144.233.140 mailhub1.toyota.co.uk
      • Reverse DNS mailhub1.toyota.co.uk 81.144.233.140
    • Port 25 (smtp) : Open
      • Not Listed in any blacklists

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.toyota.co.uk. 4vrns.x.incapdns.net.

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: mailhub1.toyota.co.uk. = IP: [81.144.233.140] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: mailhub2.toyota.co.uk. = IP: [81.144.233.141] Valid Unreachable TX:1 RX:0 LOSS:100%
  • Host: toyota.co.uk. = IP: [149.126.74.207] Valid Reachable (15.721ms)

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

      Domain Name WHOIS Information - toyota.co.uk

      • Domain name
      • toyota.co.uk
      • Data validation
      • Nominet was able to match the registrant's name and address against a 3rd party data source on 26-May-2017
      • Registrar
      • Toyota (GB) Plc t/a Toyota (GB) PLC [Tag = TOYOTA]
      • URL: http://www.toyota.co.uk
      • Relevant dates
      • Registered on before Aug-1996
      • Expiry date 06-Sep-2022
      • Last updated 07-Sep-2017
      • Registration status
      • Registered until expiry date.
      • Name servers
      • ns-1196.awsdns-21.org
      • ns-1618.awsdns-10.co.uk 205.251.198.82
      • ns-414.awsdns-51.com
      • ns-774.awsdns-32.net
      • WHOIS lookup made at 16:45:03 31-Mar-2019

      Website Hosting WHOIS Information - 81.144.233.140

      • NetRange 81.0.0.0 - 81.255.255.255
      • CIDR 81.0.0.0/8
      • NetHandle NET-81-0-0-0-1
      • Parent ()
      • NetType Allocated to RIPE NCC
      • OriginAS
      • Organization RIPE Network Coordination Centre (RIPE)
      • RegDate
      • Updated 2009-03-25
      • Ref: https://rdap.arin.net/registry/ip/81.0.0.0
      • ResourceLink: https://apps.db.ripe.net/search/query.html
      • ResourceLink whois.ripe.net
      • OrgName RIPE Network Coordination Centre
      • OrgId RIPE
      • Address P.O. Box 10096
      • City Amsterdam
      • StateProv
      • PostalCode 1001EB
      • Country NL
      • RegDate
      • Updated 2013-07-29
      • Ref: https://rdap.arin.net/registry/entity/RIPE
      • ReferralServer: whois://whois.ripe.net
      • ResourceLink: https://apps.db.ripe.net/search/query.html
      • OrgTechHandle RNO29-ARIN
      • OrgTechName RIPE NCC Operations
      • OrgTechPhone +31 20 535 4444
      • OrgTechEmail This email address is being protected from spambots. You need JavaScript enabled to view it.
      • OrgTechRef: https://rdap.arin.net/registry/entity/RNO29-ARIN
      • OrgAbuseHandle ABUSE3850-ARIN
      • OrgAbuseName Abuse Contact
      • OrgAbusePhone +31205354444
      • OrgAbuseEmail This email address is being protected from spambots. You need JavaScript enabled to view it.
      • OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE3850-ARIN
      • inetnum 81.144.233.0 - 81.144.233.255
      • country GB
      • admin-c RW3455-RIPE
      • tech-c RW3455-RIPE
      • status ASSIGNED PA
      • mnt-by BTNET-MNT
      • mnt-lower BTNET-MNT
      • mnt-routes BTNET-MNT
      • created: 2004-01-22T16:33:44Z
      • last-modified: 2013-01-16T13:55:39Z
      • source RIPE
      • person Richard Wood
      • address Great Burgh
      • address Yew tree Bottom Road
      • address Epsom
      • address Surrey
      • address KT18 5UX
      • address GB
      • phone +44 01737367471
      • nic-hdl RW3455-RIPE
      • mnt-by BTNET-MNT
      • created: 2013-01-16T13:50:40Z
      • last-modified: 2013-01-16T13:50:40Z
      • route 81.144.233.0/24
      • origin AS2856
      • mnt-by BTNET-MNT
      • created: 2012-04-11T15:01:06Z
      • last-modified: 2012-04-11T15:01:06Z
      • source RIPE

    Processing Website

      Website Headers for www.toyota.co.uk

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

      • Web Server is Apache
      • Request Response HTTP/1.1 200 OK OK
      • SSL is available and enabled
        • Certificate Name /C=GB/ST=Surrey/L=Epsom/O=Toyota (G.B.) PLC/CN=*.toyota.co.uk
          • Certificate Issued To
          • Country GB
          • City Surrey
          • Locality Epsom
          • Organisation Toyota (G.B.) PLC
          • Certificate Scope *.toyota.co.uk
          Certificate Issuer
          • Country US
          • Organisation DigiCert Inc
          • Certificate Scope DigiCert SHA2 Secure Server CA
          Certificate Validity
          • Valid From 180510000000Z
          • Valid To 200708120000Z
          Certificate Ciphers
          • SN RSA-SHA256
          • LN sha256WithRSAEncryption
          Certificate Extensions
          • Alternative Hostnames DNS:*.toyota.co.uk, DNS:toyota.co.uk
          • Key Usage TLS Web Server Authentication, TLS Web Client Authentication
      • There was a redirect to https://www.toyota.co.uk/

        • 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

        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 [170188]
        • content-type The Media type of the Response Body [text/html; charset=utf-8]
        • date The date and time of generation [Sun, 31 Mar 2019 15:45:05 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 [no-cache="set-cookie"]
        • 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 [1.1 vegur]
        • 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 [incap_ses_457_166592=WGfzGr/ekQSmgLfGZZhXBoHgoFwAAAAA3hCLU60wI5Q6ZD1EAmOGQQ==; path=/; Domain=.toyota.co.uk]

        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-oneagent-js-injection [true]
        • x-ruxit-js-agent [true]
        • x-iinfo [3-55189297-55189325 NNNN CT(0 0 0) RT(1554047104785 168) q(0 0 0 0) r(2 2) U6]
        • x-cdn [Incapsula]

      Robots.txt

      • You have a robots.txt file and it appears to be valid
        • Allow Entries (0) - Specific Allow
          • Disallow Entries (18) - Specific Disallow
            • /sys/
            • /_migration/
            • /_working_area/
            • /api/
            • /cpadmin/
            • /my-toyota/content.json
            • /my-toyota/countries.json
            • /my-toyota/languages.json
            • /my-toyota/nmsc-config.json
            • /my-toyota/nmsc-config-acc.json
            • /my-toyota/priority.json
            • /my-toyota/or - checkout.json
            • /my-toyota/preview-nmsc-config.json
            • /my-toyota/prev-nmsc-config.json
            • /my-toyota/uat-nmsc-config.json
            • /osb/
            • /sso/
            • /owners/99-service-mot-offer.json
          • Sitemap Entries (1) - Sitemaps
            • https://www.toyota.co.uk/sitemap.xml
          • Other Entries (1)

      Processing Website Profile Data

        Website Render for www.toyota.co.uk

        Technology Profile toyota.co.uk

        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.toyota.co.uk/

        We will retrieve your Ranking Profile from Moz.com

        • 30784 The number of external, equity links
        • 117497 The number of internal and external equity and non-equity links
        • 72 The Domain Authority (DA) ( 0->100 )
        • 57 The Page Authority (PA) ( 0->100 )
        • 5.699999809 The MozRank of the Domain ( 0->10 )

        Meta Profile https://www.toyota.co.uk/

        We will check the entire body for metadata

        • viewport : width=device-width, initial-scale=1.0
        • description : Welcome to Toyota UK. Find out about our new and used cars, as well as offers on all of your favourite models & much more. Contact us for more information.
        • keywords : Toyota Model Range, New Cars, Used Cars, Hybrid Cars, Small Cars, 4x4 Cars, Estate Cars, Latest Offers, Toyota Finance, Toyota 5 year warranty, Toyota News and Events,
        • msapplication-tilecolor : #f0f0f0
        • theme-color : #f0f0f0

      Processing Completed

      • Performance Profile
        • DNS Lookups : 0.43 seconds
        • DNS Folding/Unfolding : 0.00 seconds
        • DNS Nameserver Checks : 0.00 seconds
        • DNS TXT Records : 0.00 seconds
        • DNS MX Records : 0.11 seconds
        • DNS CNAME : 0.00 seconds
        • DNS Address : 20.05 seconds
        • WHOIS Lookups : 0.45 seconds
        • First CURL : 0.06 seconds
        • Second CURL : 1.86 seconds
        • SSL Lookup : 0.21 seconds
        • Header Parsing : 0.00 seconds
        • Robots.txt Parsing : 0.13 seconds
        • Website Profile : 6.73 seconds
        • Website MozData : 0.28 seconds
        • Website META : 0.10 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.