Analysis report on domain: cctld.co favicon

cctld.co
Generated on
30 Jun 2018 11:18
Duration of the analysis
6.2s
Share

Score 82%
D
DNS
A
DOMAIN
A
MAIL
A
WEB
D

Resume

Domain have "A" field

Host has no "A" (IPv4) field.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

HTTPS port (443) is open

The https port is close while there is a website.

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

Content Security Policy header is present

The Content-Security-Policy header was not found.

Content Type Options header is present

The X-Content-Type-Options header was not found.

HTTP port (80) is open

The http port is close while there is a website.

DNS

Dns servers for co

cctld.co was detected as host

Host informations

Ips
     
    Cname
    -

    Query informations

    Server
    l.root-servers.net
    [ 199.7.83.42 ]
    Duration
    108 ms
    Type
    authority
    Headers
    RCODE : 0AA : 0TC : 0

    Response

    Query informations

    Server
    ns1.cctld.co
    [ 156.154.100.25 ]
    Duration
    2 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    Query informations

    Server
    ns2.cctld.co
    [ 156.154.101.25 ]
    Duration
    3 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    Query informations

    Server
    ns3.cctld.co
    [ 156.154.102.25 ]
    Duration
    15 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    Query informations

    Server
    ns4.cctld.co
    [ 156.154.103.25 ]
    Duration
    15 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    Query informations

    Server
    ns5.cctld.co
    [ 156.154.104.25 ]
    Duration
    3 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    Query informations

    Server
    ns6.cctld.co
    [ 156.154.105.25 ]
    Duration
    3 ms
    Type
    unknown
    Headers
    RCODE : 0AA : 1TC : 0

    BIND version is hidden

    Passed

    The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

    1.031s

    Domain have at least 2 DNS servers

    Passed

    In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.

    RFC

    0.000s

    All Dns servers are responding

    Passed

    Every DNS servers should be accessible and accept public query.

    0.002s

    All servers return success

    Passed

    It's important that all servers returned a "success" code.

    0.002s

    Responses are not CNAME or A

    Passed

    The answers should not be a CNAME or A type.

    RFC

    0.001s

    DNS servers IP are differents

    Passed

    IPs for DNS servers must be different in order to have high availability.

    0.000s

    DNS servers IP are in different class C

    Passed

    The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.

    RFC

    0.000s

    SOA are synchronized

    Passed

    The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.

    0.000s

    SOA email is valid

    Passed

    An email address must respect some conditions to be valid, accordding to the RFC 5322.

    RFC

    0.000s

    SOA refresh is valid

    Passed

    The refresh value be must between 1200 and 43200.

    RFC

    0.000s

    SOA retry, refresh and expire values are correct

    Passed

    The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

    RFC

    0.000s

    DNS servers are not open relay

    Passed

    DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.

    0.029s

    Transfer zone is disable

    Passed

    An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.

    documentation

    0.085s

    Recursive query is disable

    Passed

    Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

    RFC documentation documentation

    0.030s

    DNS servers IP are not private

    Passed

    It is strictly forbidden to have private IP in DNS

    documentation

    0.000s

    Same MX are returned

    Passed

    It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.

    0.030s

    DNS servers are synchronized

    Skipped

    The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".

    0.000s

    Domain

    Whois

    Registrar
    -
    Owner
    Created at
    unknown
    Changed at
    unknown
    Expires at
    unknown

    Reputation

    Google Safe Browsing
    Web of trust
    Blacklists
    Virus Total
    Domain
    Whois server
    whois.nic.co
    Created at
    unknown
    Changed at
    unknown
    Expires at
    unknown
    Name servers
    Owner
    Name
    Organization
    Address
    -
    City
    Zip code
    Country
    CO
    Phone
    Email
    please query the rdds service of the registrar of record identified in this output for information on how to contact the registrant, admin, or tech contact of the queried domain name.
    Admin
    Name
    Organization
    Address
    -
    City
    Zip code
    Country
    Phone
    Email
    please query the rdds service of the registrar of record identified in this output for information on how to contact the registrant, admin, or tech contact of the queried domain name.
    Tech
    Name
    Organization
    Address
    -
    City
    Zip code
    Country
    Phone
    Email
    please query the rdds service of the registrar of record identified in this output for information on how to contact the registrant, admin, or tech contact of the queried domain name.

    Google Safe Browsing

    Status

    Web of Trust

    Status

    Blacklists

    RFC Ignorant
    Rbl Jp
    RblDns
    Sorbs
    Spam Eating Monkey
    SpamHaus
    SuRbl
    Support Intelligence
    Swinog
    UriBl

    Virus Total

    Detection ratio
    0 / 67

    Scans

    ADMINUSLabs
    AegisLab WebGuard
    AlienVault
    Antiy-AVL
    Avira
    Baidu-International
    BitDefender
    Blueliv
    C-SIRT
    CLEAN MX
    Certly
    Comodo Site Inspector
    CyRadar
    CyberCrime
    DNS8
    Dr.Web
    ESET
    Emsisoft
    Fortinet
    FraudScore
    FraudSense
    G-Data
    Google Safebrowsing
    K7AntiVirus
    Malc0de Database
    Malekal
    Malware Domain Blocklist
    MalwareDomainList
    MalwarePatrol
    Malwarebytes hpHosts
    Malwared
    Nucleon
    OpenPhish
    Opera
    Phishtank
    Quttera
    Rising
    SCUMWARE.org
    SecureBrain
    Spam404
    Sucuri SiteCheck
    Tencent
    ThreatHive
    Trustwave
    VX Vault
    Virusdie External Site Scan
    Web Security Guard
    Webutation
    Yandex Safebrowsing
    ZCloudsec
    ZDB Zeus
    ZeroCERT
    Zerofox
    ZeusTracker
    desenmascara.me
    malwares.com URL checker
    securolytics
    zvelo
    AutoShun
    Forcepoint ThreatSeeker
    Kaspersky
    Netcraft
    NotMining
    PhishLabs
    Sophos
    StopBadware
    URLQuery

    Domain is not blacklisted

    Passed

    A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

    0.000s

    Domain is not listed in Google Safe Browsing

    Passed

    Google safe browsing categorizes a domain as bad if something suspicious is detected.

    0.000s

    Domain is not listed in VirusTotal

    Passed

    Virus Total analyze your domain or IP address with 66 antivirus.

    0.000s

    Domain have good reputation on Web of Trust

    Passed

    Web Of Trust rates thousands of websites and find threats if they exist.

    0.000s

    DNS servers are same in dns tree and whois

    Skipped

    The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

    0.001s

    Mail

    There is no mail server.

    This domain has no MX server

    MX servers are accessibles

    Skipped

    Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

    0.000s

    MX IPs have reverse

    Skipped

    When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup, called a PTR lookup, named after the type of DNS record used. If the result of the reverse lookup matches the result of a forward DNS Lookup, then it's much more likely that the message is legitimate. If the IP address doesn't match, it's much more likely that the sending address was spoofed and therefore much more likely that it's unwanted and could be considered spam.

    documentation

    0.000s

    HELO command is accepted

    Skipped

    According to the RFC 2181, smtp server should accept HELO command

    RFC

    0.000s

    EHLO command is accepted

    Skipped

    According to the RFC 2181, smtp server should accept EHLO command

    RFC

    0.000s

    STARTTLS command is accepted

    Skipped

    STARTTLS turns an unencrypted connection into a secure connection.

    0.000s

    EXPN command is refused

    Skipped

    EXPN command is now considered to be a security risk, spammers being able to harvest valid e-mail addresses via each mailing list.

    0.000s

    VRFY command is refused

    Skipped

    As the EXPN command, VRFY is used by spammers to verify an address.

    0.000s

    MX servers are not open relay

    Skipped

    If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.

    0.000s

    MX servers accept abuse@ address

    Skipped

    According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

    RFC

    0.000s

    MX servers accept postmaster@ address

    Skipped

    According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

    RFC

    0.000s

    Banner return 2xx or 4xx code

    Skipped

    The banner must return (2xx) a valid (4xx) or temporary code.

    0.000s

    Banner return server name

    Skipped

    Banner must contain the name of the server

    0.000s

    SMTP server type is hidden

    Skipped

    There is a risk to display the type and the version of the server, because people can find a breach for a specific version and use it

    0.000s

    Web

    Website

    Url
    https://cctld.co/
    Https
    Title
    Unknown
    Description
    Unknown
    First paragraph
    Unknown
    Url
    http://cctld.co/
    Title
    Unknown
    Description
    Unknown
    Response time
    0.002 second
    Server
    Unknown
    Powered by
    Unknown
    Encoding
    Unknown
    HSTS
    Url
    https://cctld.co/
    Title
    Unknown
    Description
    Unknown
    Response time
    0.002 second
    Server
    Unknown
    Powered by
    Unknown
    Encoding
    Unknown
    HSTS

    Domain have "A" field

    Host has no "A" (IPv4) field.

    The domain must have an A field in order for the website to be accessible.

    0.000s

    Domain have "AAAA" field

    Host has no "AAAA" (IPv6) field.

    It is highly recommended to have an IPv6 for the website.

    0.000s

    HTTPS port (443) is open

    The https port is close while there is a website.

    This test verifies the presence of a website for the given IP or domain. Then scans port 443.
    If the domain or IP is pointing to a website then port 443 must be open so that it can be accessed from a browser.
    Otherwise port 443 must be closed.

    0.000s

    X-XSS-Protection header is present

    The X-XSS-Protection header was not found.

    The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.

    documentation

    0.000s

    Content Security Policy header is present

    The Content-Security-Policy header was not found.

    The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (XSS).

    documentation

    0.000s

    Content Type Options header is present

    The X-Content-Type-Options header was not found.

    The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.

    0.000s

    HTTP port (80) is open

    The http port is close while there is a website.

    This test verifies the presence of a website for the given IP or domain. Then scans port 80.
    If the domain or IP is pointing to a website then port 80 must be open so that it can be accessed from a browser.
    Otherwise port 80 must be closed.

    0.000s

    Web server version is hidden

    Passed

    To avoid giving details to malicious people, the version of the server should not be visible.

    0.000s

    Web application technology is hidden

    Passed

    To avoid giving details to malicious people, the technology that supports the application should not be visible.

    0.000s

    Host "www" have "A" field

    Skipped

    WWW host is not required for a website, but it's better to have one.

    0.000s

    Host "www" have "AAAA" field

    Skipped

    If you configure a WWW host for your website, it is recommended to have an IPv6.

    0.000s

    Cookies are secure

    Skipped

    Using "HttpOnly" instruction prevents someone to access to cookies via Javascript. The secure flag will allow you to prevent a cookie from ever being communicated in simple HTTP. (RFC 6265 section 8.3)

    RFC

    0.000s