Analysis report on domain: outlook.com favicon

outlook.com
Generated on
28 Jun 2018 07:20
Duration of the analysis
24.9s
Share

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

Resume

IPv4 & IPv6 syntaxes are corrects in SPF

IPv4 has not the correct syntax.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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 Security Policy header is present

The Content-Security-Policy header was not found.

Banner return server name

outlook-com.olc.protection.outlook.com with IP [104.47.44.33] does not contain the name of the server.

1

outlook-com.olc.protection.outlook.com with IP [104.47.45.33] does not contain the name of the server.

1

DNS

Dns servers for outlook.com

outlook.com was detected as 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
  • Unknown error

Query informations

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

Response

Query informations

Server
a.gtld-servers.net
[ 192.5.6.30 ]
Duration
518 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
b.gtld-servers.net
[ 192.33.14.30 ]
Duration
249 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
c.gtld-servers.net
[ 192.26.92.30 ]
Duration
24 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
d.gtld-servers.net
[ 192.31.80.30 ]
Duration
24 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
e.gtld-servers.net
[ 192.12.94.30 ]
Duration
33 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
f.gtld-servers.net
[ 192.35.51.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
g.gtld-servers.net
[ 192.42.93.30 ]
Duration
32 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
h.gtld-servers.net
[ 192.54.112.30 ]
Duration
26 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
i.gtld-servers.net
[ 192.43.172.30 ]
Duration
26 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
j.gtld-servers.net
[ 192.48.79.30 ]
Duration
26 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
k.gtld-servers.net
[ 192.52.178.30 ]
Duration
128 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
l.gtld-servers.net
[ 192.41.162.30 ]
Duration
127 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
m.gtld-servers.net
[ 192.55.83.30 ]
Duration
129 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
ns1.msft.net
[ 208.84.0.53 ]
Duration
20 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1a.o365filtering.com
[ 157.56.110.11 ]
Duration
95 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns2.msft.net
[ 208.84.2.53 ]
Duration
30 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns2a.o365filtering.com
[ 157.56.116.52 ]
Duration
28 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Tous les étapes ne retournent pas la même réponse.

Response

Query informations

Server
ns3.msft.net
[ 193.221.113.53 ]
Duration
28 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns4.msft.net
[ 208.76.45.53 ]
Duration
29 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns4a.o365filtering.com
[ 157.55.133.11 ]
Duration
89 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Name servers

Mx Servers

A and AAAA fields

IPv4
40.97.128.194
TTL
300 (5 minutes)
IPv4
40.97.116.82
TTL
300 (5 minutes)
IPv4
40.97.161.50
TTL
300 (5 minutes)
IPv4
40.97.164.146
TTL
300 (5 minutes)
IPv4
40.97.153.146
TTL
300 (5 minutes)
IPv4
40.97.156.114
TTL
300 (5 minutes)
IPv4
40.97.160.2
TTL
300 (5 minutes)
IPv4
40.97.148.226
TTL
300 (5 minutes)

Text Fields

Type
Spf (TXT)
TTL
300 (5 minutes)
Name
@
Raw data
v=spf1 include:spf-a.outlook.com include:spf-b.outlook.com ip4:157.55.9.128/25 include:spf.protection.outlook.com include:spf-a.hotmail.com include:_spf-ssg-b.microsoft.com include:_spf-ssg-c.microsoft.com ~all
IPv4
ALL
~all

Includes

spf-a.outlook.com
v=spf1 ip4:157.56.232.0/21 ip4:157.56.240.0/20 ip4:207.46.198.0/25 ip4:207.46.4.128/25 ip4:157.56.24.0/25 ip4:157.55.157.128/25 ip4:157.55.61.0/24 ip4:157.55.49.0/25 ip4:65.55.174.0/25 ip4:65.55.126.0/25 ip4:65.55.113.64/26 ip4:65.55.94.0/25 -all
spf-b.outlook.com
v=spf1 ip4:65.55.78.128/25 ip4:111.221.112.0/21 ip4:207.46.58.128/25 ip4:111.221.69.128/25 ip4:111.221.66.0/25 ip4:111.221.23.128/25 ip4:70.37.151.128/25 ip4:157.56.248.0/21 ip4:213.199.177.0/26 ip4:157.55.225.0/25 ip4:157.55.11.0/25 -all
spf.protection.outlook.com
v=spf1 ip4:207.46.100.0/24 ip4:207.46.163.0/24 ip4:65.55.169.0/24 ip4:157.56.110.0/23 ip4:157.55.234.0/24 ip4:213.199.154.0/24 ip4:213.199.180.128/26 ip4:52.100.0.0/14 include:spfa.protection.outlook.com -all
spf-a.hotmail.com
v=spf1 ip4:157.55.0.192/26 ip4:157.55.1.128/26 ip4:157.55.2.0/25 ip4:65.54.190.0/24 ip4:65.54.51.64/26 ip4:65.54.61.64/26 ip4:65.55.111.0/24 ip4:65.55.116.0/25 ip4:65.55.34.0/24 ip4:65.55.90.0/24 ip4:65.54.241.0/24 ip4:207.46.117.0/24 ~all
_spf-ssg-b.microsoft.com
v=spf1 ip4:207.68.169.173/30 ip4:207.68.176.0/26 ip4:207.46.132.128/27 ip4:207.68.176.96/27 ip4:65.55.238.129/26 ip4:65.55.238.129/26 ip4:207.46.116.128/29 ip4:65.55.178.128/27 ip4:213.199.161.128/27 ip4:65.55.33.64/28 ~all
_spf-ssg-c.microsoft.com
v=spf1 ip4:65.54.121.120/29 ip4:65.55.81.48/28 ip4:65.55.234.192/26 ip4:207.46.200.0/27 ip4:65.55.52.224/27 ip4:94.245.112.10/31 ip4:94.245.112.0/27 ip4:111.221.26.0/27 ip4:207.46.50.192/26 ip4:207.46.50.224 ~all
Type
Dkim
TTL
600 (10 minutes)
Selector
selector1
Raw data
v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvWyktrIL8DO/+UGvMbv7cPd/Xogpbs7pgVw8y9ldO6AAMmg8+ijENl/c7Fb1MfKM7uG3LMwAr0dVVKyM+mbkoX2k5L7lsROQr0Z9gGSpu7xrnZOa58+/pIhd2Xk/DFPpa5+TKbWodbsSZPRN8z0RY5x59jdzSclXlEyN9mEZdmOiKTsOP6A7vQxfSya9jg5N81dfNNvP7HnWejMMsKyIMrXptxOhIBuEYH67JDe98QgX14oHvGM2Uz53if/SW8MF09rYh9sp4ZsaWLIg6T343JzlbtrsGRGCDJ9JPpxRWZimtz+Up/BlKzT6sCCrBihb/Bi3pZiEBB4Ui/vruL5RCQIDAQAB;n=2048,1452627113,1468351913
Version
DKIM1
Key Type
rsa 2048 bits
Public Key
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvWyktrIL8DO/+UGvMbv7
cPd/Xogpbs7pgVw8y9ldO6AAMmg8+ijENl/c7Fb1MfKM7uG3LMwAr0dVVKyM+mbk
oX2k5L7lsROQr0Z9gGSpu7xrnZOa58+/pIhd2Xk/DFPpa5+TKbWodbsSZPRN8z0R
Y5x59jdzSclXlEyN9mEZdmOiKTsOP6A7vQxfSya9jg5N81dfNNvP7HnWejMMsKyI
MrXptxOhIBuEYH67JDe98QgX14oHvGM2Uz53if/SW8MF09rYh9sp4ZsaWLIg6T34
3JzlbtrsGRGCDJ9JPpxRWZimtz+Up/BlKzT6sCCrBihb/Bi3pZiEBB4Ui/vruL5R
CQIDAQAB
-----END PUBLIC KEY-----
Type
Dmarc
TTL
3600 (1 hour)
Raw data
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com; fo=1
Version
DMARC1
Percentage
100
Main Domain Procedure
none
Sub Domain Procedure
quarantine
Error Report Policy
1
Forensic recipient
  • d@ruf.agari.com
Aggregate recipient
  • d@rua.agari.com
Type
Txt
TTL
300 (5 minutes)
Value
google-site-verification=0iLWhIMhXEkeWwWfFU4ursTn-_OvoOjaA0Lr7Pg1sEM
Type
Txt
TTL
300 (5 minutes)
Value
google-site-verification=DC2uC-T8kD33lINhNzfo0bNBrw-vrCXs5BPF5BXY56g

SOA

From
ns4a.o365filtering.com
Master server
sn2mgt0101dc120.prdmgt01.prod.exchangelabs.com
TTL
300 (5 minutes)
Contact
gYeCfIeI@microsoft.com
Serial
2013967644
Refresh
1800 (30 minutes)
Retry
900 (15 minutes)
Expire
2419200 (4 weeks)
Minimum
300 (5 minutes)

Hosts found

Name
www.outlook.com
Cname
outlook.office365.com
TTL
300 (5 minutes)
Name
smtp.outlook.com
Cname
lb.geo.office365.com
TTL
300 (5 minutes)
Name
imap.outlook.com
Cname
lb.geo.office365.com
TTL
300 (5 minutes)
Name
pop.outlook.com
Cname
lb.geo.office365.com
TTL
300 (5 minutes)

BIND version is hidden

Passed

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

4.192s

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 Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.005s

All servers return success

Passed

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

0.002s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.001s

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

DNS servers are synchronized

Passed

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

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

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

3.363s

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

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

Domain

Whois

Registrar
MarkMonitor Inc.
Owner
-
Created at
18 Aug 1994
Changed at
16 Jul 2017
Expires at
17 Aug 2018

Reputation

Google Safe Browsing
Web of trust
94%
Blacklists
Virus Total
Domain
Registrar
Id
292
Name
MarkMonitor Inc.
Phone
-
Email
Url
-

Google Safe Browsing

Status

Web of Trust

Trust Rate
94%
Child Safe Rate
94%
Categories
Good site

Blacklists

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

Virus Total

Detection ratio
0 / 67

Scans

ADMINUSLabs
AegisLab WebGuard
AlienVault
Antiy-AVL
Avira
Baidu-International
BitDefender
Blueliv
C-SIRT
CLEAN MX
Certly
Comodo Site Inspector
CyRadar
CyberCrime
DNS8
Dr.Web
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
FraudScore
FraudSense
G-Data
Google Safebrowsing
K7AntiVirus
Kaspersky
Malc0de Database
Malekal
Malware Domain Blocklist
MalwareDomainList
MalwarePatrol
Malwarebytes hpHosts
Malwared
Nucleon
OpenPhish
Opera
Phishtank
Quttera
Rising
SCUMWARE.org
SecureBrain
Spam404
Sucuri SiteCheck
Tencent
ThreatHive
Trustwave
VX Vault
Virusdie External Site Scan
Web Security Guard
Webutation
Yandex Safebrowsing
ZCloudsec
ZDB Zeus
ZeroCERT
Zerofox
ZeusTracker
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Netcraft
NotMining
PhishLabs
Sophos
StopBadware
URLQuery

DNS servers are same in dns tree and whois

Passed

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

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

Mail

Mail servers

Name
outlook-com.olc.protection.outlook.com
IP
104.47.44.33
Banner
220 SN1NAM04FT049.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000
Name
outlook-com.olc.protection.outlook.com
IP
104.47.45.33
Banner
220 CO1NAM04FT037.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000

SPF

Find more informations about this SPF entry into the DNS> Zone tab

Raw data
v=spf1 include:spf-a.outlook.com include:spf-b.outlook.com ip4:157.55.9.128/25 include:spf.protection.outlook.com include:spf-a.hotmail.com include:_spf-ssg-b.microsoft.com include:_spf-ssg-c.microsoft.com ~all

DKIM

Find more informations about DKIM entries into the DNS> Zone tab

selector1._domainkey
v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvWyktrIL8DO/+UGvMbv7cPd/Xogpbs7pgVw8y9ldO6AAMmg8+ijENl/c7Fb1MfKM7uG3LMwAr0dVVKyM+mbkoX2k5L7lsROQr0Z9gGSpu7xrnZOa58+/pIhd2Xk/DFPpa5+TKbWodbsSZPRN8z0RY5x59jdzSclXlEyN9mEZdmOiKTsOP6A7vQxfSya9jg5N81dfNNvP7HnWejMMsKyIMrXptxOhIBuEYH67JDe98QgX14oHvGM2Uz53if/SW8MF09rYh9sp4ZsaWLIg6T343JzlbtrsGRGCDJ9JPpxRWZimtz+Up/BlKzT6sCCrBihb/Bi3pZiEBB4Ui/vruL5RCQIDAQAB;n=2048,1452627113,1468351913

DMARC

Find more informations about this DMARC entry into the DNS> Zone tab

Raw data
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com; fo=1
Name
outlook-com.olc.protection.outlook.com
IP
104.47.44.33
Banner
220 SN1NAM04FT049.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000
Starttls
yes
Mail size
47 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to outlook-com.olc.protection.outlook.com ...
220 SN1NAM04FT049.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000
HELO nstools.fr
250 SN1NAM04FT049.mail.protection.outlook.com Hello [195.154.82.101]
EHLO nstools.fr
250-SN1NAM04FT049.mail.protection.outlook.com Hello [195.154.82.101]
250-SIZE 49283072
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
QUIT
221 2.0.0 Service closing transmission channel
Name
outlook-com.olc.protection.outlook.com
IP
104.47.45.33
Banner
220 CO1NAM04FT037.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000
Starttls
yes
Mail size
47 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to outlook-com.olc.protection.outlook.com ...
220 CO1NAM04FT037.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Thu, 28 Jun 2018 07:20:44 +0000
HELO domain.com
250 CO1NAM04FT037.mail.protection.outlook.com Hello [195.154.82.101]
EHLO domain.com
250-CO1NAM04FT037.mail.protection.outlook.com Hello [195.154.82.101]
250-SIZE 49283072
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8
QUIT
221 2.0.0 Service closing transmission channel

IPv4 & IPv6 syntaxes are corrects in SPF

IPv4 has not the correct syntax.

IPs must be valid, otherwise the SPF will be useless.

RFC

0.000s

Banner return server name

outlook-com.olc.protection.outlook.com with IP [104.47.44.33] does not contain the name of the server.

1

outlook-com.olc.protection.outlook.com with IP [104.47.45.33] does not contain the name of the server.

1

Banner must contain the name of the server

0.001s

MX servers are accessibles

Passed

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

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.

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.

1.913s

MX servers accept abuse@ address

Passed

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

RFC

1.910s

MX servers accept postmaster@ address

Passed

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

RFC

1.924s

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 records are FQDN

Passed

MX must be a domain, not an IP.

RFC

0.000s

MX records are not CNAME

Passed

According to the RFC 1034 and 2181 CNAME records should not be used with NS and MX

RFC RFC

0.001s

SMTP server number

Passed

Domain should have at least 2 SMTP servers according to the RFC

0.000s

MX IPs are differents

Passed

The IP of the SMTP servers must be different if it is no longer reachable.

0.000s

MX IPs are in different class C

Passed

The class C of every IPs should be differents

0.000s

SPF is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure SPF.

0.000s

SPF record is TXT type

Passed

SPF record is no longer used, SPF must be into TXT record because many servers do not support SPF record. If SPF record exist, it should be the same as TXT

RFC

0.000s

Domain have only 1 SPF record

Passed

To avoid issue with SPF, it is strongly recommended to configure only one.

0.000s

SPF version exists

Passed

According to the RFC, the SPF version must be specified.

RFC

0.000s

SPF version at first position

Passed

SPF has to start with version's tag.

RFC

0.000s

SPF "all" exists

Passed

According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.

RFC

0.000s

SPF "all" at last position

Passed

The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

SPF haven't PTR

Passed

PTR has become obselete in SPF, should not be found in it.

RFC

0.000s

SPF "Redirect" at last position

Passed

The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

SPF records of type TXT & SPF are the same

Passed

SPF record has become obselete, if it is configured then it must be the same as the one present in the TXT record

0.000s

DMARC is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure DMARC.

0.000s

Domain have only 1 DMARC record

Passed

To avoid issue with DMARC, it is strongly recommended to configure only one.

0.000s

DMARC version exist

Passed

According to the RFC 7489 section 6.3, the DMARC version is required.

RFC

0.000s

DMARC version at first position

Passed

According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.

RFC

0.000s

DMARC procedure exists

Passed

According to the RFC 7489 section 6.3, the procedure is required.

RFC

0.000s

DMARC "p" field is valid

Passed

According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "sp" field is valid

Passed

According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "pct" field is valid

Passed

According to the RFC 7489 section 6.3, the percentage's value must be between 0 and 100.

RFC

0.000s

DMARC "adkim" field is valid

Passed

According to the RFC 7489 section 6.3, the adkim tag value must be the letter R or S.

RFC

0.000s

DMARC "aspf" field is valid

Passed

According to the RFC 7489 section 6.3, the aspf tag value must be the letter R or S.

RFC

0.000s

DMARC "rf" field is valid

Passed

According to the RFC 7489 section 6.3, the RF tag's value must be afrf or iodef.

RFC

0.000s

DMARC "ri" field is valid

Passed

According to the RFC 7489 section 6.3, the RI tag's value must be an integer.

RFC

0.000s

DMARC "ruf" field is valid

Passed

According to the RFC 7489 section 6.3, the RUF tag's value must be a valid email.

RFC

0.000s

DMARC "rua" field is valid

Passed

According to the RFC 7489 section 6.3, the RUA tag's value must be a valid email.

RFC

0.000s

DKIM is configured for domain

Configured selector(s)

selector1

It is strongly recommended to configure DKIM.

0.000s

DKIM version exist

Passed

According to the RFC 6376 section 3.6.1, the DKIM version is required.

RFC

0.000s

DKIM Service Type is valid

Passed

This Tag is optionnal but when use, it must be equal to "*" or "email".

RFC

0.000s

DKIM Testing flag is valid

Passed

This Tag is optionnal but when use, it must be equal to "s", "y" or "y:s".

RFC

0.000s

DKIM public key is valid

Passed

According to the RFC 6376 section 3.6.1, the public key is required and must be valid.

RFC

0.000s

DKIM public key is secure

Passed

The size of the public key must be bigger than 1024 bits.

0.000s

Web

Website

Url
https://outlook.live.com/owa/
Https
Title
Outlook.com - Microsoft free personal email
Description
Unknown
First paragraph
Unknown
Url
http://www.outlook.com/
Redirect to
http://outlook.live.com/
Redirect code
301 - moved permanently

Headers

  • Cache-Control: no-cache
  • Connection: close
  • Content-Length: 0
  • Date: Thu, 28 Jun 2018 07:20:45 GMT
  • Location: http://outlook.live.com/
  • Pragma: no-cache
  • Server: Microsoft-IIS/10.0
  • Strict-Transport-Security: max-age=31536000
  • X-FEServer: PR0P264CA0035, PR0P264CA0035
  • X-Powered-By: ASP.NET
  • X-RequestId: bb1e4adf-4513-4666-b475-68ba2347950e
  • request-id: 75d5768c-403c-4444-81ec-bcdddf916804
Url
http://outlook.live.com/
Redirect to
https://outlook.live.com/
Redirect code
301 - moved permanently

Headers

  • Connection: close
  • Content-Length: 0
  • Date: Thu, 28 Jun 2018 07:20:45 GMT
  • Location: https://outlook.live.com/
  • Server: Microsoft-IIS/10.0
  • X-MSEdge-Ref: Ref A: 7A06A4A5FF8448C4ADBB812E36115E1B Ref B: PAR02EDGE0211 Ref C: 2018-06-28T07:20:45Z
Url
https://outlook.live.com/
Redirect to
https://outlook.live.com/owa/
Redirect code
302 - moved temporarily

Headers

  • Cache-Control: no-cache
  • Connection: close
  • Content-Length: 0
  • Date: Thu, 28 Jun 2018 07:20:45 GMT
  • Location: https://outlook.live.com/owa/
  • Pragma: no-cache
  • Strict-Transport-Security: max-age=31536000
  • X-FEServer: PR0P264CA0022, PR0P264CA0022
  • X-MSEdge-Ref: Ref A: B072042EE5644CDBBE706495F7E1A227 Ref B: PAR02EDGE0311 Ref C: 2018-06-28T07:20:45Z
  • X-Powered-By: ASP.NET
  • X-RequestId: f5faf90c-2aa6-4713-a1b9-569e21e5d270
  • request-id: 84f7026e-7eb1-4114-9d5e-5a76b529a95e
Url
https://outlook.live.com/owa/
Title
Outlook.com - Microsoft free personal email
Description
Unknown
Response time
0.031 second
Server
Unknown
Powered by
asp
Encoding
utf-8
HSTS

Headers

  • Cache-Control: private
  • Connection: close
  • Content-Length: 3640
  • Content-Type: text/html; charset=utf-8
  • Date: Thu, 28 Jun 2018 07:20:45 GMT
  • Set-Cookie: ClientId=6B7BA19C7793416B8CCC0F93251653F6; expires=Fri, 28-Jun-2019 07:20:45 GMT; path=/; secure, ClientId=6B7BA19C7793416B8CCC0F93251653F6; expires=Fri, 28-Jun-2019 07:20:45 GMT; path=/; secure, HostSwitchPrg=; expires=Tue, 28-Jun-1988 07:20:45 GMT; path=/; secure, OptInPrg=; expires=Tue, 28-Jun-1988 07:20:45 GMT; path=/; secure, logonLatency=LGN01=636657672459674398; domain=live.com; path=/; secure; HttpOnly, O365Consumer=; expires=Tue, 28-Jun-1988 07:20:45 GMT; path=/; secure
  • Strict-Transport-Security: max-age=31536000; includeSubDomains
  • X-BEServer: PR2P264MB0094
  • X-BackEnd-Begin: 2018-06-28T07:20:45.966
  • X-BackEnd-End: 2018-06-28T07:20:45.970
  • X-BackEndHttpStatus: 200
  • X-CalculatedBETarget: PR2P264MB0094.FRAP264.PROD.OUTLOOK.COM
  • X-Content-Type-Options: nosniff
  • X-DiagInfo: PR2P264MB0094
  • X-FEServer: PR0P264CA0003
  • X-FRAME-OPTIONS: SAMEORIGIN
  • X-MSEdge-Ref: Ref A: 9E63158B8C2143F0840E0D4CA0A08918 Ref B: PAR02EDGE0215 Ref C: 2018-06-28T07:20:46Z
  • X-Powered-By: ASP.NET
  • X-RUM-Validated: 1
  • X-UA-Compatible: IE=EmulateIE7
  • request-id: 7106e694-a857-411f-819a-2f10851977be
Url
https://www.outlook.com/
Redirect to
https://outlook.live.com/
Redirect code
301 - moved permanently

Headers

  • Cache-Control: no-cache
  • Connection: close
  • Content-Length: 0
  • Date: Thu, 28 Jun 2018 07:20:45 GMT
  • Location: https://outlook.live.com/
  • Pragma: no-cache
  • Server: Microsoft-IIS/10.0
  • Strict-Transport-Security: max-age=31536000
  • X-FEServer: PR0P264CA0040, PR0P264CA0040
  • X-Powered-By: ASP.NET
  • X-RequestId: e05c4daf-f8dd-410d-b066-d06e00c344cf
  • request-id: d28233e9-6b96-4367-a09d-8054d1b4fc18

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

0.000s

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

Host "www" have "A" field

Passed

WWW host is not required for a website, but it's better to have one.

0.000s

Host "www" have "AAAA" field

Passed

If you configure a WWW host for your website, it is recommended to have an IPv6.

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

Passed

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

Content Type Options header is present

Passed

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