Analysis report on IP address: 193.253.218.21

193.253.218.21 has no website

Generated on
22 Jul 2021 07:35
Duration of the analysis
19.0s
Share

Score 79%
B
DNS
-
IP
A
MAIL
B
WEB
B

Resume

EHLO command is accepted

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr [193.253.218.21] does not accept EHLO.

503 Bad sequence of commands

STARTTLS command is accepted

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr [193.253.218.21] does not accept TLS.

Web application technology is hidden

Server is powered by: ASP.NET

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

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr with IP [193.253.218.21] does not contain the name of the server.

1

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for 218.253.193.in-addr.arpa

193.253.218.21 was detected as ipv4

Query informations

Server
d.root-servers.net
[ 199.7.91.13 ]
Duration
14 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.in-addr-servers.arpa
[ 199.180.182.53 ]
Duration
290 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
187 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

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

Response

Query informations

Server
pri.authdns.ripe.net
[ 193.0.9.5 ]
Duration
16 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

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

Response

Query informations

Server
ns6.oleane.net
[ 194.2.0.6 ]
Duration
19 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns7.oleane.net
[ 194.2.0.7 ]
Duration
4 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns.wanadoo.fr
[ 80.10.200.224 ]
Duration
9 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0

Query informations

Server
ns2.wanadoo.fr
[ 80.10.203.224 ]
Duration
3 ms
Type
unknown
Headers
RCODE : 0 AA : 1 TC : 0
DNSSEC analysis not possible on an IP

Ip

Informations

Ip
193.253.218.21
Type
ipv4
Reverse
lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr
ARPA
21.218.253.193.in-addr.arpa
Class C
193.253.218.0/24
ASN
3215 Orange
Organisation
WITR1-RIPE
Maintainer
FT-BRX

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 '193.253.218.0 - 193.253.218.255'

% Abuse contact for '193.253.218.0 - 193.253.218.255' is O3t5h4h9g4J9hEJ6iA== [at] orange.com'

inetnum:        193.253.218.0 - 193.253.218.255
netname:        IP2000-ADSL-BAS
descr:          LNPUT658 Puteaux Bloc 2
country:        FR
admin-c:        WITR1-RIPE
tech-c:         WITR1-RIPE
status:         ASSIGNED PA
remarks:        for hacking, spamming or security problems send mail to
remarks:        dXaJh3k= [at] orange.fr
mnt-by:         FT-BRX
created:        2008-05-28T08:58:44Z
last-modified:  2017-05-19T09:55:10Z
source:         RIPE

% Information related to '193.253.192.0/18AS3215'

route:          193.253.192.0/18
descr:          France Telecom
origin:         AS3215
mnt-by:         FT-BRX
created:        2012-11-21T16:26:34Z
last-modified:  2012-11-21T16:26:34Z
source:         RIPE

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


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

Mail

Mail servers

Name
lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr
IP
193.253.218.21
Banner
220 DGM-SRV-EXC.dgm.local ESMTP Service ready
Name
lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr
IP
193.253.218.21
Banner
220 DGM-SRV-EXC.dgm.local ESMTP Service ready
Starttls
no
Dane
no
Mail size
0 Bytes
Expn
no
Vrfy
no

Smtp simulation

Connection to lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr ...
220 DGM-SRV-EXC.dgm.local ESMTP Service ready
HELO nstools.fr
250 Requested mail action okay, completed
EHLO nstools.fr
503 Bad sequence of commands
QUIT
221 Service closing transmission channel
Autodiscover analysis not possible on an IP

EHLO command is accepted

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr [193.253.218.21] does not accept EHLO.

503 Bad sequence of commands

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

RFC

0.000s

STARTTLS command is accepted

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr [193.253.218.21] 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 definition

0.000s

Banner return server name

lputeaux-658-1-79-21.w193-253.abo.wanadoo.fr with IP [193.253.218.21] does not contain the name of the server.

1

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

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.

5.113s

Banner return 2xx or 4xx code

Passed

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

0.000s

SMTP server type is hidden

Passed

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

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

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

Web

Website

Url
https://193.253.218.21/owa/auth/logon.aspx?url=https%3a%2f%2f193.253.218.21%2fowa%2f&reason=0
Https
Title
Outlook
Description
Unknown
First paragraph
Unknown
Url
http://193.253.218.21/
Title
WEB SERVICE
Description
Unknown
Response time
0.29 second
Server
Unknown
Powered by
Unknown
Encoding
Unknown
HSTS

Headers

  • CONNECTION: close
  • CONTENT-LENGTH: 14092
  • CONTENT-TYPE: text/html
  • Date: Thu, 29 Jul 2021 12:41:19 GMT
  • Etag: "1488890319:370c"
  • Last-Modified: Tue, 07 Mar 2017 12:38:39 GMT
  • P3P: CP=CAO PSA OUR
Url
https://193.253.218.21/
Redirect to
https://193.253.218.21/owa/
Redirect code
302 - moved temporarily

Headers

  • Cache-Control: no-cache
  • Connection: close
  • Content-Length: 0
  • Date: Thu, 29 Jul 2021 11:41:20 GMT
  • Location: https://193.253.218.21/owa/
  • Pragma: no-cache
  • Server: Microsoft-IIS/8.5
  • X-FEServer: DGM-SRV-EXC
  • X-RequestId: 8fdf80cd-465b-4410-8aa6-88fb12d0a9c1
Url
https://193.253.218.21/owa/
Redirect to
https://193.253.218.21/owa/auth/logon.aspx?url=https%3a%2f%2f193.253.218.21%2fowa%2f&reason=0
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 214
  • Content-Type: text/html; charset=utf-8
  • Date: Thu, 29 Jul 2021 11:41:20 GMT
  • Location: https://193.253.218.21/owa/auth/logon.aspx?url=https%3a%2f%2f193.253.218.21%2fowa%2f&reason=0
  • Server: Microsoft-IIS/8.5
  • X-FEServer: DGM-SRV-EXC
  • X-Powered-By: ASP.NET
  • request-id: 2cc0f71e-8f76-4cc7-9818-1f0bda7b808d
Url
https://193.253.218.21/owa/auth/logon.aspx?url=https%3a%2f%2f193.253.218.21%2fowa%2f&reason=0
Title
Outlook
Description
Unknown
Response time
1.199 seconds
Server
microsoft
Powered by
asp
Encoding
utf-8
HSTS

Headers

  • Cache-Control: no-cache, no-store
  • Connection: close
  • Content-Length: 58721
  • Content-Type: text/html; charset=utf-8
  • Date: Thu, 29 Jul 2021 11:41:20 GMT
  • Expires: -1
  • Pragma: no-cache
  • Server: Microsoft-IIS/8.5
  • X-AspNet-Version: 4.0.30319
  • X-Frame-Options: SAMEORIGIN
  • X-Powered-By: ASP.NET
  • request-id: 27c7c93c-b37c-481b-af51-18a4848e45b5

Web application technology is hidden

Server is powered by: ASP.NET

To avoid giving details to malicious people, the technology that supports the application 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.

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

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

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