Analysis report on domain: integrity.hu favicon

integrity.hu
Generated on
23 Mar 2021 00:33
Duration of the analysis
146.7s
Share

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

Resume

DNS servers are synchronized

Name Servers responded with dns1.hu from IP 212.52.165.53 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
212.52.165.53: dns1.hu, dns2.hu, dns3.hu, dns4.hu

Name Servers responded with dns2.hu from IP 194.149.0.68 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
194.149.0.68: dns1.hu, dns2.hu, dns3.hu, dns4.hu

Name Servers responded with dns3.hu from IP 94.199.49.123 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
94.199.49.123: dns1.hu, dns2.hu, dns3.hu, dns4.hu

Same MX are returned

Server 194.149.0.68 returns different MX records from 212.52.165.53:
a.mx.integrity.hu, b.mx.integrity.hu, c.mx.integrity.hu, d.mx.integrity.hu

MX servers are accessibles

Can't connect with SMTP server a.mx.integrity.hu [212.52.166.160].

Can't connect with SMTP server b.mx.integrity.hu [212.52.164.132].

Can't connect with SMTP server c.mx.integrity.hu [94.199.49.122].

Can't connect with SMTP server d.mx.integrity.hu [195.56.45.242].

SMTP server number

There is no valid SMTP server.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

X-XSS-Protection header is present

The X-XSS-Protection header was not found.

Host "www" have "AAAA" field

Host has no "AAAA" (IPv6) field for www.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DNS

Dns servers for integrity.hu

integrity.hu was detected as domain

Query informations

Server
k.root-servers.net
[ 193.0.14.129 ]
Duration
77 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
a.hu
[ 193.239.148.1 ]
Duration
317 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
b.hu
[ 193.239.149.161 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
c.hu
[ 193.6.16.1 ]
Duration
37 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
d.hu
[ 195.70.35.250 ]
Duration
38 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
e.hu
[ 194.0.25.11 ]
Duration
4 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns-com.nic.hu
[ 194.0.1.12 ]
Duration
20 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
ns2.nic.fr
[ 192.93.0.4 ]
Duration
4 ms
Type
authority
Headers
RCODE : 0 AA : 0 TC : 0

Response

Query informations

Server
dns1.hu
[ 212.52.165.53 ]
Duration
303 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
dns2.hu
[ 194.149.0.68 ]
Duration
79 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Query informations

Server
dns3.hu
[ 94.199.49.123 ]
Duration
87 ms
Type
answer
Headers
RCODE : 0 AA : 1 TC : 0

Response

Name servers

Mx Servers

Name
a.mx.integrity.hu
IPs
Priority
10
TTL
3600 (1 hour)
Name
b.mx.integrity.hu
IPs
Priority
10
TTL
3600 (1 hour)
Name
c.mx.integrity.hu
IPs
Priority
10
TTL
3600 (1 hour)
Name
d.mx.integrity.hu
IPs
Priority
10
TTL
3600 (1 hour)

A and AAAA fields

IPv4
212.52.164.124
TTL
3600 (1 hour )
IPv4
213.181.220.125
TTL
3600 (1 hour )

Text Fields

Type
Spf (TXT)
TTL
3600 (1 hour)
Name
@
Raw data
v=spf1 ip4:212.52.164.124 ip4:212.52.165.188 ip4:212.52.165.196 ip4:212.52.165.152 ip4:94.199.49.120 ip4:212.52.165.211 ip4:212.52.165.212/30 ip4:212.52.165.216/29 ip4:212.52.165.224/30 ip4:212.52.165.228/31 mx ~all
Mechanisms
mx
IPv4
ALL
~all
Type
Spf
TTL
3600 (1 hour)
Name
@
Raw data
v=spf1 ip4:212.52.164.124 ip4:212.52.165.188 ip4:212.52.165.196 ip4:212.52.165.152 ip4:94.199.49.120 ip4:212.52.165.211 ip4:212.52.165.212/30 ip4:212.52.165.216/29 ip4:212.52.165.224/30 ip4:212.52.165.228/31 mx ~all
Mechanisms
mx
IPv4
ALL
~all
Type
Dkim
TTL
3600 (1 hour)
Selector
mail
Raw data
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2EYk7AfNqbp+6YCrnRysU15sEimURA6isVpi7hoL363hrKzzhxl434nPEbiPepbwqUDK/k7h6WBOhLniywulap+4+4Sxf2XwJB0Ywvmxn0shnWGNK1qQfWlQrhb8OMrF8wsiOocTDuYq8nuiHoJcuO3zXie9yBcCGh4C/JrZATAnwVhp/lxXiqAAcBoE3HLrZcIVy8yA5HV4PAcNlkIHkJY2Y/WHNhBKaQql6fNJ/M8x5BbLIp0MGOzCAyfMF76wFAmWr0MWCeShkgF2zFJqGgJP2BYkppIJSsUVgVyvHEIMnWQbjneq5Vp/lLmNEUsgAy7nkGgLOTC/B7ToJzhprQIDAQAB
Version
DKIM1
Key Type
rsa 2048 bits
Public Key
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2EYk7AfNqbp+6YCrnRys
U15sEimURA6isVpi7hoL363hrKzzhxl434nPEbiPepbwqUDK/k7h6WBOhLniywul
ap+4+4Sxf2XwJB0Ywvmxn0shnWGNK1qQfWlQrhb8OMrF8wsiOocTDuYq8nuiHoJc
uO3zXie9yBcCGh4C/JrZATAnwVhp/lxXiqAAcBoE3HLrZcIVy8yA5HV4PAcNlkIH
kJY2Y/WHNhBKaQql6fNJ/M8x5BbLIp0MGOzCAyfMF76wFAmWr0MWCeShkgF2zFJq
GgJP2BYkppIJSsUVgVyvHEIMnWQbjneq5Vp/lLmNEUsgAy7nkGgLOTC/B7ToJzhp
rQIDAQAB
-----END PUBLIC KEY-----
Type
Dmarc
TTL
3600 (1 hour)
Raw data
v=DMARC1; p=none; fo=1; ruf=mailto:postmaster@integrity.hu; rua=mailto:postmaster@integrity.hu
Version
DMARC1
Main Domain Procedure
none
Error Report Policy
1
Forensic recipient
  • postmaster@integrity.hu
Aggregate recipient
  • postmaster@integrity.hu
Type
Txt
TTL
3600 (1 hour)
Value
MS=314AC16F5E0AF103A64165213826A18F5EB2682C
Type
Txt
TTL
3600 (1 hour)
Value
MS=ms39687752
Type
Txt
TTL
3600 (1 hour)
Value
google-site-verification=Eflc7lS2lfJeAXRO6SGFc-k_H8FBb_lgUfe9VWH_XDE

SOA

From
dns3.hu
Master server
dns1.hu
TTL
86400 (1 day)
Contact
fIOHiIF1h4h5hg==@dns1.hu
Serial
2021031902
Refresh
86400 (1 day)
Retry
7200 (2 hours)
Expire
3600000 (1 month)
Minimum
3600 (1 hour)

DNSKEY

TTL
3600 (1 hour)
Flag
256 (ZSK)
Protocole
3
Algorithme
8 (RSA/SHA-256)
Key
AwEAAbjO0HMwGxBlSd18MQLoUPXFeMcKy4c+2xezvdfNo8lKzdKTOAPe/hntVCmq6atBRn5evlrFwSaWFCQXohgBID7ZlcbeDyv/apOyoU6gYQD7ng++Iq9Lyi4WmW7aNzkuj0p6WNVNoI/JFadkxlNIBWo5Uadx0A1Szbr/k0jKsxmZ
TTL
3600 (1 hour)
Flag
257 (KSK)
Protocole
3
Algorithme
8 (RSA/SHA-256)
Key
AwEAAc5saVFEo9oauiw2zhTX6S7lF6iRy0hcn1T/L7nSFSMEhQh3SgxRfI0iTLyh7Hsixr+zVP1JtkJ+VlRRkaFWLzLXBiKTgMsEVtsVGOuyTMfx5XoUy5z2Hq24NTekAlDaUZ1qYG/NKxZzHUe1m1LpDjklB7o3ESECndZCczifzIesPT5Kk1RKYBF3I5y9xEXg9hoHsPjReOWtPcF9oPXc/Al5YviT/TVyt65UvRLuyX8jNYlNgEYaDGvdA49X7XPxoZ4NONxo3wdyna6Qu1r45+7UMF5REhYuN8XGcEAgcGMS6KzybQ+TMtQ3HtDGXJeQ97WU0NWteqm1xfl2+BEL0Lk=

RRSIG

Numbers of Labels
2
Created
11 Mar 2021 00:00
Expire
01 Apr 2021 00:00
Algorithme
8 (RSA/SHA-256)
Orig TTL
86400 (1 day)
TTL
3600 (1 hour)
signature Name
integrity.hu
signature
QGEPIu/HV4ggMbsefhTRYFJcTd5J0bmHI/+sG+2zwvdYRyR/R9Q6ZbBfSMOUcQB6rIPRamEncJM+oaQ15S761SD0EYTwDiAMEbMgQ7l2zZV56pt5EgD/i24QkCqKtfVFhkdqTE9U6Wr/qkEWzZWVGeI9ajO4jUnCUhvVLt2wAQE=

DS

Keyttag
59026
Digest Type
2 (SHA-256)
Algorithme
8 (RSA/SHA-256)
TTL
86400 (1 day)
Digest
c807cdbb7accbd3e999fa9216b24a9448a4a85e1ed041509e5d583274af20f79

DNS servers are synchronized

Name Servers responded with dns1.hu from IP 212.52.165.53 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
212.52.165.53: dns1.hu, dns2.hu, dns3.hu, dns4.hu

Name Servers responded with dns2.hu from IP 194.149.0.68 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
194.149.0.68: dns1.hu, dns2.hu, dns3.hu, dns4.hu

Name Servers responded with dns3.hu from IP 94.199.49.123 are not the same with SList.

SList: dns1.hu, dns2.hu, dns3.hu
94.199.49.123: dns1.hu, dns2.hu, dns3.hu, dns4.hu

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

Same MX are returned

Server 194.149.0.68 returns different MX records from 212.52.165.53:
a.mx.integrity.hu, b.mx.integrity.hu, c.mx.integrity.hu, d.mx.integrity.hu

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

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

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

All servers return success

Passed

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

0.003s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.003s

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

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

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

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

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

Domain

Whois

Registrar
-
Owner
-
Created at
27 Jan 1997
Changed at
unknown
Expires at
unknown

Reputation

Google Safe Browsing
Web of trust
Blacklists
Virus Total
Domain
Whois server
whois.nic.hu
Created at
27 Jan 1997
Changed at
unknown
Expires at
unknown
Name servers

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

Scans

ADMINUSLabs
AICC (MONITORAPP)
AegisLab WebGuard
AlienVault
Antiy-AVL
Armis
Artists Against 419
Avira
BADWARE.INFO
Baidu-International
BitDefender
BlockList
Blueliv
CINS Army
CLEAN MX
CMC Threat Intelligence
CRDF
Certego
Cisco Talos IP Blacklist
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
Malware Domain Blocklist
MalwareDomainList
MalwarePatrol
Malwared
Nucleon
OpenPhish
PREBYTES
Phishing Database
Phishtank
Quick Heal
Quttera
Rising
SCUMWARE.org
Sangfor
SecureBrain
Sophos
Spam404
Spamhaus
StopForumSpam
Sucuri SiteCheck
Tencent
ThreatHive
Threatsourcing
Trustwave
URLhaus
VX Vault
Virusdie External Site Scan
Web Security Guard
Yandex Safebrowsing
ZeroCERT
alphaMountain.ai
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Cyan
Lumu
Netcraft
NotMining
PhishLabs
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.000s

Mail

There is no mail server.

Name
a.mx.integrity.hu
IP
212.52.166.160
Accessible
Name
b.mx.integrity.hu
IP
212.52.164.132
Accessible
Name
c.mx.integrity.hu
IP
94.199.49.122
Accessible
Name
d.mx.integrity.hu
IP
195.56.45.242
Accessible

Autodiscover not configured

MX servers are accessibles

Can't connect with SMTP server a.mx.integrity.hu [212.52.166.160].

Can't connect with SMTP server b.mx.integrity.hu [212.52.164.132].

Can't connect with SMTP server c.mx.integrity.hu [94.199.49.122].

Can't connect with SMTP server d.mx.integrity.hu [195.56.45.242].

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

0.000s

SMTP server number

There is no 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

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

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

MX IPs are differents

Passed

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

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

IPv4 & IPv6 syntaxes are corrects in SPF

Passed

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

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

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

mail

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

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

MX IPs are in different class C

Skipped

The class C of every IPs should be differents

0.000s

Web

Website

Url
https://integrity.hu/
Https
Title
INTEGRITY Kft.
Description
szerverhoszting, domain regisztráció
First paragraph
Akciós domain regisztráció: .hu regisztráció díja 2 éves fenntartással 1 480 Ft/db + áfa. Az akció visszavonásig érvényes. .eu regisztráció díja 1 éves fenntartással 480 Ft/db + áfa. Az akció visszavonásig érvényes. (Az akciós 1 éves .eu regisztrációkat minden héten csütörtökön 8.00-16.00 óra között küldjük be a nyilvántartó rendszerébe.)   Aláíró és titkosítókulcsok kezelése, a nyilvános kulcsok biztonságos megosztása– 2021. március 23. kedd, 18.30-19.15, a részvétel díjmentes, de regisztrációhoz kötött.   Akciós domain regisztráció: .hu regisztráció díja 2 éves fenntartással 1 480 Ft/db + áfa. Az akció visszavonásig érvényes. .eu regisztráció díja 1 éves fenntartással 48...
Url
http://www.integrity.hu/
Redirect to
https://integrity.hu/
Redirect code
302 - moved temporarily

Headers

  • Connection: close
  • Content-Length: 154
  • Content-Type: text/html
  • Date: Tue, 23 Mar 2021 00:36:06 GMT
  • Location: https://integrity.hu/
  • Server: nginx
Url
https://integrity.hu/
Title
INTEGRITY Kft.
Description
szerverhoszting, domain regisztráció
Response time
0.292 second
Server
nginx
Powered by
Unknown
Encoding
utf-8
HSTS

Headers

  • Connection: close
  • Content-Type: text/html; charset=UTF-8
  • Date: Tue, 23 Mar 2021 00:36:06 GMT
  • Server: nginx
  • Strict-Transport-Security: max-age=63072000
  • Transfer-Encoding: chunked
  • Vary: Accept-Encoding
  • X-Content-Type-Options: nosniff
  • X-Frame-Options: SAMEORIGIN
Url
https://www.integrity.hu/
Redirect to
https://integrity.hu/
Redirect code
302 - moved temporarily

Headers

  • Connection: close
  • Content-Length: 154
  • Content-Type: text/html
  • Date: Tue, 23 Mar 2021 00:36:09 GMT
  • Location: https://integrity.hu/
  • Server: nginx

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

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

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

Host "www" have "AAAA" field

Host has no "AAAA" (IPv6) field for www.

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

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

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

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.

RFC

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