Analysis report on IP address: 82.64.75.64
Congratulation
Your domain is really well configured
DNS
Dns servers for 64.82.in-addr.arpa
82.64.75.64 was detected as ipv4
- Name
- ns2.proxad.net
- IPs
- Name
- ns3.proxad.net
- IPs
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
- e.root-servers.net
[ 192.203.230.10 ] - 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
- 141 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
- 35 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
- 177 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
- 235 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
- 257 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
- 13 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
- 8 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Tous les étapes ne retournent pas la même réponse.
Response
Query informations
- Server
- ns3.lacnic.net
[ 200.3.13.14 ] - Duration
- 197 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Tous les étapes ne retournent pas la même réponse.
Response
Query informations
- Server
- ns4.apnic.net
[ 202.12.31.53 ] - Duration
- 150 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Tous les étapes ne retournent pas la même réponse.
Response
Query informations
- Server
- pri.authdns.ripe.net
[ 193.0.9.5 ] - Duration
- 16 ms
- Type
- server_failure
- Headers
- RCODE : 5 AA : 0 TC : 0
Le serveur de nom n'était pas en mesure de traiter la requête de type dns dû à un problème avec ce même serveur
Le serveur refuse de répondre à la requête de type edns.
Query informations
- Server
- rirns.arin.net
[ 199.253.249.53 ] - Duration
- 146 ms
- Type
- authority
- Headers
- RCODE : 0 AA : 0 TC : 0
Response
Query informations
- Server
- ns.ripe.net
[ 193.0.9.6 ] - Duration
- 14 ms
- Type
- server_failure
- Headers
- RCODE : 5 AA : 0 TC : 0
Le serveur de nom n'était pas en mesure de traiter la requête de type dns dû à un problème avec ce même serveur
Le serveur refuse de répondre à la requête de type edns.
Query informations
- Server
- ns2.proxad.net
[ 213.228.58.41 ] - Duration
- 3 ms
- Type
- unknown
- Headers
- RCODE : 0 AA : 1 TC : 0
Query informations
- Server
- ns3.proxad.net
[ 213.228.57.41 ] - Duration
- 8 ms
- Type
- unknown
- Headers
- RCODE : 0 AA : 1 TC : 0
Ip
Informations
- Ip
- 82.64.75.64
- Type
- ipv4
- Reverse
- 82-64-75-64.subs.proxad.net
- ARPA
- 64.75.64.82.in-addr.arpa
- Class C
- 82.64.75.0/24
- ASN
- 12322 Free SAS
- Organisation
- ACP23-RIPE
- Maintainer
- PROXAD-MNT
Reputation
- Blacklists
- Whois server
- whois.ripe.net
% 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.64.0.0 - 82.64.114.255' % Abuse contact for '82.64.0.0 - 82.64.114.255' is O3V2iYd5 [at] proxad.net' inetnum: 82.64.0.0 - 82.64.114.255 netname: FR-PROXAD-ADSL descr: Proxad / Free SAS descr: Dynamic pool (ADSL) descr: NCC#2001087947 (29440) 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: 2003-09-30T13:16:54Z last-modified: 2003-10-28T14:45:43Z source: RIPE % Information related to '82.64.0.0/14AS12322' route: 82.64.0.0/14 descr: ProXad network / Free SA descr: Paris, France origin: AS12322 mnt-by: PROXAD-MNT created: 2003-04-03T09:35:03Z last-modified: 2003-04-03T09:35:03Z 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 servers
- Name
- 82-64-75-64.subs.proxad.net
- IP
- 82.64.75.64
- Banner
SPF
There is no SPF record for this domain
DKIM
Your domain has no DKIM selector found
Do you have one to analyse ?
- Name
- 82-64-75-64.subs.proxad.net
- IP
- 82.64.75.64
- Banner
- Starttls
- yes
- Dane
- no
- Mail size
- 23.01 MB
- Expn
- no
- Vrfy
- no
Smtp simulation
- Connection to 82-64-75-64.subs.proxad.net ...
- 220 smtp.scalaire.com NO UCE ESMTP Qmail on Debian GNU/Linux
- HELO domain.com
- 250 smtp.scalaire.com
- EHLO domain.com
- 250-smtp.scalaire.com
250-PIPELINING
250-SIZE 24123000
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-DSN
250-SMTPUTF8
250 CHUNKING
- QUIT
- 221 2.0.0 Bye
Web
There is no web server. Please test 82-64-75-64.subs.proxad.net.
- Url
- http://82.64.75.64/
- Timeout
- Yes
- Url
- https://82.64.75.64/
- 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)
RFC0.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.
documentation0.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).
documentation0.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