Analysis report on IP address: 82.241.0.11

82.241.0.11
Generated on
26 Mar 2021 16:32
Duration of the analysis
39.9s
Share

Score 100%
A
DNS
-
IP
A
MAIL
A
WEB
A

Congratulation

Your domain is really well configured

DNS

Dns servers for 0.241.82.in-addr.arpa

82.241.0.11 was detected as ipv4

There is no Dns server for this domain

Possible problem in Dns Tree

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

  • Not synchronised
  • Server failure or format error
  • Refuse to respond or is in timeout state.
  • Unknown error

Query informations

Server
j.root-servers.net
[ 192.58.128.30 ]
Duration
9 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

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

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

Query informations

Server
c.in-addr-servers.arpa
[ 196.216.169.10 ]
Duration
184 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.in-addr-servers.arpa
[ 200.10.60.53 ]
Duration
235 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.in-addr-servers.arpa
[ 203.119.86.101 ]
Duration
255 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
f.in-addr-servers.arpa
[ 193.0.9.1 ]
Duration
14 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns3.afrinic.net
[ 204.61.216.100 ]
Duration
18 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

All the step don't return the same response.

Response

Query informations

Server
ns3.lacnic.net
[ 200.3.13.14 ]
Duration
197 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

All the step don't return the same response.

Response

Query informations

Server
ns4.apnic.net
[ 202.12.31.53 ]
Duration
150 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

All the step don't return the same response.

Response

Query informations

Server
pri.authdns.ripe.net
[ 193.0.9.5 ]
Duration
13 ms
Type
server_failure
Headers
RCODE : 5 AA : 0 TC : 0

The name server was unable to process this dns query due to a problem with the name server

Server refused to answer when edns query is performed.

Query informations

Server
rirns.arin.net
[ 199.253.249.53 ]
Duration
147 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns.ripe.net
IPs
  • No IP
Name
ns2.proxad.net
IPs
  • No IP
Name
ns3.proxad.net
IPs
  • No IP

Query informations

Server
ns.ripe.net
[ 193.0.9.6 ]
Duration
13 ms
Type
server_failure
Headers
RCODE : 5 AA : 0 TC : 0

The name server was unable to process this dns query due to a problem with the name server

Server refused to answer when edns query is performed.

Query informations

Server
ns2.proxad.net
[ 213.228.58.41 ]
Duration
7 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns2-rev.proxad.net
IPs
  • No IP
Name
ns3-rev.proxad.net
IPs
  • No IP

Query informations

Server
ns3.proxad.net
[ 213.228.57.41 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Name
ns2-rev.proxad.net
IPs
  • No IP
Name
ns3-rev.proxad.net
IPs
  • No IP
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
82.241.0.11
Type
ipv4
Reverse
laf31-6_migr-82-241-0-11.fbx.proxad.net
ARPA
11.0.241.82.in-addr.arpa
Class C
82.241.0.0/24
ASN
12322 Free SAS
Organisation
ACP23-RIPE
Maintainer
PROXAD-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 '82.241.0.0 - 82.241.3.255'

% Abuse contact for '82.241.0.0 - 82.241.3.255' is O3V2iYd5 [at] proxad.net'

inetnum:        82.241.0.0 - 82.241.3.255
netname:        FR-PROXAD-ADSL
descr:          Proxad / Free SAS
descr:          Static pool (Freebox)
descr:          laf31-6 (toulouse2)
descr:          NCC#2005090519
country:        FR
admin-c:        ACP23-RIPE
tech-c:         TCP8-RIPE
status:         ASSIGNED PA
remarks:        Spam/Abuse requests: mailto:dXaJh3k= [at] proxad.net
mnt-by:         PROXAD-MNT
created:        2005-09-29T13:38:39Z
last-modified:  2005-09-29T13:38:39Z
source:         RIPE

% Information related to '82.224.0.0/11AS12322'

route:          82.224.0.0/11
descr:          ProXad network / Free SAS
descr:          Paris, France
origin:         AS12322
mnt-by:         PROXAD-MNT
created:        2003-11-04T13:26:17Z
last-modified:  2003-11-04T13:26:17Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.99 (HEREFORD)


Blacklists

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

Ip is not blacklisted

Passed

An ip must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Mail

There is no mail server. Please test laf31-6_migr-82-241-0-11.fbx.proxad.net.

Autodiscover analysis not possible on an IP

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

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

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

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

There is no web server. Please test laf31-6_migr-82-241-0-11.fbx.proxad.net.

Url
http://82.241.0.11/
Timeout
Yes
Url
https://82.241.0.11/
Timeout
Yes

HTTP port (80) is open

Skipped

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

Skipped

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

Skipped

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

0.000s

Web application technology is hidden

Skipped

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)

RFC

0.000s

X-XSS-Protection header is present

Skipped

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

Skipped

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

Skipped

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