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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
28.05.2022 13:33:23

Older results

T - 22.01.2020 00:52:17

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
jayotis.works	A	137.186.158.213 Edmonton/Alberta/Canada (CA) - TELUS Communications Inc Hostname: d137-186-158-213.abhsia.telus.net	yes	1	0
	AAAA		yes
www.jayotis.works	A	137.186.156.54 Edmonton/Alberta/Canada (CA) - TELUS Communications Inc Hostname: d137-186-156-54.abhsia.telus.net	yes	1	0
	AAAA		yes
*.jayotis.works	A	137.186.156.54	yes
	AAAA		yes
	CNAME		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 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.06.2022, 00:00:00 +, Signature-Inception: 21.05.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: works
works	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 46672, DigestType 2 and Digest AzndmbhrlrjkN5COmuo+tXj60N4hG9jPek/miF4KzdI=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner works., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.06.2022, 05:00:00 +, Signature-Inception: 28.05.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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 15060, Flags 256


	Public Key with Algorithm 8, KeyTag 17496, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner works., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 16.06.2022, 21:33:01 +, Signature-Inception: 26.05.2022, 20:33:01 +, KeyTag 46672, Signer-Name: works


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


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

Zone: jayotis.works
jayotis.works	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest w07gvlN1TSKIMia4/kLouG67VUZRmz/LB0BXwvmsGTQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner jayotis.works., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.06.2022, 21:33:01 +, Signature-Inception: 26.05.2022, 20:33:01 +, KeyTag 17496, Signer-Name: works


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


	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 jayotis.works., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2022, 17:39:10 +, Signature-Inception: 18.05.2022, 17:39:10 +, KeyTag 2371, Signer-Name: jayotis.works


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


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


	RRSIG Type 1 validates the A - Result: 137.186.158.213 Validated: RRSIG-Owner jayotis.works., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	RRSIG Type 16 validates the TXT - Result: txt Validated: RRSIG-Owner jayotis.works., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	CNAME-Query sends a valid NSEC RR as result with the query name "jayotis.works" equal the NSEC-owner "jayotis.works" and the NextOwner "\000.jayotis.works". 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 jayotis.works., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "jayotis.works" equal the NSEC-owner "jayotis.works" and the NextOwner "\000.jayotis.works". 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 jayotis.works., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.jayotis.works) sends a valid NSEC RR as result with the query name "_443._tcp.jayotis.works" equal the NSEC-owner "_443._tcp.jayotis.works" and the NextOwner "\000._443._tcp.jayotis.works". 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: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner _443._tcp.jayotis.works., Algorithm: 13, 4 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "jayotis.works" equal the NSEC-owner "jayotis.works" and the NextOwner "\000.jayotis.works". 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 jayotis.works., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:44 +, Signature-Inception: 27.05.2022, 10:33:44 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.

Zone: www.jayotis.works
www.jayotis.works	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.jayotis.works" and the NextOwner "\000.www.jayotis.works". 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 1 validates the A - Result: 137.186.156.54 Validated: RRSIG-Owner www.jayotis.works., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.05.2022, 12:33:45 +, Signature-Inception: 27.05.2022, 10:33:45 +, KeyTag 34505, Signer-Name: jayotis.works


	CNAME-Query sends a valid NSEC RR as result with the query name "www.jayotis.works" equal the NSEC-owner "www.jayotis.works" and the NextOwner "\000.www.jayotis.works". 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, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.jayotis.works., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:45 +, Signature-Inception: 27.05.2022, 10:33:45 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.jayotis.works" equal the NSEC-owner "www.jayotis.works" and the NextOwner "\000.www.jayotis.works". 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, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.jayotis.works., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:46 +, Signature-Inception: 27.05.2022, 10:33:46 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "www.jayotis.works" equal the NSEC-owner "www.jayotis.works" and the NextOwner "\000.www.jayotis.works". 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, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner www.jayotis.works., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:45 +, Signature-Inception: 27.05.2022, 10:33:45 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.jayotis.works) sends a valid NSEC RR as result with the query name "_443._tcp.www.jayotis.works" equal the NSEC-owner "_443._tcp.www.jayotis.works" and the NextOwner "\000._443._tcp.www.jayotis.works". 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: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, 53, HIP, 61, 64, 65, 99, URI, CAA Validated: RRSIG-Owner _443._tcp.www.jayotis.works., Algorithm: 13, 5 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:46 +, Signature-Inception: 27.05.2022, 10:33:46 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.jayotis.works" equal the NSEC-owner "www.jayotis.works" and the NextOwner "\000.www.jayotis.works". 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, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, 99, URI Validated: RRSIG-Owner www.jayotis.works., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.05.2022, 12:33:46 +, Signature-Inception: 27.05.2022, 10:33:46 +, KeyTag 34505, Signer-Name: jayotis.works


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.jayotis.works	• donald.ns.cloudflare.com / 20m882		•
jayotis.works	• donald.ns.cloudflare.com / 67m37	2606:4700:58::adf5:3b9e San Francisco/California/United States (US) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c19e San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:219e London/England/United Kingdom (GB) - CloudFLARENET-EU	•
	• miki.ns.cloudflare.com / 67m60	2606:4700:50::adf5:3aca San Francisco/California/United States (US) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c0ca San José/Provincia de San Jose/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:20ca London/England/United Kingdom (GB) - CloudFLARENET-EU	•
works	• v0n0.nic.works / app11.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• v0n1.nic.works / ns054b.app26.ams2.afilias-nst.info		•
	• v0n2.nic.works / ns054b.app16.ams2.afilias-nst.info		•
	• v0n3.nic.works / ns054b.app29.ams2.afilias-nst.info		•
	• v2n0.nic.works / LHR10		•
	• v2n1.nic.works / LHR8		•

4. SOA-Entries

Domain:	works
Zone-Name:	works
Primary:	v0n0.nic.works
Mail:	hostmaster.donuts.email
Serial:	1653736566
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	6

Domain:	jayotis.works
Zone-Name:	jayotis.works
Primary:	donald.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2278467650
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	3600
num Entries:	6

Domain:	www.jayotis.works
Zone-Name:	jayotis.works
Primary:	donald.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2278467650
Refresh:	10000
Retry:	2400
Expire:	604800
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

Domainname	Http-Status	Sec.	G
• http://jayotis.works/ 137.186.158.213	-14	10.060	T
Timeout - The operation has timed out

• http://www.jayotis.works/ 137.186.156.54	-14	10.047	T
Timeout - The operation has timed out

• https://jayotis.works/ 137.186.158.213	-14	10.044	T
Timeout - The operation has timed out

• https://www.jayotis.works/ 137.186.156.54	-14	10.046	T
Timeout - The operation has timed out

• http://jayotis.works/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 137.186.158.213	-14	10.046	T
Timeout - The operation has timed out
Visible Content:

• http://www.jayotis.works/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 137.186.156.54	-14	10.047	T
Timeout - The operation has timed out
Visible Content:

• https://137.186.156.54/ 137.186.156.54	-14	10.043	T
Timeout - The operation has timed out

• https://137.186.158.213/ 137.186.158.213	-14	10.063	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "jayotis.works" is domain, public suffix is ".works", top-level-domain is ".works", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .works-domains preloaded: 36 (complete: 175327)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: jayotis.works has only one ip address.
	Warning: Only one ip address found: www.jayotis.works 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: jayotis.works 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.jayotis.works has no ipv6 address.
A	Good: 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 jayotis.works, 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.jayotis.works, 1 ip addresses.
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 2 different Name Servers found: donald.ns.cloudflare.com, miki.ns.cloudflare.com, 2 Name Servers included in Delegation: donald.ns.cloudflare.com, miki.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: donald.ns.cloudflare.com, miki.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: donald.ns.cloudflare.com.
A	Good: Only one SOA.Primary Name Server found.: donald.ns.cloudflare.com.
A	Good: SOA.Primary Name Server included in the delegation set.: donald.ns.cloudflare.com.
A	Good: 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: donald.ns.cloudflare.com, miki.ns.cloudflare.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: 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
A	Good: Name servers with different Country locations found: 2 Name Servers, 3 Countries: CR, GB, US
A
A	Info: 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:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
A	Good: 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://jayotis.works/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 137.186.158.213	-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.jayotis.works/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 137.186.156.54	-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.
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 156160 milliseconds, 156.160 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. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: donald.ns.cloudflare.com, miki.ns.cloudflare.com

QNr.	Domain	Type	NS used
1	com	NS	h.root-servers.net (2001:500:1::53)
	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	donald.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	miki.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	donald.ns.cloudflare.com: 108.162.193.158, 172.64.33.158, 173.245.59.158	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5	donald.ns.cloudflare.com: 2606:4700:58::adf5:3b9e, 2803:f800:50::6ca2:c19e, 2a06:98c1:50::ac40:219e	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6	miki.ns.cloudflare.com: 108.162.192.202, 172.64.32.202, 173.245.58.202	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7	miki.ns.cloudflare.com: 2606:4700:50::adf5:3aca, 2803:f800:50::6ca2:c0ca, 2a06:98c1:50::ac40:20ca	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

14. CAA - Entries

Domainname	Value	∑ Queries
www.jayotis.works	no CAA entry found	1
jayotis.works	no CAA entry found	1
works	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
jayotis.works	txt	ok	1
www.jayotis.works		ok	1
_acme-challenge.jayotis.works		missing entry or wrong length	1
_acme-challenge.www.jayotis.works		missing entry or wrong length	1
_acme-challenge.jayotis.works.jayotis.works		perhaps wrong	1
_acme-challenge.www.jayotis.works.jayotis.works		perhaps wrong	1
_acme-challenge.www.jayotis.works.www.jayotis.works		perhaps wrong	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=b06bca2c-1c67-40ac-becf-2a07271f0ca6

Last Result: https://check-your-website.server-daten.de/?q=jayotis.works - 2022-05-28 13:33:23

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=jayotis.works