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



V

Connect failure - perhaps firewall, 2 invalid Headers

Checked:
23.06.2022 11:58:31


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
data.tellux.fr
A
90.23.22.80
Anceaumeville/Normandy/France (FR) - Orange
Hostname: lfbn-rou-1-392-80.w90-23.abo.wanadoo.fr
yes
1
0

AAAA

yes


www.data.tellux.fr

Name Error
yes
1
0
*.tellux.fr
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.data.tellux.fr
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 20826, Flags 256



Public Key with Algorithm 8, KeyTag 47671, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2022, 00:00:00 +, Signature-Inception: 20.06.2022, 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 13, KeyTag 51508, DigestType 2 and Digest GzOGhk0wzMj0VBuYW/LKMg5PUsV8UzU/bSnJrVilZx8=



1 RRSIG RR to validate DS RR found



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



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 38791, Flags 256



Public Key with Algorithm 13, KeyTag 51508, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 172800 sec, Signature-expiration: 12.08.2022, 07:03:46 +, Signature-Inception: 13.06.2022, 06:03:47 +, KeyTag 51508, Signer-Name: fr



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 51508 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 51508, DigestType 2 and Digest "GzOGhk0wzMj0VBuYW/LKMg5PUsV8UzU/bSnJrVilZx8=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

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



DS with Algorithm 8, KeyTag 13729, DigestType 2 and Digest +PJWyHUghRpdrwvdAI73pSepWiAW4WZ42DwjhAS0QRg=



1 RRSIG RR to validate DS RR found



RRSIG-Owner tellux.fr., Algorithm: 13, 2 Labels, original TTL: 172800 sec, Signature-expiration: 19.08.2022, 10:38:32 +, Signature-Inception: 07.06.2022, 07:25:12 +, KeyTag 38791, Signer-Name: fr



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 52716, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner tellux.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 13729, Signer-Name: tellux.fr



RRSIG-Owner tellux.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



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



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



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

Zone: data.tellux.fr
data.tellux.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 "lfbvaj30p71pusdvan112dl42lesb03n" between the hashed NSEC3-owner "lfbvaj30p71pusdvan112dl42lesb03n" and the hashed NextOwner "m7i0jku9qaj2mn2eec60sp88f0faisvd". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 90.23.22.80
Validated: RRSIG-Owner data.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 60 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "lfbvaj30p71pusdvan112dl42lesb03n" equal the hashed NSEC3-owner "lfbvaj30p71pusdvan112dl42lesb03n" and the hashed NextOwner "m7i0jku9qaj2mn2eec60sp88f0faisvd". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "lfbvaj30p71pusdvan112dl42lesb03n" equal the hashed NSEC3-owner "lfbvaj30p71pusdvan112dl42lesb03n" and the hashed NextOwner "m7i0jku9qaj2mn2eec60sp88f0faisvd". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "lfbvaj30p71pusdvan112dl42lesb03n" equal the hashed NSEC3-owner "lfbvaj30p71pusdvan112dl42lesb03n" and the hashed NextOwner "m7i0jku9qaj2mn2eec60sp88f0faisvd". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.data.tellux.fr) sends a valid NSEC3 RR as result with the hashed owner name "lfbvaj30p71pusdvan112dl42lesb03n" (unhashed: data.tellux.fr). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "hsfs2gtjqvinip21sv1qpli4k2cqphc6" (unhashed: _tcp.data.tellux.fr) with the owner "ffcij5o113k2ip9hvsbkc4spq8980orv" and the NextOwner "lfbvaj30p71pusdvan112dl42lesb03n". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ffcij5o113k2ip9hvsbkc4spq8980orv.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "0n3lntak18987n9a2vr6jegeimhv42nt" (unhashed: *.data.tellux.fr) with the owner "m7i0jku9qaj2mn2eec60sp88f0faisvd" and the NextOwner "ffcij5o113k2ip9hvsbkc4spq8980orv". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.data.tellux.fr) sends a valid NSEC3 RR as result with the owner name "m7i0jku9qaj2mn2eec60sp88f0faisvd" greater the NextOwner-Name "ffcij5o113k2ip9hvsbkc4spq8980orv", so the NSEC3 covers the end of the zone. The hashed query name "a132cml8ffqn5t7hemhhi7oejuvoaitj" comes before the hashed NextOwner, so the zone confirmes the not-existence of that TLSA RR.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner m7i0jku9qaj2mn2eec60sp88f0faisvd.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "lfbvaj30p71pusdvan112dl42lesb03n" equal the hashed NSEC3-owner "lfbvaj30p71pusdvan112dl42lesb03n" and the hashed NextOwner "m7i0jku9qaj2mn2eec60sp88f0faisvd". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



Status: Good. NoData-Proof required and found.

Zone: www.data.tellux.fr
www.data.tellux.fr
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "lfbvaj30p71pusdvan112dl42lesb03n" as Owner. That's the Hash of "data.tellux.fr" with the NextHashedOwnerName "m7i0jku9qaj2mn2eec60sp88f0faisvd". So that domain name is the Closest Encloser of "www.data.tellux.fr". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner lfbvaj30p71pusdvan112dl42lesb03n.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr



The ClosestEncloser says, that "*.data.tellux.fr" with the Hash "0n3lntak18987n9a2vr6jegeimhv42nt" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "m7i0jku9qaj2mn2eec60sp88f0faisvd" and the Next Owner "ffcij5o113k2ip9hvsbkc4spq8980orv", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, MX, TXT, RRSIG Validated: RRSIG-Owner m7i0jku9qaj2mn2eec60sp88f0faisvd.tellux.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 22.07.2022, 05:53:42 +, Signature-Inception: 22.06.2022, 05:53:42 +, KeyTag 52716, Signer-Name: tellux.fr


3. Name Servers

DomainNameserverNS-IP
www.data.tellux.fr
  dns101.ovh.net

data.tellux.fr
  dns101.ovh.net
2001:41d0:1:4a91::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS

tellux.fr
  dns101.ovh.net
2001:41d0:1:4a91::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS


  ns101.ovh.net
2001:41d0:1:1991::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS

fr
  d.nic.fr / dns.ams.nic.fr


  e.ext.nic.fr / ops-nsext01-p.sidn.nl


  f.ext.nic.fr / s2.bnx


  g.ext.nic.fr / 1.ber.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:2231451962
Refresh:3600
Retry:1800
Expire:3600000
TTL:5400
num Entries:4


Domain:tellux.fr
Zone-Name:tellux.fr
Primary:dns101.ovh.net
Mail:tech.ovh.net
Serial:2022062201
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:data.tellux.fr
Zone-Name:tellux.fr
Primary:dns101.ovh.net
Mail:tech.ovh.net
Serial:2022062201
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:1


Domain:www.data.tellux.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://data.tellux.fr/
90.23.22.80 GZip used - 12248 / 18971 - 35.44 %
200

Html is minified: 142.97 %
0.660
H-
small visible content (num chars: 0)
Date: Thu, 23 Jun 2022 09:58:59 GMT
Server: Apache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Security-Policy: default src 'self'; script src 'self'; object src 'self'; frame-ancestors 'self'
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: microphone=(), geolocation=()
Strict-Transport-Security: max age=31536000
Access-Control-Allow-Origin: https://example.com
Content-Length: 12248
Connection: close
Content-Type: text/html; charset=UTF-8

• https://data.tellux.fr/
90.23.22.80
-2

1.127
V
ConnectFailure - Unable to connect to the remote server

• http://data.tellux.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
90.23.22.80
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/12
404

Html is minified: 128.72 %
0.116
A-
Not Found
Visible Content: Object not found! The requested URL was not found on this server. [an error occurred while processing this directive] The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error. If you think this is a server error, please contact the webmaster . Error 404 data.tellux.fr Thu Jun 23 11:59:01 2022 Apache
Date: Thu, 23 Jun 2022 09:59:01 GMT
Server: Apache
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Content-Security-Policy: default src 'self'; script src 'self'; object src 'self'; frame-ancestors 'self'
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: microphone=(), geolocation=()
Strict-Transport-Security: max age=31536000
Access-Control-Allow-Origin: https://example.com
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
Content-Language: en

• https://90.23.22.80/
90.23.22.80
-2

1.133
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "data.tellux.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: 2383 (complete: 175327)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: data.tellux.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: data.tellux.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 - only one version with Http-Status 200
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
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.
Vhttps://data.tellux.fr/ 90.23.22.80
-2

connect failure - perhaps firewall
Vhttps://90.23.22.80/ 90.23.22.80
-2

connect failure - perhaps firewall
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 data.tellux.fr, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 8.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns101.ovh.net, ns101.ovh.net, 2 Name Servers included in Delegation: dns101.ovh.net, ns101.ovh.net, 2 Name Servers included in 1 Zone definitions: dns101.ovh.net, ns101.ovh.net, 1 Name Servers listed in SOA.Primary: dns101.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns101.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns101.ovh.net.
AGood: Consistency 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. Ordered list of name servers: dns101.ovh.net, ns101.ovh.net
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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: ovh.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
A
AInfo: IPv6-Subnet-list: 2 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:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1991:, 2001:41d0:0001:4a91:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: d.nic.fr: 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 (dns.ams.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: dns101.ovh.net: 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: 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.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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://data.tellux.fr/ 90.23.22.80
200
Strict-Transport-Security: max age=31536000
Parse Error - Header can't be parsed
http://data.tellux.fr/ 90.23.22.80
200

Warning: HSTS header sent via http has no effect
ADuration: 49350 milliseconds, 49.350 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=R3, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3867853338
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-21 14:31:38
2022-09-19 14:31:37
data.tellux.fr - 1 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=R3, O=Let's Encrypt, C=US
0 /0 new
1
4

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6982129598
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-21 12:31:38
2022-09-19 12:31:37
data.tellux.fr
1 entries


6268790713
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-03-02 06:23:25
2022-05-31 05:23:24
data.tellux.fr
1 entries


6259634216
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-02-28 16:34:26
2022-05-29 15:34:25
data.tellux.fr
1 entries


6054061351
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-01-26 14:44:15
2022-04-26 13:44:14
data.tellux.fr
1 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: dns101.ovh.net, ns101.ovh.net

QNr.DomainTypeNS used
1
net
NS
j.root-servers.net (2001:503:c27::2:30)

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
2
dns101.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
3
ns101.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130
4
dns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
5
ns13.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
6
ns15.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1
7
dns13.ovh.net: 213.251.188.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
8
dns13.ovh.net: 2001:41d0:1:4a84::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
9
ns13.ovh.net: 213.251.128.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
10
ns13.ovh.net: 2001:41d0:1:1984::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
11
ns15.ovh.net: 213.251.128.134
A
dns10.ovh.net (2001:41d0:1:4a81::1)
12
ns15.ovh.net: 2001:41d0:1:1986::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
13
dns101.ovh.net: 213.251.188.145
A
dns10.ovh.net (2001:41d0:1:4a81::1)
14
dns101.ovh.net: 2001:41d0:1:4a91::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
15
ns101.ovh.net: 213.251.128.145
A
dns10.ovh.net (2001:41d0:1:4a81::1)
16
ns101.ovh.net: 2001:41d0:1:1991::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
data.tellux.fr
0

no CAA entry found
1
0
tellux.fr
0

no CAA entry found
1
0
fr
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tellux.fr
1|www.tellux.fr
ok
1
0
data.tellux.fr

ok
1
0
_acme-challenge.data.tellux.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.data.tellux.fr.tellux.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.data.tellux.fr.data.tellux.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=1a5182b5-34b0-4dc0-81de-827c70b9006d


Last Result: https://check-your-website.server-daten.de/?q=data.tellux.fr - 2022-06-23 11:58:31


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

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