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




T

Timeout

Checked:
19.10.2021 07:33:34


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jcp-connect.fr
A
176.139.8.11
Rennes/Brittany/France (FR) - BOUYGUES Telecom
Hostname: static-176-139-8-11.ftth.abo.bbox.fr
yes
2
0

AAAA

yes


www.jcp-connect.fr
CNAME
jcp-connect.fr
yes
1
0

A
176.139.8.11
Rennes/Brittany/France (FR) - BOUYGUES Telecom
Hostname: static-176-139-8-11.ftth.abo.bbox.fr
yes


*.jcp-connect.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 14748, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.11.2021, 00:00:00 +, Signature-Inception: 11.10.2021, 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: 31.10.2021, 21:00:00 +, Signature-Inception: 18.10.2021, 20:00:00 +, KeyTag 14748, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 38315, 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: 19.11.2021, 12:20:20 +, Signature-Inception: 20.09.2021, 11:20:21 +, 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: jcp-connect.fr
jcp-connect.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 "dlatuctk32822tug5t0dpt58pdjodfh4" between the hashed NSEC3-owner "dlasmfi7cptnink1b9slruddpmn672c4" and the hashed NextOwner "dlb1fcnq7mdv8a53265umpvop6iq81iu". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner dlasmfi7cptnink1b9slruddpmn672c4.fr., Algorithm: 13, 2 Labels, original TTL: 5400 sec, Signature-expiration: 10.12.2021, 03:41:31 +, Signature-Inception: 11.10.2021, 03:21:50 +, KeyTag 38315, 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 "jcp-connect.fr". Opt-Out: True.
Bitmap: NS, SOA, TXT, NAPTR, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner hse6lveakji7ri5c4e8a03bfg5ha71ao.fr., Algorithm: 13, 2 Labels, original TTL: 5400 sec, Signature-expiration: 19.11.2021, 12:20:21 +, Signature-Inception: 20.09.2021, 11:20:21 +, KeyTag 38315, Signer-Name: fr



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 34505, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.11.2021, 18:44:49 +, Signature-Inception: 13.09.2021, 18:44:49 +, KeyTag 2371, Signer-Name: jcp-connect.fr



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



Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



RRSIG Type 1 validates the A - Result: 176.139.8.11
Validated: RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



RRSIG Type 16 validates the TXT - Result: 3ftdooh4l8mhu58mourjgkgg1d
Validated: RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



CNAME-Query sends a valid NSEC RR as result with the query name "jcp-connect.fr" equal the NSEC-owner "jcp-connect.fr" and the NextOwner "\000.jcp-connect.fr". 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, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "jcp-connect.fr" equal the NSEC-owner "jcp-connect.fr" and the NextOwner "\000.jcp-connect.fr". 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, NS, SOA, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.jcp-connect.fr) sends a valid NSEC RR as result with the query name "_443._tcp.jcp-connect.fr" equal the NSEC-owner "_443._tcp.jcp-connect.fr" and the NextOwner "\000._443._tcp.jcp-connect.fr". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.jcp-connect.fr., Algorithm: 13, 4 Labels, original TTL: 3600 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



Status: Good. NoData-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "jcp-connect.fr" equal the NSEC-owner "jcp-connect.fr" and the NextOwner "\000.jcp-connect.fr". 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, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, 99, URI Validated: RRSIG-Owner jcp-connect.fr., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr



Status: Good. NoData-Proof required and found.

Zone: www.jcp-connect.fr
www.jcp-connect.fr
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.jcp-connect.fr" and the NextOwner "\000.www.jcp-connect.fr". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA



RRSIG Type 5 validates the CNAME - Result: jcp-connect.fr
Validated: RRSIG-Owner www.jcp-connect.fr., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.10.2021, 06:33:46 +, Signature-Inception: 18.10.2021, 04:33:46 +, KeyTag 34505, Signer-Name: jcp-connect.fr


3. Name Servers

DomainNameserverNS-IP
jcp-connect.fr
  marty.ns.cloudflare.com / 67m22
108.162.193.204
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
172.64.33.204
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
173.245.59.204
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
2606:4700:58::adf5:3bcc
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c1cc
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:21cc
London/England/United Kingdom (GB) - CloudFLARENET-EU


  zelda.ns.cloudflare.com / 67m32
108.162.192.242
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
172.64.32.242
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
173.245.58.242
Newark/New Jersey/United States (US) - Cloudflare, Inc.


 
2606:4700:50::adf5:3af2
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c0f2
San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:20f2
London/England/United Kingdom (GB) - CloudFLARENET-EU

fr
  d.nic.fr / dns.nyc.nic.fr


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


  f.ext.nic.fr / s2.amx


  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:2228723454
Refresh:3600
Retry:1800
Expire:3600000
TTL:5400
num Entries:1


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


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


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


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


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


Domain:jcp-connect.fr
Zone-Name:jcp-connect.fr
Primary:marty.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2038331170
Refresh:10000
Retry:2400
Expire:604800
TTL:3600
num Entries:12


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://jcp-connect.fr/
176.139.8.11
-14

10.044
T
Timeout - The operation has timed out

• http://www.jcp-connect.fr/
176.139.8.11
-14

10.026
T
Timeout - The operation has timed out

• https://jcp-connect.fr/
176.139.8.11
-14

10.037
T
Timeout - The operation has timed out

• https://www.jcp-connect.fr/
176.139.8.11
-14

10.030
T
Timeout - The operation has timed out

• http://jcp-connect.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
176.139.8.11
-14

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

• http://www.jcp-connect.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
176.139.8.11
-14

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

• https://176.139.8.11/
176.139.8.11
-14

10.046
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "jcp-connect.fr" is domain, 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: 2245 (complete: 168171)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: jcp-connect.fr has only one ip address.
Warning: Only one ip address found: www.jcp-connect.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: jcp-connect.fr has no ipv6 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: www.jcp-connect.fr has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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 jcp-connect.fr, 1 ip addresses.
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 www.jcp-connect.fr, 1 ip addresses.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: marty.ns.cloudflare.com, zelda.ns.cloudflare.com, 2 Name Servers included in Delegation: marty.ns.cloudflare.com, zelda.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: marty.ns.cloudflare.com, zelda.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: marty.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: marty.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: marty.ns.cloudflare.com.
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: marty.ns.cloudflare.com, zelda.ns.cloudflare.com
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: com
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: cloudflare.com
AGood: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US
AInfo: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 172., 173., 3 different subnets (first two Bytes): 108.162., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.192., 108.162.193., 172.64.32., 172.64.33., 173.245.58., 173.245.59.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
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.

4. Content- and Performance-critical Checks

http://jcp-connect.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.139.8.11
-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.
http://www.jcp-connect.fr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.139.8.11
-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: 131986 milliseconds, 131.986 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)

Small Code Update - wait one minute


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

Small Code Update - wait one minute


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: marty.ns.cloudflare.com, zelda.ns.cloudflare.com

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (2001:500:2d::d)

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
marty.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
3
zelda.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
4
marty.ns.cloudflare.com: 108.162.193.204, 172.64.33.204, 173.245.59.204
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
marty.ns.cloudflare.com: 2606:4700:58::adf5:3bcc, 2803:f800:50::6ca2:c1cc, 2a06:98c1:50::ac40:21cc
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
zelda.ns.cloudflare.com: 108.162.192.242, 172.64.32.242, 173.245.58.242
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
zelda.ns.cloudflare.com: 2606:4700:50::adf5:3af2, 2803:f800:50::6ca2:c0f2, 2a06:98c1:50::ac40:20f2
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.jcp-connect.fr
0

no CAA entry found
1
0
jcp-connect.fr
0

no CAA entry found
1
0
fr
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jcp-connect.fr
3ftdooh4l8mhu58mourjgkgg1d
ok
1
0
www.jcp-connect.fr
3ftdooh4l8mhu58mourjgkgg1d
ok
1
0
_acme-challenge.jcp-connect.fr
gWrRqKV0Wf7G3IRWLvMAHTJob6ntFYA-mZjJmQV_W04
looks good, correct length, correct characters
1
0
_acme-challenge.www.jcp-connect.fr
X4x35Igc619M-V6OPOksmMuFvSHLYfXabsv7Go4LrGI
looks good, correct length, correct characters
1
0
_acme-challenge.jcp-connect.fr.jcp-connect.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jcp-connect.fr.jcp-connect.fr

Name Error - The domain name does not exist
1
0
_acme-challenge.www.jcp-connect.fr.www.jcp-connect.fr

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=000d2a5c-d3aa-4f47-874a-05f9a347b4ee


Last Result: https://check-your-website.server-daten.de/?q=jcp-connect.fr - 2021-10-19 07:33:34


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

<a href="https://check-your-website.server-daten.de/?q=jcp-connect.fr" target="_blank">Check this Site: jcp-connect.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