DNS & HTTP Analysis for phishtank.com

Details
Category: Tool Processing Reports

Processing Domain phishtank.com on 25/04/2019 15:41:12


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

Processing DNS Records

Basic Checks

Here we check the basic functioning and security of your DNS

  • Zone Queries 6 Record Types and 10 Records Found
  • Zone Transfer Failed
  • Zone Dump
    • A
      • mail01.phishtank.com. TTL 300 34.237.97.135
      • phishtank.com. TTL 300 104.16.101.75
      • phishtank.com. TTL 300 104.17.177.85
    • AAAA
      • phishtank.com. TTL 300 2606:4700:0:0:0:0:6810:654b
      • phishtank.com. TTL 300 2606:4700:0:0:0:0:6811:b155
    • MX
      • phishtank.com. TTL 300 100 mail01.phishtank.com.
    • TXT
      • phishtank.com. TTL 300 "v=spf1 ip4:34.237.97.135/32 a mx include:mailgun.org include:amazonses.com ?all"
    • SOA
      • phishtank.com. TTL 3600 fiona.ns.cloudflare.com. dns.cloudflare.com. 2029917424 10000 2400 604800 3600
    • NS
      • phishtank.com. TTL 86400 fiona.ns.cloudflare.com.
      • phishtank.com. TTL 86400 lakas.ns.cloudflare.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.

  • fiona.ns.cloudflare.com 173.245.58.157 Found and Match. (Missing from Zone Address Records )
  • fiona.ns.cloudflare.com Found and Match. (Missing from Zone Address Records )
  • lakas.ns.cloudflare.com 173.245.59.194 Found and Match. (Missing from Zone Address Records )
  • lakas.ns.cloudflare.com Found and Match. (Missing from Zone Address Records )
  • All Name Servers SHOULD BE on Different Subnets

Processing 1 TXT Records

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:34.237.97.135/32 (The IPv4 Address of a permitted sender - make sure this scopes your outgoing mail server)
  • a (Permit servers listed in A records -extra lookup, some server's won't bother)
  • mx (Permit servers listed in MX records -extra lookup, some server's won't bother)
  • include:mailgun.org (An Include - Additional look-ups required, some server's won't bother.)
  • include:amazonses.com (An Include - Additional look-ups required, some server's won't bother.)
  • ?all (SPF Result is neutral and has no effect)

Processing 1 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 100 handled by host mail01.phishtank.com. [34.237.97.135] Valid
    • Email Handled Locally
    • Forward DNS 34.237.97.135 mail01.phishtank.com
      • Reverse DNS mail01.phishtank.com 34.237.97.135
    • Port 25 (smtp) : Open
      • Not Listed in any blacklists

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 3 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: mail01.phishtank.com. = IP: [34.237.97.135] Valid Unreachable TX:1 RX:0 LOSS:100%
    • Host: phishtank.com. = IP: [104.16.101.75] Valid Reachable (12.895ms)
    • Host: phishtank.com. = IP: [104.17.177.85] Valid Reachable (12.424ms)

    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: phishtank.com. = IP: [2606:4700:0:0:0:0:6810:654b] Valid
    • Host: phishtank.com. = IP: [2606:4700:0:0:0:0:6811:b155] Valid

    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 [104.17.177.85]

      • Domain Name WHOIS Information - phishtank.com

      • Domain Name PHISHTANK.COM
      • Registry Domain ID 386602188_DOMAIN_COM-VRSN
      • Registrar WHOIS Server whois.PublicDomainRegistry.com
      • Registrar URL: http://www.publicdomainregistry.com
      • Updated Date: 2019-02-22T20:33:36Z
      • Creation Date: 2006-03-24T00:26:15Z
      • Registry Expiry Date: 2020-03-23T23:26:15Z
      • Registrar PDR Ltd. d/b/a PublicDomainRegistry.com
      • Registrar IANA ID 303
      • Registrar Abuse Contact Email This email address is being protected from spambots. You need JavaScript enabled to view it.
      • Registrar Abuse Contact Phone +1.2013775952
      • Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
      • Name Server FIONA.NS.CLOUDFLARE.COM
      • Name Server LAKAS.NS.CLOUDFLARE.COM
      • DNSSEC unsigned
      • URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

      Website Hosting WHOIS Information - 104.17.177.85

      • NetRange 104.16.0.0 - 104.31.255.255
      • CIDR 104.16.0.0/12
      • NetHandle NET-104-16-0-0-1
      • Parent NET104 (NET-104-0-0-0-0)
      • NetType Direct Assignment
      • OriginAS AS13335
      • Organization Cloudflare, Inc. (CLOUD14)
      • RegDate 2014-03-28
      • Updated 2017-02-17
      • Ref: https://rdap.arin.net/registry/ip/104.16.0.0
      • OrgName Cloudflare, Inc.
      • OrgId CLOUD14
      • Address 101 Townsend Street
      • City San Francisco
      • StateProv CA
      • PostalCode 94107
      • Country US
      • RegDate 2010-07-09
      • Updated 2018-10-10
      • Ref: https://rdap.arin.net/registry/entity/CLOUD14
      • OrgAbuseHandle ABUSE2916-ARIN
      • OrgAbuseName Abuse
      • OrgAbusePhone +1-650-319-8930
      • OrgAbuseEmail abuse@cloudflare.com
      • OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN
      • OrgNOCHandle NOC11962-ARIN
      • OrgNOCName NOC
      • OrgNOCPhone +1-650-319-8930
      • OrgNOCEmail noc@cloudflare.com
      • OrgNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN
      • OrgTechHandle ADMIN2521-ARIN
      • OrgTechName Admin
      • OrgTechPhone +1-650-319-8930
      • OrgTechEmail rir@cloudflare.com
      • OrgTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN
      • RNOCHandle NOC11962-ARIN
      • RNOCName NOC
      • RNOCPhone +1-650-319-8930
      • RNOCEmail noc@cloudflare.com
      • RNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN
      • RTechHandle ADMIN2521-ARIN
      • RTechName Admin
      • RTechPhone +1-650-319-8930
      • RTechEmail rir@cloudflare.com
      • RTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN
      • RAbuseHandle ABUSE2916-ARIN
      • RAbuseName Abuse
      • RAbusePhone +1-650-319-8930
      • RAbuseEmail abuse@cloudflare.com
      • RAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN

    Processing Website

      Website Headers for www.phishtank.com

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

      • Web Server is cloudflare
      • Server header does not contain version information
      • Request Response HTTP/1.1 403 Forbidden Forbidden
      • SSL is not available
      • There was no redirection

        • 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

        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 [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; charset=UTF-8]
        • date The date and time of generation [Thu, 25 Apr 2019 15:37:38 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 [max-age=15]
        • expires Gives the date/time after which the response is considered stale [Thu, 25 Apr 2019 15:37:53 GMT]
        • 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 [__cfduid=d5dc4709e3e67bda5ccdefd2794e1c0871556206658; expires=Fri, 24-Apr-20 15:37:38 GMT; path=/; domain=.phishtank.com; HttpOnly]

        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

        • cf-ray [4cd166407c0769dd-LHR]

      Robots.txt

      • You do not appear to have a robots.txt file. This is ok

    Processing Website Profile Data

      Website Render for www.phishtank.com

      Technology Profile phishtank.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 http://www.phishtank.com/

      We will retrieve your Ranking Profile from Moz.com

      • 4555748 The number of external, equity links
      • 5330751 The number of internal and external equity and non-equity links
      • 60 The Domain Authority (DA) ( 0->100 )
      • 56 The Page Authority (PA) ( 0->100 )
      • 5.599999905 The MozRank of the Domain ( 0->10 )

      Google Safe Browsing http://www.phishtank.com/

      We will retrieve Safe Browsing Status from Google

      • This site is NOT listed as being unsafe by Google

      PhishTank Lookup http://www.phishtank.com/

      We will check PhishTank to see if your site is listed

      • This site is listed as being unsafe by PhishTank

      Alexa Rank Profile http://www.phishtank.com/

      We will retrieve your Ranking Profile from Alexa.com

      • 469 The number of external in links
      • 230850 Your Alexa Rank

      Meta Profile http://www.phishtank.com/

      We will check the entire body for metadata

      Processing Completed

      • Performance Profile
        • DNS Lookups : 0.28 seconds
        • DNS Folding/Unfolding : 0.00 seconds
        • DNS Nameserver Checks : 0.00 seconds
        • DNS TXT Records : 0.00 seconds
        • DNS MX Records : 0.13 seconds
        • DNS CNAME : 0.00 seconds
        • DNS Address : 10.06 seconds
        • WHOIS Lookups : 0.40 seconds
        • First CURL : 0.07 seconds
        • SSL Lookup : 0.07 seconds
        • Header Parsing : 0.00 seconds
        • Robots.txt Parsing : 0.07 seconds
        • Website Profile : 3.76 seconds
        • Website MozData : 0.39 seconds
        • Safe Browsing : 0.09 seconds
        • PhishTank : 0.16 seconds
        • Website Alexa : 0.77 seconds
        • Website META : 0.03 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.