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




T

Timeout

Checked:
20.11.2023 22:29:59


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
api.iotago.fr
A
82.65.66.86
Paris/Île-de-France/France (FR) - Proxad / Free SAS
Hostname: 82-65-66-86.subs.proxad.net
yes
1
0

AAAA

yes


www.api.iotago.fr

Name Error
yes
1
0
*.iotago.fr
A
188.165.53.185
yes



AAAA

yes



CNAME

yes


*.api.iotago.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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 46780, 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.2023, 00:00:00 +, Signature-Inception: 20.11.2023, 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 29133, DigestType 2 and Digest EwPo2o+2DbUA1b6h7l3JorzJPf4vxD00ZXZlj+zPV0k=



1 RRSIG RR to validate DS RR found



RRSIG-Owner fr., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.12.2023, 17:00:00 +, Signature-Inception: 20.11.2023, 16:00:00 +, KeyTag 46780, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 60747, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner fr., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 19.01.2024, 14:30:45 +, Signature-Inception: 20.11.2023, 14:26:31 +, KeyTag 29133, Signer-Name: fr



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



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

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



DS with Algorithm 8, KeyTag 8626, DigestType 2 and Digest AgvuVW6D9DHHGrvheqoKoOBB562rIrBDCxeDkfzP+yM=



1 RRSIG RR to validate DS RR found



RRSIG-Owner iotago.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.01.2024, 05:44:49 +, Signature-Inception: 14.11.2023, 05:12:12 +, KeyTag 60747, Signer-Name: fr



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 393, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner iotago.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



RRSIG-Owner iotago.fr., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 8626, Signer-Name: iotago.fr



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



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



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

Zone: api.iotago.fr
api.iotago.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 "6eh94m38r3q52rjgehrm1qbvt47d4od3" between the hashed NSEC3-owner "6eh94m38r3q52rjgehrm1qbvt47d4od3" and the hashed NextOwner "9mbsmfv1g1m6rc2mned7760ret9l7b68". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 82.65.66.86
Validated: RRSIG-Owner api.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "6eh94m38r3q52rjgehrm1qbvt47d4od3" equal the hashed NSEC3-owner "6eh94m38r3q52rjgehrm1qbvt47d4od3" and the hashed NextOwner "9mbsmfv1g1m6rc2mned7760ret9l7b68". 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 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "6eh94m38r3q52rjgehrm1qbvt47d4od3" equal the hashed NSEC3-owner "6eh94m38r3q52rjgehrm1qbvt47d4od3" and the hashed NextOwner "9mbsmfv1g1m6rc2mned7760ret9l7b68". 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 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "6eh94m38r3q52rjgehrm1qbvt47d4od3" equal the hashed NSEC3-owner "6eh94m38r3q52rjgehrm1qbvt47d4od3" and the hashed NextOwner "9mbsmfv1g1m6rc2mned7760ret9l7b68". 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 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.api.iotago.fr) sends a valid NSEC3 RR as result with the hashed owner name "6eh94m38r3q52rjgehrm1qbvt47d4od3" (unhashed: api.iotago.fr). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "1aqmi85bukv13e9pho3g2crechfrsjha" (unhashed: _tcp.api.iotago.fr) with the owner "cgp8rgtij7t2dghv6ldus4o62u7fc5hi" and the NextOwner "27ukagrso8h42u2ll2p4miu2tqj9v8a6". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cgp8rgtij7t2dghv6ldus4o62u7fc5hi.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.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 "2tte5vulgjjkpsjs8cpooq3h9jo39vmm" (unhashed: *.api.iotago.fr) with the owner "27ukagrso8h42u2ll2p4miu2tqj9v8a6" and the NextOwner "2uh7hrae17rk4opsci7dsr42b2e69ojl". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: A, RRSIG Validated: RRSIG-Owner 27ukagrso8h42u2ll2p4miu2tqj9v8a6.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "6eh94m38r3q52rjgehrm1qbvt47d4od3" equal the hashed NSEC3-owner "6eh94m38r3q52rjgehrm1qbvt47d4od3" and the hashed NextOwner "9mbsmfv1g1m6rc2mned7760ret9l7b68". 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 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



Status: Good. NoData-Proof required and found.

Zone: www.api.iotago.fr
www.api.iotago.fr
0 DS RR in the parent zone found



Bitmap: A, NS, SOA, MX, TXT, AAAA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cgp8rgtij7t2dghv6ldus4o62u7fc5hi.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "6eh94m38r3q52rjgehrm1qbvt47d4od3" as Owner. That's the Hash of "api.iotago.fr" with the NextHashedOwnerName "9mbsmfv1g1m6rc2mned7760ret9l7b68". So that domain name is the Closest Encloser of "www.api.iotago.fr". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner 6eh94m38r3q52rjgehrm1qbvt47d4od3.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr



The ClosestEncloser says, that "*.api.iotago.fr" with the Hash "2tte5vulgjjkpsjs8cpooq3h9jo39vmm" 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 "27ukagrso8h42u2ll2p4miu2tqj9v8a6" and the Next Owner "2uh7hrae17rk4opsci7dsr42b2e69ojl", 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, RRSIG Validated: RRSIG-Owner 27ukagrso8h42u2ll2p4miu2tqj9v8a6.iotago.fr., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2023, 19:30:45 +, Signature-Inception: 20.11.2023, 19:30:45 +, KeyTag 393, Signer-Name: iotago.fr


3. Name Servers

DomainNameserverNS-IP
www.api.iotago.fr
  dns11.ovh.net

api.iotago.fr
  dns11.ovh.net
213.251.188.130
Roubaix/Hauts-de-France/France (FR) - OVH SAS


 
2001:41d0:1:4a82::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS

iotago.fr
  dns11.ovh.net
213.251.188.130
Roubaix/Hauts-de-France/France (FR) - OVH SAS


 
2001:41d0:1:4a82::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS


  ns11.ovh.net
213.251.128.130
Roubaix/Hauts-de-France/France (FR) - OVH SAS


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

fr
  a.nic.fr


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


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


  f.ext.nic.fr / s2.dex


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


4. SOA-Entries


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


Domain:fr
Zone-Name:fr
Primary:a.nic.fr
Mail:dnsmaster.afnic.fr
Serial:2236943493
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:4


Domain:iotago.fr
Zone-Name:iotago.fr
Primary:dns11.ovh.net
Mail:tech.ovh.net
Serial:2023112001
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:api.iotago.fr
Zone-Name:iotago.fr
Primary:dns11.ovh.net
Mail:tech.ovh.net
Serial:2023112001
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:www.api.iotago.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://api.iotago.fr/
82.65.66.86
301
https://api.iotago.fr/
Html is minified: 109.03 %
0.423
A
Server: nginx/1.22.1
Date: Mon, 20 Nov 2023 21:30:34 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://api.iotago.fr/

• https://api.iotago.fr/
82.65.66.86
-14

10.030
T
Timeout - The operation has timed out

• http://api.iotago.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
82.65.66.86
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://api.iotago.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 109.03 %
1.970
A
Visible Content: 301 Moved Permanently nginx/1.22.1
Server: nginx/1.22.1
Date: Mon, 20 Nov 2023 21:30:46 GMT
Content-Type: text/html
Content-Length: 169
Connection: close
Location: https://api.iotago.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://api.iotago.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-14

10.027
T
Timeout - The operation has timed out
Visible Content:

• https://82.65.66.86/
82.65.66.86
-14

10.046
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "api.iotago.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: 3151 (complete: 231048)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: api.iotago.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: api.iotago.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.
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
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 api.iotago.fr, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.api.iotago.fr

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 11 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 11 Queries complete, 11 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.dns11.ovh.net (2001:41d0:1:4a82::1, 213.251.188.130), ns11.ovh.net (2001:41d0:1:1982::1, 213.251.128.130)
Ok (4 - 8):: An average of 5.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns11.ovh.net, ns11.ovh.net, 2 Name Servers included in Delegation: dns11.ovh.net, ns11.ovh.net, 2 Name Servers included in 1 Zone definitions: dns11.ovh.net, ns11.ovh.net, 1 Name Servers listed in SOA.Primary: dns11.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns11.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns11.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: dns11.ovh.net, ns11.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
AGood: All name servers have ipv4- and ipv6-addresses.: 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
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
AGood: Name Server IPv4-addresses from different subnet found:
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:1982:, 2001:41d0:0001:4a82:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.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.
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: ok (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: dns11.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.
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.

4. Content- and Performance-critical Checks

https://api.iotago.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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
ADuration: 83203 milliseconds, 83.203 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)

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


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: dns11.ovh.net, ns11.ovh.net

QNr.DomainTypeNS used
1
net
NS
m.root-servers.net (2001:dc3::35)

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
dns11.ovh.net: 2001:41d0:1:4a82::1, 213.251.188.130
NS
l.gtld-servers.net (2001:500:d937::30)

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

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
3
dns13.ovh.net
NS
l.gtld-servers.net (2001:500:d937::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
4
ns13.ovh.net
NS
l.gtld-servers.net (2001:500:d937::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
ns15.ovh.net
NS
l.gtld-servers.net (2001:500:d937::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
dns13.ovh.net: 213.251.188.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
7
dns13.ovh.net: 2001:41d0:1:4a84::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
8
ns13.ovh.net: 213.251.128.132
A
dns10.ovh.net (2001:41d0:1:4a81::1)
9
ns13.ovh.net: 2001:41d0:1:1984::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
10
ns15.ovh.net: 213.251.128.134
A
dns10.ovh.net (2001:41d0:1:4a81::1)
11
ns15.ovh.net: 2001:41d0:1:1986::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
api.iotago.fr
0

no CAA entry found
1
0
iotago.fr
0

no CAA entry found
1
0
fr
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
iotago.fr
v=spf1 include:mx.ovh.com ~all
ok
1
0
api.iotago.fr

ok
1
0
_acme-challenge.api.iotago.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.api.iotago.fr.iotago.fr

perhaps wrong
1
0
_acme-challenge.api.iotago.fr.api.iotago.fr

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=3515cf49-87a5-4820-8ede-8eb4d0f5e5ff


Last Result: https://check-your-website.server-daten.de/?q=api.iotago.fr - 2023-11-20 22:29:59


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro