STARTTLS command is accepted
ns3.uk.akauk.net [85.91.32.83] does not accept TLS.
Analysis report on IP address: 85.91.32.83
Resume
SMTP server type is hidden
ns3.uk.akauk.net with IP [85.91.32.83] displays the type of SMTP, sendmail founded
220 ns3.watford.akauk.net ESMTP Sendmail 8.14.4/8.14.4; Thu, 8 Apr 2021 07:49:02 +0100
Web server version is hidden
Version 2.2.15 has been found.
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
ns3.uk.akauk.net with IP [85.91.32.83] does not contain the name of the server.
ns3.watford.akauk.net ESMTP Sendmail 8.14.4/8.14.4; Thu, 8 Apr 2021 07:49:02 +0100
Content Security Policy header is present
The Content-Security-Policy header was not found.
DNS
Dns servers for 32.91.85.in-addr.arpa
85.91.32.83 was detected as ipv4
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Possible problem in Dns Tree
We have detected the following error on one or more server(s).
Consult Tree for more details.
- The answer is CNAME, A or not an authority
Query informations
- Server
- j.root-servers.net
[ 192.58.128.30 ] - Duration
- 9 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- a.in-addr-servers.arpa
- IPs
- Name
- b.in-addr-servers.arpa
- IPs
- Name
- c.in-addr-servers.arpa
- IPs
- Name
- d.in-addr-servers.arpa
- IPs
- Name
- e.in-addr-servers.arpa
- IPs
- Name
- f.in-addr-servers.arpa
- IPs
Query informations
- Server
- a.in-addr-servers.arpa
[ 199.180.182.53 ] - Duration
- 142 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- b.in-addr-servers.arpa
[ 199.253.183.183 ] - Duration
- 36 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- c.in-addr-servers.arpa
[ 196.216.169.10 ] - Duration
- 173 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- d.in-addr-servers.arpa
[ 200.10.60.53 ] - Duration
- 241 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- e.in-addr-servers.arpa
[ 203.119.86.101 ] - Duration
- 259 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- f.in-addr-servers.arpa
[ 193.0.9.1 ] - Duration
- 22 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns3.afrinic.net
- IPs
- Name
- ns3.lacnic.net
- IPs
- Name
- ns4.apnic.net
- IPs
- Name
- pri.authdns.ripe.net
- IPs
- Name
- rirns.arin.net
- IPs
Query informations
- Server
- ns3.afrinic.net
[ 204.61.216.100 ] - Duration
- 831 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Query informations
- Server
- ns3.lacnic.net
[ 200.3.13.14 ] - Duration
- 196 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Query informations
- Server
- ns4.apnic.net
[ 202.12.31.53 ] - Duration
- 148 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Query informations
- Server
- pri.authdns.ripe.net
[ 193.0.9.5 ] - Duration
- 14 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Query informations
- Server
- rirns.arin.net
[ 199.253.249.53 ] - Duration
- 139 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
- Name
- ns1.moose.co.uk
- IPs
- Name
- ns4.moose.co.uk
- IPs
Query informations
- Server
- ns1.moose.co.uk
[ 85.91.32.11 ] - Duration
- 21 ms
- Type
- unknown
- Headers
- RCODE : 0 AA : 1 TC : 0
There is an answer but it is a CNAME type.
Query informations
- Server
- ns4.moose.co.uk
[ 62.232.125.45 ] - Duration
- 22 ms
- Type
- unknown
- Headers
- RCODE : 0 AA : 1 TC : 0
There is an answer but it is a CNAME type.
DNSSEC analysis not possible on an IP
Ip
Informations
- Ip
- 85.91.32.83
- Type
- ipv4
- Reverse
- ns3.uk.akauk.net
- ARPA
- 83.32.91.85.in-addr.arpa
- Class C
- 85.91.32.0/24
- ASN
- 4589 EASYNET Easynet Global Services
- Organisation
- RJW2-RIPE
- Maintainer
- MOOSE-MNT
Reputation
- Blacklists
Ip
- Whois server
- whois.ripe.net
Raw data
% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '85.91.32.0 - 85.91.33.255' % Abuse contact for '85.91.32.0 - 85.91.33.255' is O4B9hnV4gX2C [at] moose.co.uk' inetnum: 85.91.32.0 - 85.91.33.255 netname: MOOSE-W descr: Moose Internet Services Ltd. descr: Network Operations Centre country: GB admin-c: RJW2-RIPE tech-c: RJW2-RIPE status: LIR-PARTITIONED PA mnt-by: MOOSE-MNT mnt-lower: MOOSE-MNT mnt-routes: EASYNET-UK-MNT created: 2006-04-11T08:41:52Z last-modified: 2006-04-13T11:18:02Z source: RIPE % Information related to '85.91.32.0/23AS4589' route: 85.91.32.0/23 descr: Moose Internet Services Ltd descr: Easynet UK origin: AS4589 mnt-by: EASYNET-UK-MNT created: 2006-04-18T13:39:24Z last-modified: 2006-04-18T13:39:24Z source: RIPE % This query was served by the RIPE Database Query Service version 1.99 (BLAARKOP)
Blacklists
- RFC Ignorant
- Rbl Jp
- RblDns
- Sorbs
- Spam Eating Monkey
- SpamHaus
- SuRbl
- Support Intelligence
- Swinog
- UriBl
Ip is not blacklisted
SpamHaus has blacklisted your domain/IP.
An ip must not be blacklisted or it will be penalized for referencing and deliverability of emails.
0.001s
Mail servers
- Name
- ns3.uk.akauk.net
- IP
- 85.91.32.83
- Banner
- Name
- ns3.uk.akauk.net
- IP
- 85.91.32.83
- Banner
- Starttls
- no
- Dane
- no
- Mail size
- 1 Byte
- Expn
- no
- Vrfy
- no
Smtp simulation
- Connection to ns3.uk.akauk.net ...
- 220 ns3.watford.akauk.net ESMTP Sendmail 8.14.4/8.14.4; Thu, 8 Apr 2021 07:49:02 +0100
- HELO domain.com
- 250 ns3.watford.akauk.net Hello ns.tools [195.154.82.101], pleased to meet you
- EHLO domain.com
- 250-ns3.watford.akauk.net Hello ns.tools [195.154.82.101], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-DELIVERBY
250 HELP
- QUIT
- 221 2.0.0 ns3.watford.akauk.net closing connection
Autodiscover analysis not possible on an IP
STARTTLS command is accepted
ns3.uk.akauk.net [85.91.32.83] does not accept TLS.
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
altospam StartTLS definition0.000s
SMTP server type is hidden
ns3.uk.akauk.net with IP [85.91.32.83] displays the type of SMTP, sendmail founded
220 ns3.watford.akauk.net ESMTP Sendmail 8.14.4/8.14.4; Thu, 8 Apr 2021 07:49:02 +0100
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
ns3.uk.akauk.net with IP [85.91.32.83] does not contain the name of the server.
ns3.watford.akauk.net ESMTP Sendmail 8.14.4/8.14.4; Thu, 8 Apr 2021 07:49:02 +0100
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.
documentation0.000s
HELO command is accepted
Passed
EHLO command is accepted
Passed
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.
2.520s
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
MX servers accept abuse@ address
Skipped
MX servers accept postmaster@ address
Skipped
According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.
RFC0.000s
Web
Website
- Url
- https://85.91.32.83/
- Https
- Title
- Apache HTTP Server Test Page powered by CentOS
- Description
- Unknown
- First paragraph
This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page it means that the Apache HTTP server installed at this site is working properly. The fact that you are seeing this page indicates that the website you just visited is either experiencing problems or is undergoing routine maintenance. If you would like to let the administrators of this website know that you've seen this page instead of the page you expected, you should send them e-mail. In general, mail sent to the name "webmaster" and directed to the website's domain should reach the appropriate person. For example, if you experienced problems while visiting www....
- Url
- http://85.91.32.83/
- Title
- Apache HTTP Server Test Page powered by CentOS
- Description
- Unknown
- Response time
- 0.047 second
- Server
- apache (version 2.2.15)
- Powered by
- Unknown
- Encoding
- utf-8
- HSTS
Headers
- Accept-Ranges: bytes
- Connection: close
- Content-Length: 4961
- Content-Type: text/html; charset=UTF-8
- Date: Thu, 08 Apr 2021 06:49:04 GMT
- Server: Apache/2.2.15 (CentOS)
- Url
- https://85.91.32.83/
- Title
- Apache HTTP Server Test Page powered by CentOS
- Description
- Unknown
- Response time
- 0.099 second
- Server
- apache (version 2.2.15)
- Powered by
- Unknown
- Encoding
- utf-8
- HSTS
Headers
- Accept-Ranges: bytes
- Connection: close
- Content-Length: 4961
- Content-Type: text/html; charset=UTF-8
- Date: Thu, 08 Apr 2021 06:49:05 GMT
- Server: Apache/2.2.15 (CentOS)
Web server version is hidden
Version 2.2.15 has been found.
To avoid giving details to malicious people, the version of the server should not be visible.
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.
documentation0.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.
RFC0.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).
documentation0.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 application technology is hidden
Passed
To avoid giving details to malicious people, the technology that supports the application should not be visible.
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)
RFC0.000s