Analysis report on domain: terago.ca favicon

terago.ca
Generated on
13 Nov 2021 03:16
Duration of the analysis
103.5s
Share

Score 73%
C
DNS
B
DOMAIN
A
MAIL
C
WEB
B

Resume

DNS servers IP are in different class C

IPs have the same C class.

SMTP server number

There is only one valid SMTP server.

MX servers accept abuse@ address

terago-ca.mail.protection.outlook.com [104.47.60.36] does not accept email to abuse@terago.ca.

MX servers accept postmaster@ address

terago-ca.mail.protection.outlook.com [104.47.60.36] does not accept email to postmaster@terago.ca.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

Cookies are secure

The HttpOnly flag was not 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

terago-ca.mail.protection.outlook.com with IP [104.47.60.36] does not contain the name of the server.

1

DKIM version exist

Selector 200608: The field "v=" is missing.

k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6QbinBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1gbVEi3GcVwrIQphal1QIDAQAB;

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for terago.ca

terago.ca was detected as domain

Query informations

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

Response

Query informations

Server
any.ca-servers.ca
[ 199.4.144.2 ]
Duration
499 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.ca-servers.ca
[ 185.159.196.2 ]
Duration
21 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
j.ca-servers.ca
[ 198.182.167.1 ]
Duration
12 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
x.ca-servers.ca
[ 199.253.250.68 ]
Duration
41 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns1.terago.cloud
[ 207.251.32.1 ]
Duration
154 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
ns2.terago.cloud
[ 207.251.32.2 ]
Duration
154 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Name servers

Mx Servers

Name
terago-ca.mail.protection.outlook.com
IPs
Priority
5
TTL
60 (1 minute)

A and AAAA fields

IPv4
107.20.213.8
TTL
60 (1 minute )
IPv4
54.88.237.42
TTL
60 (1 minute )

Text Fields

Type
Spf (TXT)
TTL
60 (1 minute)
Name
@
Raw data
v=spf1 mx a:mail.teraint.net ip4:67.226.181.229 ip4:67.226.180.229 ip4:207.54.126.52 ip4:67.226.151.1 ip4:209.97.193.217 ip4:67.226.151.24 ip4:67.226.151.25 ip4:209.97.193.216 ip4:64.46.32.116 include:aspmx.pardot.com include:spf.protection.outlook.com include:amazonses.com include:campaigns.structuredweb.com -all
Mechanisms
mx
IPv4
A
ALL
-all

Includes

aspmx.pardot.com
v=spf1 include:et._spf.pardot.com -all
spf.protection.outlook.com
v=spf1 ip4:40.92.0.0/15 ip4:40.107.0.0/16 ip4:52.100.0.0/14 ip4:104.47.0.0/17 ip6:2a01:111:f400::/48 ip6:2a01:111:f403::/48 include:spfd.protection.outlook.com -all
amazonses.com
v=spf1 ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/19 ip4:54.240.96.0/19 ip4:52.82.172.0/22 -all
campaigns.structuredweb.com
v=spf1 ip4:52.7.190.205/32 ip4:34.233.83.180/32 ip4:52.6.160.60/32 include:sendgrid.net ?all
Type
Dkim
TTL
3600 (1 hour)
Selector
200608
Raw data
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6QbinBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1gbVEi3GcVwrIQphal1QIDAQAB;
Key Type
rsa 1024 bits
Public Key
-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK
/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6Qbi
nBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1g
bVEi3GcVwrIQphal1QIDAQAB
-----END PUBLIC KEY-----
Type
Dmarc
TTL
3600 (1 hour)
Raw data
v=DMARC1; p=none; rua=mailto:rua@terago.ca
Version
DMARC1
Main Domain Procedure
none
Aggregate recipient
  • rua@terago.ca
Type
Txt
TTL
60 (1 minute)
Value
ouh1t1m7jnpgtop7urd7or2787
Type
Txt
TTL
60 (1 minute)
Value
pardot503891=6b04203c20a9e43b6952252554ec46569bd3c05d443f959292465b5dfaf26066
Type
Txt
TTL
60 (1 minute)
Value
8u1/iSXQrjtqy4DRQgIkjhs8+/EGkWzx4PQFDa5IwClCHKmXTmxlfizhzrplxTwtTNrsPUPXEMFg0b2tCJdupg==
Type
Txt
TTL
60 (1 minute)
Value
MS=008DF7AB550417839E44576F497F140A1FD8C163
Type
Txt
TTL
60 (1 minute)
Value
docusign=a469ef43-0dc9-4c74-bcfa-08780d7cb13d
Type
Txt
TTL
60 (1 minute)
Value
google-site-verification=83g2aihiRdN6gdEz8ARETgh2pIuKc_q6QZbvjs1k2uw

SOA

From
ns2.terago.cloud
Master server
ns1.terago.cloud
TTL
120 (2 minutes)
Contact
fYSCg3c=@terago.ca
Serial
2021111001
Refresh
7200 (2 hours)
Retry
3600 (1 hour)
Expire
604800 (1 week)
Minimum
120 (2 minutes)
Your domain is not protected by DNSSEC DNSSEC Definition

DNS servers IP are in different class C

IPs have the same C class.

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

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.

0.162s

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

All servers return success

Passed

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

0.023s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.023s

DNS servers IP are differents

Passed

IPs for DNS servers must be different in order to have high availability.

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

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

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

0.515s

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

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

Domain

Whois

Registrar
-
Owner
3645908 Canada Inc. o/a Terago Canada Inc.
Created at
unknown
Changed at
unknown
Expires at
unknown

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.cira.ca
Created at
unknown
Changed at
unknown
Expires at
unknown
Name servers
Owner
Name
3645908 Canada Inc. o/a Terago Canada Inc.
Organization
Address
55 Commerce Valley Dr W #800
City
Thornhill
Zip code
L3T7V9
Country
CA
Phone
+1.8668372462
Email
fYSCg3c=@terago.ca
Admin
Name
TeraGo IP NOC
Organization
TeraGo Networks Inc
Address
55 Commerce Valley Drive West, Suite 800
City
Thornhill
Zip code
L3T7V9
Country
CA
Phone
+1.8668372462
Email
fYSCg3c=@terago.ca
Tech
Name
TeraGo IP NOC
Organization
TeraGo Networks Inc
Address
55 Commerce Valley Drive West, Suite 800
City
Thornhill
Zip code
L3T7V9
Country
CA
Phone
+1.8668372462
Email
fYSCg3c=@terago.ca

Google Safe Browsing

Status

Web of Trust

Status

Blacklists

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

Virus Total

Detection ratio
0 / 87

Scans

ADMINUSLabs
AICC (MONITORAPP)
AlienVault
Antiy-AVL
Armis
Artists Against 419
Avira
BADWARE.INFO
Baidu-International
Bfore.Ai PreCrime
BitDefender
BlockList
Blueliv
CINS Army
CLEAN MX
CMC Threat Intelligence
CRDF
Certego
Comodo Valkyrie Verdict
CyRadar
CyberCrime
Cyren
DNS8
Dr.Web
ESET
EmergingThreats
Emsisoft
EonScope
Feodo Tracker
Forcepoint ThreatSeeker
Fortinet
FraudScore
G-Data
Google Safebrowsing
GreenSnow
Hoplite Industries
IPsum
K7AntiVirus
Kaspersky
MalBeacon
MalSilo
MalwareDomainList
MalwarePatrol
Malwared
Nucleon
OpenPhish
PREBYTES
Phishing Database
Phishtank
Quick Heal
Quttera
Rising
SCUMWARE.org
Sangfor
Scantitan
SecureBrain
Snort IP sample list
Sophos
Spam404
Spamhaus
StopForumSpam
Sucuri SiteCheck
Tencent
ThreatHive
Threatsourcing
Trustwave
URLhaus
VX Vault
Virusdie External Site Scan
Web Security Guard
Webroot
Yandex Safebrowsing
ZeroCERT
alphaMountain.ai
benkow.cc
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Cyan
Lumu
Netcraft
NotMining
PhishLabs
SafeToOpen
StopBadware

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

DNS servers are same in dns tree and whois

Skipped

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

0.001s

Mail

Mail servers

Name
terago-ca.mail.protection.outlook.com
IP
104.47.60.36
Banner
220 QB1CAN01FT008.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 13 Nov 2021 03:18:03 +0000

SPF

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

Raw data
v=spf1 mx a:mail.teraint.net ip4:67.226.181.229 ip4:67.226.180.229 ip4:207.54.126.52 ip4:67.226.151.1 ip4:209.97.193.217 ip4:67.226.151.24 ip4:67.226.151.25 ip4:209.97.193.216 ip4:64.46.32.116 include:aspmx.pardot.com include:spf.protection.outlook.com include:amazonses.com include:campaigns.structuredweb.com -all

DKIM

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

Have you other DKIM selector to analyse ?


200608._domainkey
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6QbinBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1gbVEi3GcVwrIQphal1QIDAQAB;

DMARC

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

Raw data
v=DMARC1; p=none; rua=mailto:rua@terago.ca
Name
terago-ca.mail.protection.outlook.com
IP
104.47.60.36
Banner
220 QB1CAN01FT008.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 13 Nov 2021 03:18:03 +0000
Starttls
yes
Dane
no
Mail size
150 MB
Expn
no
Vrfy
no

Smtp simulation

Connection to terago-ca.mail.protection.outlook.com ...
220 QB1CAN01FT008.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Sat, 13 Nov 2021 03:18:03 +0000
HELO domain.com
250 QB1CAN01FT008.mail.protection.outlook.com Hello [195.154.82.101]
EHLO domain.com
250-QB1CAN01FT008.mail.protection.outlook.com Hello [195.154.82.101]
250-SIZE 157286400
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

Autodiscover not configured

SMTP server number

There is only one valid SMTP server.

Domain should have at least 2 SMTP servers according to the RFC. Note: You can use a service like altospam to solve this problem. Click on the link below to learn more

altospam

0.000s

MX servers accept abuse@ address

terago-ca.mail.protection.outlook.com [104.47.60.36] does not accept email to abuse@terago.ca.

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

RFC

0.747s

MX servers accept postmaster@ address

terago-ca.mail.protection.outlook.com [104.47.60.36] does not accept email to postmaster@terago.ca.

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

RFC

0.744s

Banner return server name

terago-ca.mail.protection.outlook.com with IP [104.47.60.36] does not contain the name of the server.

1

Banner must contain the name of the server

0.001s

DKIM version exist

Selector 200608: The field "v=" is missing.

k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGoQCNwAQdJBy23MrShs1EuHqK/dtDC33QrTqgWd9CJmtM3CK2ZiTYugkhcxnkEtGbzg+IJqcDRNkZHyoRezTf6QbinBB2dbyANEuwKI5DVRBFowQOj9zvM3IvxAEboMlb0szUjAoML94HOkKuGuCkdZ1gbVEi3GcVwrIQphal1QIDAQAB;

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

RFC DKIM definition

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

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.

0.744s

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

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

IPv4 & IPv6 syntaxes are corrects in SPF

Passed

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

RFC

0.001s

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

PTR must be just before All statement

Passed

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

0.001s

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)

200608

It is strongly recommended to configure DKIM. Note: You could use a service like Mailout to fix this problem. Click on below link to know more

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

MX IPs are differents

Skipped

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

0.000s

MX IPs are in different class C

Skipped

The class C of every IPs should be differents

0.000s

Web

Website

Url
https://terago.ca/
Https
Title
TeraGo
Description
Unknown
First paragraph
“We are pleased to work with TeraGo on their SD-WAN solution to generate deeper visibility and networking analytics for our numerous locations." Raj Perumal - Chief Information Officer. Introducing TeraGo Managed Network Services (MNS). A better way to manage your network and optimize your IT infrastructure. Watch TeraGo, Microsoft and Veeam have a comprehensive discussion on how M365 enables organizations to improve productivity and achieve more, faster while keeping security at the forefront. From Cloud and Connectivity, to Redundancy and Disaster Recovery, we’ve got you covered. Navigate through our solutions based on the business challenges you need to overcome for your organization. ...
Url
http://www.terago.ca/
Redirect to
https://www.terago.ca/
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 206
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Sat, 13 Nov 2021 03:18:04 GMT
  • Location: https://www.terago.ca/
  • Server: Apache
  • Set-Cookie: AWSALB=ohBbGaR/mKXbp6T8kyAeNXFdD2B5yfZQ0eKBjc6enCpah2n+DI3uw7w77QO3lFyHiaiP0OT00ZWjHsNbO8VFY9+uXLA0yZp6zbYb+n/s8Z8ANCKHM5bfkGXZ3AZp; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/, AWSALBCORS=ohBbGaR/mKXbp6T8kyAeNXFdD2B5yfZQ0eKBjc6enCpah2n+DI3uw7w77QO3lFyHiaiP0OT00ZWjHsNbO8VFY9+uXLA0yZp6zbYb+n/s8Z8ANCKHM5bfkGXZ3AZp; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/; SameSite=None
Url
https://www.terago.ca/
Redirect to
http://terago.ca/
Redirect code
301 - moved permanently

Headers

  • Connection: close
  • Content-Length: 225
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Sat, 13 Nov 2021 03:18:04 GMT
  • Location: http://terago.ca/
  • Server: Apache
  • Set-Cookie: AWSALB=Ns0FXYXDkoh6E5WqAfG1eLJvzBqgaxhSCuSqH0Zl8A/3sNEblrYPvy/kNvaGJw+52v5uH3dvekYR5l4uIPkm0RCK3yrd70QfcAXNm4edF78Ev0CdqXI00GNxCQQe; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/, AWSALBCORS=Ns0FXYXDkoh6E5WqAfG1eLJvzBqgaxhSCuSqH0Zl8A/3sNEblrYPvy/kNvaGJw+52v5uH3dvekYR5l4uIPkm0RCK3yrd70QfcAXNm4edF78Ev0CdqXI00GNxCQQe; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/; SameSite=None; Secure
Url
http://terago.ca/
Redirect to
https://terago.ca/
Redirect code
302 - found

Headers

  • Connection: close
  • Content-Length: 202
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Sat, 13 Nov 2021 03:18:04 GMT
  • Location: https://terago.ca/
  • Server: Apache
  • Set-Cookie: AWSALB=Z7SFi0fiw5hm3NLLhgEFiNi4bQSUeidHPCKXqzWTKc8DsK4Zl7jUmiae/uTxAxACPst+dRYSFpy566Gj22fB4ds4hDlc6iqkzwf3MDzj+lvpwG8XWl33oSlLZ4ck; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/, AWSALBCORS=Z7SFi0fiw5hm3NLLhgEFiNi4bQSUeidHPCKXqzWTKc8DsK4Zl7jUmiae/uTxAxACPst+dRYSFpy566Gj22fB4ds4hDlc6iqkzwf3MDzj+lvpwG8XWl33oSlLZ4ck; Expires=Sat, 20 Nov 2021 03:18:04 GMT; Path=/; SameSite=None
Url
https://terago.ca/
Title
TeraGo
Description
Unknown
Response time
1.942 seconds
Server
apache
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Connection: close
  • Content-Type: text/html; charset=UTF-8
  • Date: Sat, 13 Nov 2021 03:18:06 GMT
  • Link: ; rel="https://api.w.org/", ; rel="alternate"; type="application/json", ; rel=shortlink
  • Server: Apache
  • Set-Cookie: AWSALB=rvk2ONum3/Go3ucc6Fk+abVz+E7mie2Fnsk3s8yTVEt/I/1ewxyczLCF5V9tk7IgShW1QxBLrD92uKWGJOMtLBHf8AVRIQ1e+TXkeA3dzqwHLzjvyp2KCyPNsLid; Expires=Sat, 20 Nov 2021 03:18:05 GMT; Path=/, AWSALBCORS=rvk2ONum3/Go3ucc6Fk+abVz+E7mie2Fnsk3s8yTVEt/I/1ewxyczLCF5V9tk7IgShW1QxBLrD92uKWGJOMtLBHf8AVRIQ1e+TXkeA3dzqwHLzjvyp2KCyPNsLid; Expires=Sat, 20 Nov 2021 03:18:05 GMT; Path=/; SameSite=None; Secure
  • Transfer-Encoding: chunked

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

0.000s

Cookies are secure

The HttpOnly flag was not found.

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

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

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

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