Check DNS, Urls + Redirects, Certificates and Content of your Website



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
21.11.2020 12:25:51


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
play.hayzfight.fr
A
193.70.77.102
Pontcarre/Île-de-France/France (FR) - OVH SAS
Hostname: ip102.ip-193-70-77.eu
yes
1
0

AAAA

yes


www.play.hayzfight.fr

Name Error
yes
1
0
*.hayzfight.fr
A
Fatal: DNS Timeout
yes



AAAA
Fatal: DNS Timeout
yes



CNAME
Fatal: DNS Timeout
yes


*.play.hayzfight.fr
A
Fatal: DNS Timeout
yes



AAAA
Fatal: DNS Timeout
yes



CNAME
Fatal: DNS Timeout
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.12.2020, 00:00:00 +, Signature-Inception: 20.11.2020, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: fr
fr
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 35095, DigestType 2 and Digest I8bKrcmSfumAYfK1LJuNprU/P2SPgUpKhqD6+YQ+LE4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.12.2020, 05:00:00 +, Signature-Inception: 21.11.2020, 04:00:00 +, KeyTag 26116, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 26116 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 35095, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 47293, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 172800 sec, Signature-expiration: 04.01.2021, 16:36:40 +, Signature-Inception: 05.11.2020, 15:36:40 +, KeyTag 35095, Signer-Name: fr



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 35095 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 35095, DigestType 2 and Digest "I8bKrcmSfumAYfK1LJuNprU/P2SPgUpKhqD6+YQ+LE4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: hayzfight.fr
hayzfight.fr
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "re7084cf49n78sriourfg6ergoo5sghr" between the hashed NSEC3-owner "re6r8rnq5nvr4dgbon1561fa7m7psgv1" and the hashed NextOwner "re72l6qp4mb3lju0fkg1mani2regnstp". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner re6r8rnq5nvr4dgbon1561fa7m7psgv1.fr., Algorithm: 8, 2 Labels, original TTL: 5400 sec, Signature-expiration: 11.01.2021, 07:00:06 +, Signature-Inception: 30.10.2020, 13:53:56 +, KeyTag 47293, Signer-Name: fr



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "hse6lveakji7ri5c4e8a03bfg5ha71ao" as Owner. That's the Hash of "fr" with the NextHashedOwnerName "hse7jd05fj7flboni410rmteo9d5etib". So that domain name is the Closest Encloser of "hayzfight.fr". Opt-Out: True.
Bitmap: NS, SOA, TXT, NAPTR, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hse6lveakji7ri5c4e8a03bfg5ha71ao.fr., Algorithm: 8, 2 Labels, original TTL: 5400 sec, Signature-expiration: 04.01.2021, 16:36:40 +, Signature-Inception: 05.11.2020, 15:36:40 +, KeyTag 47293, Signer-Name: fr



0 DNSKEY RR found




Zone: play.hayzfight.fr
play.hayzfight.fr
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.play.hayzfight.fr
www.play.hayzfight.fr
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.play.hayzfight.fr
  ns1.hayzfight.fr

play.hayzfight.fr
  ns1.hayzfight.fr

hayzfight.fr
U  ns1.hayzfight.fr
213.32.120.29
Roubaix/Hauts-de-France/France (FR) - OVH SAS


T 
2001:41d0:8:8ce1::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS


  ns1.inovaperf.fr
178.33.3.191
Roubaix/Hauts-de-France/France (FR) - OVH SAS


  ns2.hayzfight.fr
188.40.163.148
Paris/Île-de-France/France (FR) - Hetzner Online GmbH


  ns2.inovaperf.fr
188.40.163.148
Paris/Île-de-France/France (FR) - Hetzner Online GmbH

fr
  d.nic.fr / dns.fra.nic.fr


  e.ext.nic.fr / ns-ext1a.sidn.nl


  f.ext.nic.fr / s2.amx


  g.ext.nic.fr / 2.fra.pch


  nsmaster.nic.fr


4. SOA-Entries


Domain:fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:fr
Zone-Name:fr
Primary:nsmaster.nic.fr
Mail:hostmaster.nic.fr
Serial:2225984018
Refresh:3600
Retry:1800
Expire:3600000
TTL:5400
num Entries:4


Domain:hayzfight.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:hayzfight.fr
Zone-Name:hayzfight.fr
Primary:ns1.hayzfight.fr
Mail:bgant003.gmail.com
Serial:2020112001
Refresh:180
Retry:3600
Expire:604800
TTL:10800
num Entries:3


Domain:play.hayzfight.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.play.hayzfight.fr
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://play.hayzfight.fr/
193.70.77.102 GZip used - 724 / 1622 - 55.36 %
200

Html is minified: 121.32 %
9.090
H
small visible content (num chars: 170)
HayzFight Développement en cours 00 days 00 hours 00 minutes 00 seconds Clique ici pour rejoindre notre discord ! Map Survie > © 2019 HayzFight. Tous droits réservés
Date: Sat, 21 Nov 2020 11:29:22 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Last-Modified: Tue, 24 Dec 2019 17:30:21 GMT
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Length: 724
Connection: close
Content-Type: text/html

• https://play.hayzfight.fr/
193.70.77.102
-4

0.156
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://play.hayzfight.fr:443/
193.70.77.102 GZip used - 724 / 1622 - 55.36 %
200

Html is minified: 121.32 %
0.110
Q
Visible Content: HayzFight Développement en cours 00 days 00 hours 00 minutes 00 seconds Clique ici pour rejoindre notre discord ! Map Survie > © 2019 HayzFight. Tous droits réservés
Date: Sat, 21 Nov 2020 11:29:23 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Last-Modified: Tue, 24 Dec 2019 17:30:21 GMT
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Length: 724
Connection: close
Content-Type: text/html

• http://play.hayzfight.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
193.70.77.102
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.093
A
Not Found
Visible Content: Not Found The requested URL was not found on this server.
Date: Sat, 21 Nov 2020 11:29:22 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Length: 196
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://193.70.77.102/
193.70.77.102
-4

0.157
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

7. Comments


1. General Results, most used to calculate the result

Aname "play.hayzfight.fr" is subdomain, public suffix is ".fr", top-level-domain is ".fr", top-level-domain-type is "country-code", Country is France, tld-manager is "Association Française pour le Nommage Internet en Coopération (A.F.N.I.C.)", num .fr-domains preloaded: 1776 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: play.hayzfight.fr has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: play.hayzfight.fr has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (3 urls)
http://play.hayzfight.fr/ 193.70.77.102


Url with incomplete Content-Type - header - missing charset
http://play.hayzfight.fr:443/ 193.70.77.102


Url with incomplete Content-Type - header - missing charset
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Qhttp://play.hayzfight.fr:443/ 193.70.77.102
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
XFatal error: Nameserver doesn't support TCP connection: ns1.hayzfight.fr / 213.32.120.29: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte 213.32.120.29:53
XFatal error: Nameserver doesn't support TCP connection: ns1.hayzfight.fr / 2001:41d0:8:8ce1::1: Timeout
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain play.hayzfight.fr, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 20 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 20 Queries complete, 16 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 5.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.hayzfight.fr, ns1.inovaperf.fr, ns2.hayzfight.fr, ns2.inovaperf.fr, 2 Name Servers included in Delegation: ns1.inovaperf.fr, ns2.inovaperf.fr, 2 Name Servers included in 2 Zone definitions: ns1.hayzfight.fr, ns2.hayzfight.fr, 1 Name Servers listed in SOA.Primary: ns1.hayzfight.fr.
AGood: Only one SOA.Primary Name Server found.: ns1.hayzfight.fr.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.hayzfight.fr.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns1.inovaperf.fr (178.33.3.191): Delegation: ns1.inovaperf.fr, ns2.inovaperf.fr, Zone: ns1.hayzfight.fr, ns2.hayzfight.fr. Name Servers defined in Delegation, missing in Zone: ns1.inovaperf.fr, ns2.inovaperf.fr.Name Servers defined in Zone, missing in Delegation: ns1.hayzfight.fr, ns2.hayzfight.fr.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.hayzfight.fr (188.40.163.148): Delegation: ns1.inovaperf.fr, ns2.inovaperf.fr, Zone: ns1.hayzfight.fr, ns2.hayzfight.fr. Name Servers defined in Delegation, missing in Zone: ns1.inovaperf.fr, ns2.inovaperf.fr.Name Servers defined in Zone, missing in Delegation: ns1.hayzfight.fr, ns2.hayzfight.fr.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone.: ns2.inovaperf.fr (188.40.163.148): Delegation: ns1.inovaperf.fr, ns2.inovaperf.fr, Zone: ns1.hayzfight.fr, ns2.hayzfight.fr. Name Servers defined in Delegation, missing in Zone: ns1.inovaperf.fr, ns2.inovaperf.fr.Name Servers defined in Zone, missing in Delegation: ns1.hayzfight.fr, ns2.hayzfight.fr.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 178., 188., 213., 3 different subnets (first two Bytes): 178.33., 188.40., 213.32., 3 different subnets (first three Bytes): 178.33.3., 188.40.163., 213.32.120.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0008:, 1 different subnets (first four blocks): 2001:41d0:0008:8ce1:
Fatal: All Name Server IPv6 addresses from the same subnet.
XNameserver Timeout checking Echo Capitalization: ns1.hayzfight.fr / 213.32.120.29
XNameserver Timeout checking Echo Capitalization: ns1.hayzfight.fr / 2001:41d0:8:8ce1::1
XNameserver Timeout checking EDNS512: ns1.hayzfight.fr / 213.32.120.29
XNameserver Timeout checking EDNS512: ns1.hayzfight.fr / 2001:41d0:8:8ce1::1
Nameserver doesn't pass all EDNS-Checks: f.ext.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (s2.amx). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.hayzfight.fr: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.hayzfight.fr: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.hayzfight.fr / 213.32.120.29: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.hayzfight.fr / 2001:41d0:8:8ce1::1: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.inovaperf.fr / 178.33.3.191: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.inovaperf.fr / 188.40.163.148: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: nsmaster.nic.fr: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
http://play.hayzfight.fr/ 193.70.77.102
200

Warning: HSTS header sent via http has no effect
http://play.hayzfight.fr:443/ 193.70.77.102
200

Warning: HSTS header sent via http has no effect
ADuration: 226170 milliseconds, 226.170 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
5
5

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1936315449
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 08:59:30
2020-12-18 08:59:30
*.hayzfight.fr, hayzfight.fr - 2 entries


1936183082
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 07:40:41
2020-12-18 07:40:41
*.hayzfight.fr, hayzfight.fr - 2 entries


1936159608
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 07:25:44
2020-12-18 07:25:44
*.hayzfight.fr, hayzfight.fr - 2 entries


1936159987
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 07:24:47
2020-12-18 07:24:47
*.hayzfight.fr, hayzfight.fr - 2 entries


1930384271
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-16 16:20:29
2020-12-15 16:20:29
*.hayzfight.fr, hayzfight.fr - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
5
18

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3400151765
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 06:59:30
2020-12-18 07:59:30
*.hayzfight.fr, hayzfight.fr
2 entries


3399903324
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 05:40:41
2020-12-18 06:40:41
*.hayzfight.fr, hayzfight.fr
2 entries


3399858621
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 05:25:44
2020-12-18 06:25:44
*.hayzfight.fr, hayzfight.fr
2 entries


3399855693
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-19 05:24:47
2020-12-18 06:24:47
*.hayzfight.fr, hayzfight.fr
2 entries


3389009729
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-09-16 14:20:29
2020-12-15 15:20:29
*.hayzfight.fr, hayzfight.fr
2 entries


3149672426
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-07-27 10:31:36
2020-10-25 11:31:36
play.hayzfight.fr
1 entries


2976020960
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-06-17 11:55:32
2020-09-15 11:55:32
*.hayzfight.fr, hayzfight.fr
2 entries


2976020014
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-06-17 11:54:25
2020-09-15 11:54:25
*.hayzfight.fr, hayzfight.fr
2 entries


2975991340
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-06-17 11:37:28
2020-09-15 11:37:28
*.hayzfight.fr, hayzfight.fr
2 entries


2917158233
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-05-29 10:17:37
2020-08-27 10:17:37
*.hayzfight.fr, hayzfight.fr
2 entries


2761614619
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-26 01:00:50
2020-07-25 01:00:50
play.hayzfight.fr
1 entries


2722766456
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-15 07:19:07
2020-07-14 07:19:07
*.hayzfight.fr, hayzfight.fr
2 entries


2501064302
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-23 02:05:50
2020-05-23 01:05:50
play.hayzfight.fr
1 entries


2411869948
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-01 19:46:20
2020-05-01 18:46:20
*.hayzfight.fr, hayzfight.fr
2 entries


2425978412
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-01 19:43:05
2020-05-01 18:43:05
*.hayzfight.fr, hayzfight.fr
2 entries


2425974082
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-01 19:41:01
2020-05-01 18:41:01
*.hayzfight.fr, hayzfight.fr
2 entries


2261058589
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-24 15:23:57
2020-03-23 15:23:57
play.hayzfight.fr
1 entries


2066473425
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-03 06:13:15
2020-02-01 06:13:15
*.hayzfight.fr, hayzfight.fr
2 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.hayzfight.fr, ns1.inovaperf.fr, ns2.hayzfight.fr, ns2.inovaperf.fr

QNr.DomainTypeNS used
1
fr
NS
k.root-servers.net (2001:7fd::1)

Answer: d.nic.fr, e.ext.nic.fr, f.ext.nic.fr, g.ext.nic.fr
2
ns1.hayzfight.fr
NS
d.nic.fr (2001:678:c::1)

Answer: ns1.inovaperf.fr, ns2.inovaperf.fr
3
ns1.inovaperf.fr
NS
d.nic.fr (2001:678:c::1)

Answer: hans.ns.cloudflare.com, lana.ns.cloudflare.com
4
ns2.hayzfight.fr
NS
d.nic.fr (2001:678:c::1)

Answer: ns1.inovaperf.fr, ns2.inovaperf.fr
5
ns2.inovaperf.fr
NS
d.nic.fr (2001:678:c::1)

Answer: hans.ns.cloudflare.com, lana.ns.cloudflare.com
6
com
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
7
hans.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
8
lana.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8
9
hans.ns.cloudflare.com: 108.162.193.175, 172.64.33.175, 173.245.59.175
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
10
hans.ns.cloudflare.com: 2606:4700:58::adf5:3baf, 2803:f800:50::6ca2:c1af, 2a06:98c1:50::ac40:21af
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
11
lana.ns.cloudflare.com: 108.162.192.182, 172.64.32.182, 173.245.58.182
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
12
lana.ns.cloudflare.com: 2606:4700:50::adf5:3ab6, 2803:f800:50::6ca2:c0b6, 2a06:98c1:50::ac40:20b6
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
13
ns1.inovaperf.fr: 178.33.3.191
A
hans.ns.cloudflare.com (2a06:98c1:50::ac40:21af)
14
ns1.inovaperf.fr: No AAAA record found
AAAA
hans.ns.cloudflare.com (2a06:98c1:50::ac40:21af)
15
ns1.hayzfight.fr: 213.32.120.29
A
ns1.inovaperf.fr (178.33.3.191)
16
ns1.hayzfight.fr: 2001:41d0:8:8ce1::1
AAAA
ns1.inovaperf.fr (178.33.3.191)
17
ns2.hayzfight.fr: 188.40.163.148
A
ns1.inovaperf.fr (178.33.3.191)
18
ns2.hayzfight.fr: No AAAA record found
AAAA
ns1.inovaperf.fr (178.33.3.191)
19
ns2.inovaperf.fr: 188.40.163.148
A
hans.ns.cloudflare.com (2a06:98c1:50::ac40:21af)
20
ns2.inovaperf.fr: No AAAA record found
AAAA
hans.ns.cloudflare.com (2a06:98c1:50::ac40:21af)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
play.hayzfight.fr
0

no CAA entry found
1
0
hayzfight.fr
0

no CAA entry found
1
0
fr
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
hayzfight.fr
v=spf1 +a +mx +a:web.inovaperf.fr -all
ok
1
0
play.hayzfight.fr

ok
1
0
_acme-challenge.play.hayzfight.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.play.hayzfight.fr.hayzfight.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.play.hayzfight.fr.play.hayzfight.fr

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=3570b426-c66e-48b5-8809-6f3410e0f9a7


Last Result: https://check-your-website.server-daten.de/?q=play.hayzfight.fr - 2020-11-21 12:25:51


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=play.hayzfight.fr" target="_blank">Check this Site: play.hayzfight.fr</a>