Analysis report on domain: ns2.webicom.si favicon

ns2.webicom.si has no website

Generated on
14 Oct 2021 04:05
Duration of the analysis
166.4s
Share

Score 80%
B
DNS
B
DOMAIN
A
MAIL
B
WEB
B

Resume

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

BIND version is hidden

Dns version is visible for ns2.webicom.si with IP 91.185.202.231 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

Dns version is visible for ns1.webicom.si with IP 91.185.209.27 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

Dns version is visible for ns3.webicom.si with IP 91.185.215.197 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

MX servers accept postmaster@ address

ns2.webicom.si [91.185.202.231] does not accept email to postmaster@webicom.si.

SMTP server type is hidden

ns2.webicom.si with IP [91.185.202.231] displays the type of SMTP, exim founded

220-master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

Content Type Options header is present

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

Banner return server name

ns2.webicom.si with IP [91.185.202.231] does not contain the name of the server.

master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for webicom.si

ns2.webicom.si was detected as host

Possible problem in Dns Tree

We have detected the followings errors on one or more server(s).
Consult Tree for more details.

  • Unknown error
  • Refuse to respond or is in timeout state.

Host informations

Ips
 
Cname
-

Query informations

Server
a.root-servers.net
[ 198.41.0.4 ]
Duration
635 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.dns.si
[ 194.249.4.44 ]
Duration
221 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
f.dns.si
[ 194.146.106.62 ]
Duration
15 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
g.dns.si
[ 194.0.1.20 ]
Duration
20 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
h.dns.si
[ 204.61.216.54 ]
Duration
5 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
i.dns.si
[ 194.0.25.22 ]
Duration
4 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
k.dns.si
[ 185.159.197.11 ]
Duration
22 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
l.dns.si
[ 185.159.198.11 ]
Duration
14 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns1.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP
Name
ns3.webicom.si

ipv4

Locals
Additionals

ipv6

IPs
  • No IP

Query informations

Server
ns1.webicom.si
[ 91.185.202.230 ]
Duration
38 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns2.webicom.si
[ 91.185.202.231 ]
Duration
39 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.webicom.si
[ 91.185.202.237 ]
Duration
44 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Server refused to answer when dns query is performed.

Response

Query informations

Server
ns4.webicom.si
[ 91.185.202.238 ]
Duration
36 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns1.webicom.si
[ 91.185.209.27 ]
Duration
37 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.webicom.si
[ 91.185.202.231 ]
Duration
36 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns3.webicom.si
[ 91.185.215.197 ]
Duration
37 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns4.webicom.si
[ 91.185.202.238 ]
Duration
36 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Name servers

A and AAAA fields

IPv4
91.185.202.231
TTL
1440 (24 minutes )

SOA

From
ns3.webicom.si
Master server
ns1.webicom.si
TTL
86400 (1 day)
Contact
dXiBfYI=@webicom.net
Serial
2021101300
Refresh
86400 (1 day)
Retry
7200 (2 hours)
Expire
3600000 (1 month)
Minimum
86400 (1 day)
Your domain is not protected by DNSSEC DNSSEC Definition

All Dns servers are responding

One or more servers are not responding (timeout, refused, ...)

Every DNS servers should be accessible and accept public query.

0.006s

BIND version is hidden

Dns version is visible for ns2.webicom.si with IP 91.185.202.231 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

Dns version is visible for ns1.webicom.si with IP 91.185.209.27 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

Dns version is visible for ns3.webicom.si with IP 91.185.215.197 : 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.7.

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

0.124s

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 servers return success

Passed

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

0.006s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.006s

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.162s

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.346s

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.118s

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.120s

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

We have no registration information about this domain

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.register.si
Status
Domain registration status is unknown

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 / 61

Scans

ADMINUSLabs
AlienVault
Antiy-AVL
Avira
Baidu-International
BitDefender
Blueliv
C-SIRT
CLEAN MX
CRDF
Comodo Site Inspector
CyberCrime
Dr.Web
ESET
Emsisoft
Fortinet
FraudSense
G-Data
Google Safebrowsing
K7AntiVirus
Malc0de Database
Malekal
Malware Domain Blocklist
MalwareDomainList
MalwarePatrol
Malwarebytes hpHosts
Malwared
OpenPhish
Opera
PalevoTracker
ParetoLogic
Phishtank
Quttera
Rising
SCUMWARE.org
SecureBrain
Spam404
SpyEyeTracker
Sucuri SiteCheck
Tencent
ThreatHive
Trustwave
VX Vault
Web Security Guard
Webutation
Wepawet
Yandex Safebrowsing
ZCloudsec
ZDB Zeus
Zerofox
ZeusTracker
malwares.com URL checker
zvelo
AutoShun
Kaspersky
Netcraft
PhishLabs
Sophos
StopBadware
URLQuery
Websense ThreatSeeker

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.000s

Mail

Mail servers

Name
ns2.webicom.si
IP
91.185.202.231
Banner
220-master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
Name
ns2.webicom.si
IP
91.185.202.231
Banner
220-master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.
Starttls
yes
Dane
no
Mail size
50 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to ns2.webicom.si ...
220-master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
HELO domain.com
250 master.webicom.si Hello ns.tools [195.154.82.101]
EHLO domain.com
250-master.webicom.si Hello ns.tools [195.154.82.101]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-PIPE_CONNECT
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
QUIT
221 master.webicom.si closing connection

Autodiscover not configured

MX servers accept postmaster@ address

ns2.webicom.si [91.185.202.231] does not accept email to postmaster@webicom.si.

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

RFC

40.563s

SMTP server type is hidden

ns2.webicom.si with IP [91.185.202.231] displays the type of SMTP, exim founded

220-master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.

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

Banner return server name

ns2.webicom.si with IP [91.185.202.231] does not contain the name of the server.

master.webicom.si ESMTP Exim 4.94.2 #2 Thu, 14 Oct 2021 06:06:28 +0200 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

Banner must contain the name of the server

0.000s

MX IPs have reverse

Passed

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

Passed

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

RFC

0.000s

EHLO command is accepted

Passed

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

RFC

0.000s

STARTTLS command is accepted

Passed

STARTTLS turns an unencrypted connection into a secure connection. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

0.000s

EXPN command is refused

Passed

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

Passed

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

0.000s

MX servers are not open relay

Passed

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

40.872s

MX servers accept abuse@ address

Passed

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

RFC

40.652s

Banner return 2xx or 4xx code

Passed

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

0.000s

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

Web

Website

Url
https://ns2.webicom.si/
Https
Title
Unknown
Description
Unknown
First paragraph
Unknown
Url
http://ns2.webicom.si/
Title
Unknown
Description
Unknown
Response time
0.072 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Cache-Control: no-cache, no-store, must-revalidate
  • Connection: Upgrade, close
  • Content-Length: 163
  • Content-Type: text/html
  • Date: Thu, 14 Oct 2021 04:06:28 GMT
  • Expires: 0
  • Last-Modified: Wed, 17 Jun 2020 20:01:33 GMT
  • Pragma: no-cache
  • Server: Apache
  • Upgrade: h2,h2c
Url
https://ns2.webicom.si/
Title
Unknown
Description
Unknown
Response time
0.114 second
Server
apache
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • Accept-Ranges: bytes
  • Cache-Control: no-cache, no-store, must-revalidate
  • Connection: Upgrade, close
  • Content-Length: 163
  • Content-Type: text/html
  • Date: Thu, 14 Oct 2021 04:06:28 GMT
  • Expires: 0
  • Last-Modified: Wed, 17 Jun 2020 20:01:33 GMT
  • Pragma: no-cache
  • Server: Apache
  • Upgrade: h2,h2c

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

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

RFC

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

Domain have "A" field

Passed

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

0.000s

HTTP port (80) is open

Passed

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

HTTPS port (443) is open

Passed

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

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