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





1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
xsc.cloud
A
80.57.207.79
Helmond/North Brabant/Netherlands (NL) - chello Broadband
Hostname: g207079.upc-g.chello.nl
yes
1
0

AAAA

yes


www.xsc.cloud
CNAME
xsc.synology.me
yes
1
0

A
80.57.207.79
Helmond/North Brabant/Netherlands (NL) - chello Broadband
Hostname: g207079.upc-g.chello.nl
yes


*.xsc.cloud
A

yes



AAAA

yes



CNAME
xsc.synology.me
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (some minor bugs wildcard + nsec/nsec3)

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 46594, Flags 256



Public Key with Algorithm 8, KeyTag 48903, 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.2020, 00:00:00 +, Signature-Inception: 20.06.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: cloud
cloud
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 49804, DigestType 1 and Digest BLU30AyRXngkMlhJSFULuzn/iKA=



DS with Algorithm 8, KeyTag 49804, DigestType 2 and Digest d4HF1Oz0vQhFtJ0psueb0doYZXJQlvrrLQOTt4/RBJw=



1 RRSIG RR to validate DS RR found



RRSIG-Owner cloud., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.07.2020, 05:00:00 +, Signature-Inception: 27.06.2020, 04:00:00 +, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 2538, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner cloud., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.07.2020, 23:32:11 +, Signature-Inception: 22.06.2020, 22:40:45 +, KeyTag 2538, Signer-Name: cloud



RRSIG-Owner cloud., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.07.2020, 23:32:11 +, Signature-Inception: 22.06.2020, 22:40:45 +, KeyTag 49804, Signer-Name: cloud



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 49804, DigestType 1 and Digest "BLU30AyRXngkMlhJSFULuzn/iKA=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: xsc.cloud
xsc.cloud
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 "g5dcr9hgalj99gb4iiftd7r4881dne00" between the hashed NSEC3-owner "g5d5bhbjmnp3t3gbh2ovtkg4s7ccre0g" and the hashed NextOwner "g5e1kt5aevvo6kadgo9qcqk6fosrsktl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner g5d5bhbjmnp3t3gbh2ovtkg4s7ccre0g.cloud., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 24.07.2020, 21:26:21 +, Signature-Inception: 24.06.2020, 20:44:53 +, KeyTag 2538, Signer-Name: cloud



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k6nnfqiccqt79kvb1rieurknvn2tfr6a" as Owner. That's the Hash of "cloud" with the NextHashedOwnerName "k6nvreqaguj98dpbkopamjma76ma1sj4". So that domain name is the Closest Encloser of "xsc.cloud". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner k6nnfqiccqt79kvb1rieurknvn2tfr6a.cloud., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 22.07.2020, 23:19:33 +, Signature-Inception: 22.06.2020, 22:36:29 +, KeyTag 2538, Signer-Name: cloud



0 DNSKEY RR found




Zone: www.xsc.cloud
www.xsc.cloud
0 DS RR in the parent zone found

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 46594, Flags 256



Public Key with Algorithm 8, KeyTag 48903, 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.2020, 00:00:00 +, Signature-Inception: 20.06.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: me
me
2 DS RR in the parent zone found



DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest CboetNIEAmIIgf2YSJlEF4ANsmo=



DS with Algorithm 7, KeyTag 2569, DigestType 2 and Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.07.2020, 05:00:00 +, Signature-Inception: 27.06.2020, 04:00:00 +, KeyTag 48903, Signer-Name: (root)



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



Fatal error: Parent zone has a signed DS RR (Algorithm 7, KeyTag 2569, DigestType 1, Digest CboetNIEAmIIgf2YSJlEF4ANsmo=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.



Fatal error: Parent zone has a signed DS RR (Algorithm 7, KeyTag 2569, DigestType 2, Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.

Zone: synology.me
synology.me
2 DS RR in the parent zone found



DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest CboetNIEAmIIgf2YSJlEF4ANsmo=



DS with Algorithm 7, KeyTag 2569, DigestType 2 and Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.07.2020, 05:00:00 +, Signature-Inception: 27.06.2020, 04:00:00 +, KeyTag 48903, Signer-Name: (root)



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



0 DNSKEY RR found






Fatal error: Parent zone has a signed DS RR (Algorithm 7, KeyTag 2569, DigestType 1, Digest CboetNIEAmIIgf2YSJlEF4ANsmo=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.



Fatal error: Parent zone has a signed DS RR (Algorithm 7, KeyTag 2569, DigestType 2, Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.

Zone: xsc.synology.me
xsc.synology.me
0 DS RR in the parent zone found



0 DNSKEY RR found




3. Name Servers

DomainNameserverNS-IP
xsc.cloud
  ns39.domaincontrol.com / p09
97.74.109.20
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC


 
2603:5:21d1::14
Scottsdale/Arizona/United States (US) - GoDaddy.com


  ns40.domaincontrol.com / p04
173.201.77.20
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC


 
2603:5:22d1::14
Scottsdale/Arizona/United States (US) - GoDaddy.com

cloud
  a.nic.cloud / dns3.frpar1


  b.nic.cloud / dns1.nlams1


  c.nic.cloud / dns2.defra1


  d.nic.cloud / dns3.frpar1


xsc.synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC


  ddns-ns2.quickconnect.to
68.183.254.129
London/England/United Kingdom (GB) - DigitalOcean, LLC

synology.me
  a0.nic.me / ns009b.app30.nrt1.afilias-nst.info
199.253.59.1
Chiyoda/Tokyo/Japan (JP) - Afilias, Inc.


 
2001:500:53::1
Palo Alto/California/United States (US) - Afilias, Inc.


  a2.nic.me / 2.fra.pch
199.249.119.1
Chicago/Illinois/United States (US) - WoodyNet


 
2001:500:47::1
Ambler/Pennsylvania/United States (US) - WoodyNet


  b0.nic.me / ns009b.app29.ams2.afilias-nst.info
199.253.60.1
Los Angeles/California/United States (US) - Afilias, Inc.


 
2001:500:54::1
Zurich/Switzerland (CH) - Afilias, Inc.


  b2.nic.me / 5.fra.pch
199.249.127.1
Chicago/Illinois/United States (US) - WoodyNet


 
2001:500:4f::1
New York/United States (US) - WoodyNet


  c0.nic.me / ns009b.app3.ams2.afilias-nst.info
199.253.61.1
Washington/District of Columbia/United States (US) - Afilias, Inc.


 
2001:500:55::1
Zurich/Switzerland (CH) - Afilias, Inc.


  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC


  ddns-ns2.quickconnect.to
68.183.254.129
London/England/United Kingdom (GB) - DigitalOcean, LLC


4. SOA-Entries


Domain:cloud
Zone-Name:cloud
Primary:a.nic.cloud
Mail:support.ariservices.com
Serial:1593269093
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:4


Domain:xsc.cloud
Zone-Name:xsc.cloud
Primary:ns39.domaincontrol.com
Mail:dns.jomax.net
Serial:2020051601
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4



Domain:synology.me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:10


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:365908051
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:365908054
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:xsc.synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:365908051
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:xsc.synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:365908054
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
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://xsc.cloud/
80.57.207.79
-14

10.023
T
Timeout - The operation has timed out

• http://www.xsc.cloud/
80.57.207.79
-14

10.014
T
Timeout - The operation has timed out

• https://xsc.cloud/
80.57.207.79
-14

10.007
T
Timeout - The operation has timed out

• https://www.xsc.cloud/
80.57.207.79
-14

10.023
T
Timeout - The operation has timed out

• http://xsc.cloud/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.57.207.79
-14

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

• http://www.xsc.cloud/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
80.57.207.79
-14

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

• https://80.57.207.79/
80.57.207.79
-14

10.037
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "xsc.cloud" is domain, public suffix is ".cloud", top-level-domain is ".cloud", top-level-domain-type is "generic", tld-manager is "ARUBA PEC S.p.A."
Agood: All ip addresses are public addresses
Warning: Only one ip address found: www.xsc.cloud has only one ip address.
Warning: Only one ip address found: xsc.cloud 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: www.xsc.cloud 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: xsc.cloud 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 www.xsc.cloud, 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 xsc.cloud, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns39.domaincontrol.com, ns40.domaincontrol.com, 2 Name Servers included in Delegation: ns39.domaincontrol.com, ns40.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns39.domaincontrol.com, ns40.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns39.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns39.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns39.domaincontrol.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: ns39.domaincontrol.com, ns40.domaincontrol.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
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: 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: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.77., 97.74.109.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21d1:, 2603:0005:22d1:, 2 different subnets (first four blocks): 2603:0005:21d1:0000:, 2603:0005:22d1:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a0.nic.me / 199.253.59.1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app30.nrt1.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: a0.nic.me / 2001:500:53::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app8.nrt1.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: a2.nic.me / 199.249.119.1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (2.fra.pch). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: a2.nic.me / 2001:500:47::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (2.ber.pch). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: b0.nic.me / 199.253.60.1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app29.ams2.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: b0.nic.me / 2001:500:54::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app7.ams2.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: b2.nic.me / 199.249.127.1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (5.fra.pch). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: b2.nic.me / 2001:500:4f::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (4.fra.pch). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: c0.nic.me / 199.253.61.1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app3.ams2.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: c0.nic.me / 2001:500:55::1: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (ns009b.app3.ams2.afilias-nst.info). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
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

http://xsc.cloud/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.57.207.79
-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.xsc.cloud/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 80.57.207.79
-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: 185494 milliseconds, 185.494 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
3
12

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1718098669
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-06-25 02:40:03
2020-09-23 02:40:03
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1581519356
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-25 14:37:10
2020-07-24 14:37:10
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1581480923
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-25 14:10:52
2020-07-24 14:10:52
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1527702946
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-29 15:54:28
2020-06-27 15:54:28
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1527635775
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-29 15:08:34
2020-06-27 15:08:34
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1508740662
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-21 00:20:02
2020-06-19 00:20:02
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud - 4 entries


1508713344
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-21 00:00:46
2020-06-19 00:00:46
xsc.cloud - 1 entries


1293541051
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-08 13:34:56
2020-03-07 13:34:56
xsc.cloud - 1 entries


1265277450
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-24 17:18:04
2020-02-22 17:18:04
xsc.cloud - 1 entries


1265205176
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-24 16:21:33
2020-02-22 16:21:33
xsc.cloud - 1 entries


1262011353
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-23 00:59:47
2020-02-21 00:59:47
xsc.cloud - 1 entries


1261830948
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-22 22:52:12
2020-02-20 22:52:12
xsc.cloud - 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=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
3
12

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3000335876
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-06-25 00:40:03
2020-09-23 00:40:03
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2784594066
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-25 12:37:10
2020-07-24 12:37:10
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2784549086
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-25 12:10:52
2020-07-24 12:10:52
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2644310072
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-29 13:54:28
2020-06-27 13:54:28
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2642197772
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-29 13:08:34
2020-06-27 13:08:34
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2606356439
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-20 23:20:02
2020-06-18 22:20:02
ds.xsc.cloud, vpn.xsc.cloud, www.xsc.cloud, xsc.cloud
4 entries


2606287636
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-03-20 23:00:46
2020-06-18 22:00:46
xsc.cloud
1 entries


2244402138
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-08 12:34:56
2020-03-07 12:34:56
xsc.cloud
1 entries


2154278837
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-24 16:18:04
2020-02-22 16:18:04
xsc.cloud
1 entries


2153896033
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-24 15:21:33
2020-02-22 15:21:33
xsc.cloud
1 entries


2142891816
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-22 23:59:47
2020-02-20 23:59:47
xsc.cloud
1 entries


2142524642
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-22 21:52:12
2020-02-20 21:52:12
xsc.cloud
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: ns39.domaincontrol.com, ns40.domaincontrol.com

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::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
ns39.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns40.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
4
net
NS
k.root-servers.net (2001:7fd::1)

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
5
a1-245.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
6
a11-64.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
7
a20-65.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
8
a6-66.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
9
a8-67.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
10
a4-67.akam.net: 72.246.46.67
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
11
a6-67.akam.net
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a4-67.akam.net
72.246.46.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
23
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
ns39.domaincontrol.com: 97.74.109.20
A
a1-245.akam.net (2600:1401:2::f5)
25
ns39.domaincontrol.com: 2603:5:21d1::14
AAAA
a1-245.akam.net (2600:1401:2::f5)
26
ns40.domaincontrol.com: 173.201.77.20
A
a1-245.akam.net (2600:1401:2::f5)
27
ns40.domaincontrol.com: 2603:5:22d1::14
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
xsc.synology.me
0

no CAA entry found
1
0
www.xsc.cloud



1
0
synology.me
0

no CAA entry found
1
0
xsc.cloud
0

no CAA entry found
1
0
cloud
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
xsc.cloud

ok
1
0
www.xsc.cloud


1
0
xsc.synology.me

ok
1
0
_acme-challenge.xsc.cloud


1
0
_acme-challenge.www.xsc.cloud


1
0
_acme-challenge.xsc.synology.me

missing entry or wrong length
1
0
_acme-challenge.xsc.cloud.xsc.cloud


1
0
_acme-challenge.www.xsc.cloud.xsc.cloud


1
0
_acme-challenge.www.xsc.cloud.www.xsc.cloud


1
0
_acme-challenge.xsc.synology.me.xsc.synology.me

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=1dcf92f7-3a8a-4b8b-8223-8c23f36674c0


Last Result: https://check-your-website.server-daten.de/?q=xsc.cloud - 2020-06-27 17:02:00


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

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