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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
09.11.2020 12:49:05

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
www2.ipv6-things.com	A		yes	1	0
	AAAA	2602:806:a003:40e::1:5 Los Angeles/California/United States (US) - peterjin.org, LLC	yes
www.www2.ipv6-things.com		Name Error	yes	1	0
*.ipv6-things.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.www2.ipv6-things.com	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 26116, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2020, 00:00:00 +, Signature-Inception: 31.10.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: com
com	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.11.2020, 05:00:00 +, Signature-Inception: 09.11.2020, 04:00:00 +, KeyTag 26116, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 31510, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.11.2020, 19:24:21 +, Signature-Inception: 01.11.2020, 19:19:21 +, KeyTag 30909, Signer-Name: com


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


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

Zone: ipv6-things.com
ipv6-things.com	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 40439, DigestType 2 and Digest Dc946c81WL+SiukYBzxxC6VJC0tpNgRcpvLVggzdg/Q=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ipv6-things.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 16.11.2020, 10:32:10 +, Signature-Inception: 09.11.2020, 09:22:10 +, KeyTag 31510, Signer-Name: com


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 63255, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ipv6-things.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 40439, Signer-Name: ipv6-things.com


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


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

Zone: www2.ipv6-things.com
www2.ipv6-things.com	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 "k3vdero8dlj5rambvjnjcgtgrkbsckck" between the hashed NSEC3-owner "k3vdero8dlj5rambvjnjcgtgrkbsckck" and the hashed NextOwner "kthcu4siuim3paed0p9it08g28pcjse8". So the parent zone confirmes the not-existence of a DS RR. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	0 DNSKEY RR found





	RRSIG Type 28 validates the AAAA - Result: 2602:0806:A003:040E:0000:0000:0001:0005 Validated: RRSIG-Owner www2.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	A-Query sends a valid NSEC3 RR as result with the hashed query name "k3vdero8dlj5rambvjnjcgtgrkbsckck" equal the hashed NSEC3-owner "k3vdero8dlj5rambvjnjcgtgrkbsckck" and the hashed NextOwner "kthcu4siuim3paed0p9it08g28pcjse8". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "k3vdero8dlj5rambvjnjcgtgrkbsckck" equal the hashed NSEC3-owner "k3vdero8dlj5rambvjnjcgtgrkbsckck" and the hashed NextOwner "kthcu4siuim3paed0p9it08g28pcjse8". 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: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "k3vdero8dlj5rambvjnjcgtgrkbsckck" equal the hashed NSEC3-owner "k3vdero8dlj5rambvjnjcgtgrkbsckck" and the hashed NextOwner "kthcu4siuim3paed0p9it08g28pcjse8". 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: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www2.ipv6-things.com) sends a valid NSEC3 RR as result with the hashed owner name "k3vdero8dlj5rambvjnjcgtgrkbsckck" (unhashed: www2.ipv6-things.com). So that's the Closest Encloser of the query name. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "3230jkmvg76tmkckfuaorg67gu4f4g6m" (unhashed: _tcp.www2.ipv6-things.com) with the owner "2jvogg91191odeuhh3kk0gg9090e2o48" and the NextOwner "5cg39f9ucm9rkje0oam7j3pucrdma3h0". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner 2jvogg91191odeuhh3kk0gg9090e2o48.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	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 "0uqs619kp01pp1uvp2nuuknhc7bdp1mb" (unhashed: *.www2.ipv6-things.com) with the owner "014jfn7q0ni6eb4k90h6csaq9mgoq3r7" and the NextOwner "1lrobit27jno9l65eobvisgh83mhkmfb". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner 014jfn7q0ni6eb4k90h6csaq9mgoq3r7.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "k3vdero8dlj5rambvjnjcgtgrkbsckck" equal the hashed NSEC3-owner "k3vdero8dlj5rambvjnjcgtgrkbsckck" and the hashed NextOwner "kthcu4siuim3paed0p9it08g28pcjse8". 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: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	Status: Good. NoData-Proof required and found.

Zone: www.www2.ipv6-things.com
www.www2.ipv6-things.com	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 "jk2vcques0sjvl3dfvvfbgfk6v5fj58p" between the hashed NSEC3-owner "hu6c8l40baoptr6r2jum4riklg98m51g" and the hashed NextOwner "k3vdero8dlj5rambvjnjcgtgrkbsckck". So the parent zone confirmes the not-existence of a DS RR. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner hu6c8l40baoptr6r2jum4riklg98m51g.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k3vdero8dlj5rambvjnjcgtgrkbsckck" as Owner. That's the Hash of "www2.ipv6-things.com" with the NextHashedOwnerName "kthcu4siuim3paed0p9it08g28pcjse8". So that domain name is the Closest Encloser of "www.www2.ipv6-things.com". Opt-Out: False. Bitmap: AAAA, RRSIG Validated: RRSIG-Owner k3vdero8dlj5rambvjnjcgtgrkbsckck.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com


	The ClosestEncloser says, that "*.www2.ipv6-things.com" with the Hash "0uqs619kp01pp1uvp2nuuknhc7bdp1mb" 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 "014jfn7q0ni6eb4k90h6csaq9mgoq3r7" and the Next Owner "1lrobit27jno9l65eobvisgh83mhkmfb", 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: AAAA, RRSIG Validated: RRSIG-Owner 014jfn7q0ni6eb4k90h6csaq9mgoq3r7.ipv6-things.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 30.11.2020, 10:30:49 +, Signature-Inception: 08.11.2020, 10:30:49 +, KeyTag 63255, Signer-Name: ipv6-things.com

3. Name Servers

Domain	Nameserver	NS-IP
www.www2.ipv6-things.com	• ns-cloud-a1.googledomains.com
www2.ipv6-things.com	• ns-cloud-a1.googledomains.com	216.239.32.106 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6a Montreal/Quebec/Canada (CA) - Google LLC	•
ipv6-things.com	• ns-cloud-a1.googledomains.com	216.239.32.106 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6a Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-a2.googledomains.com	216.239.34.106 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6a Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-a3.googledomains.com	216.239.36.106 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6a Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-a4.googledomains.com	216.239.38.106 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6a Montreal/Quebec/Canada (CA) - Google LLC	•
com	• 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		•

4. SOA-Entries

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1604922526
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	11

Domain:	com
Zone-Name:	com
Primary:	a.gtld-servers.net
Mail:	nstld.verisign-grs.com
Serial:	1604922541
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	2

Domain:	ipv6-things.com
Zone-Name:	ipv6-things.com
Primary:	ns-cloud-a1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	21
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	8

Domain:	www2.ipv6-things.com
Zone-Name:	ipv6-things.com
Primary:	ns-cloud-a1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	21
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	2

Domain:	www.www2.ipv6-things.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

Startaddress: https://www2.ipv6-things.com, address used: https://www2.ipv6-things.com/, Screenshot created 2020-11-09 12:50:14 +00:0

Mobil (412px x 732px)

468 milliseconds

Screenshot mobile - https://www2.ipv6-things.com/

Mobil + Landscape (732px x 412px)

485 milliseconds

Screenshot mobile landscape - https://www2.ipv6-things.com/

Screen (1280px x 1680px)

944 milliseconds

Screenshot Desktop - https://www2.ipv6-things.com/

Mobile- and other Chrome-Checks

	width	height
visual Viewport	396	716
content Size	474	778

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://www2.ipv6-things.com/ 2602:806:a003:40e::1:5	301	https://www2.ipv6-things.com/ Html is minified: 108.54 %	0.360	A
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 09 Nov 2020 11:49:58 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://www2.ipv6-things.com/
Strict-Transport-Security: max-age=31536000; includeSubDomains

• https://www2.ipv6-things.com/ 2602:806:a003:40e::1:5 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1026	200	Html is minified: 163.48 % Other inline scripts (∑/total): 0/0	4.313	A
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 09 Nov 2020 11:49:59 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-Powered-By: Express
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Encoding: gzip

• http://www2.ipv6-things.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:806:a003:40e::1:5 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 109.46 % Other inline scripts (∑/total): 0/0	0.347	A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 09 Nov 2020 11:50:03 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://[2602:0806:a003:040e:0000:0000:0001:0005]/ 2602:806:a003:40e::1:5 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1026	200	Html is minified: 163.48 % Other inline scripts (∑/total): 0/0	4.517	N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 09 Nov 2020 11:50:04 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-Powered-By: Express
Strict-Transport-Security: max-age=31536000; includeSubDomains
Content-Encoding: gzip

7. Comments

	1. General Results, most used to calculate the result
A	name "www2.ipv6-things.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: www2.ipv6-things.com has only one ip address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: No cookie sent via http.
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 31536000 seconds = 365 days
A	Good: HSTS has includeSubdomains - directive
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (3 urls)
	http://www2.ipv6-things.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:806:a003:40e::1:5			Url with incomplete Content-Type - header - missing charset
A	http://www2.ipv6-things.com/ 2602:806:a003:40e::1:5	301	https://www2.ipv6-things.com/	Correct redirect http - https with the same domain name
N	https://[2602:0806:a003:040e:0000:0000:0001:0005]/ 2602:806:a003:40e::1:5	200		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
	Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www2.ipv6-things.com, 1 ip addresses, 1 different http results.
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
	3. DNS- and NameServer - Checks
A	Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-a1.googledomains.com.
A	Good: Only one SOA.Primary Name Server found.: ns-cloud-a1.googledomains.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-a1.googledomains.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: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.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: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: googledomains.com
A	Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
A	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: 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: ns-cloud-a1.googledomains.com: 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.
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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Good: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
	https://www2.ipv6-things.com/ 2602:806:a003:40e::1:5	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://[2602:0806:a003:040e:0000:0000:0001:0005]/ 2602:806:a003:40e::1:5	200		Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
	https://www2.ipv6-things.com/ 2602:806:a003:40e::1:5	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
	https://[2602:0806:a003:040e:0000:0000:0001:0005]/ 2602:806:a003:40e::1:5	200		Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
A	Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
A	Good: All checked attribute values are enclosed in quotation marks (" or ').
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
	http://www2.ipv6-things.com/ 2602:806:a003:40e::1:5	301		Warning: HSTS header sent via http has no effect
A	Duration: 75737 milliseconds, 75.737 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

www2.ipv6-things.com

2602:806:a003:40e::1:5

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

www2.ipv6-things.com

2602:806:a003:40e::1:5

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=ipv6-things.com
	2	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

[2602:0806:a003:040e:0000:0000:0001:0005]

2602:806:a003:40e::1:5

443

name does not match

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

[2602:0806:a003:040e:0000:0000:0001:0005]

2602:806:a003:40e::1:5

443

name does not match

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

error checking OCSP stapling

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=ipv6-things.com
	2	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

9. Certificates

CN=ipv6-things.com

09.11.2020

07.02.2021
1398 days expired

*.ipv6-things.com, ipv6-things.com - 2 entries

CN=ipv6-things.com

09.11.2020

07.02.2021
1398 days expired

*.ipv6-things.com, ipv6-things.com - 2 entries

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	037A26E29F08D88066A697A550E7CC208206
Thumbprint:	BD79A5DAFBFD917ECBF6E95619BDA0E3B3F42192
SHA256 / Certificate:	aZo808ykcmg8KSiU1BWxa/36s/c8GVl/a83QGGnvuew=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	ddd67eb0f4f10fefb77e8ca5bfdfe459f630c10737ba50a4701b3f3f95641382
SHA256 hex / Subject Public Key Information (SPKI):	ddd67eb0f4f10fefb77e8ca5bfdfe459f630c10737ba50a4701b3f3f95641382
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1360 days expired

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1360 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0A0141420000015385736A0B85ECA708
Thumbprint:	E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:	JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):	25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1163 days expired

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1163 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	44AFB080D6A327BA893039862EF8406B
Thumbprint:	DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:	BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

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

Small Code Update - wait one minute

11. Html-Content - Entries

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

QNr.	Domain	Type	NS used
1	com	NS	b.root-servers.net (2001:500:200::b)
	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	ns-cloud-a1.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
3	ns-cloud-a2.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
4	ns-cloud-a3.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
5	ns-cloud-a4.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
6	ns-cloud-a1.googledomains.com: 216.239.32.106	A	ns5.googledomains.com (2001:4860:4802:32::a)
7	ns-cloud-a1.googledomains.com: 2001:4860:4802:32::6a	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
8	ns-cloud-a2.googledomains.com: 216.239.34.106	A	ns5.googledomains.com (2001:4860:4802:32::a)
9	ns-cloud-a2.googledomains.com: 2001:4860:4802:34::6a	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
10	ns-cloud-a3.googledomains.com: 216.239.36.106	A	ns5.googledomains.com (2001:4860:4802:32::a)
11	ns-cloud-a3.googledomains.com: 2001:4860:4802:36::6a	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
12	ns-cloud-a4.googledomains.com: 216.239.38.106	A	ns5.googledomains.com (2001:4860:4802:32::a)
13	ns-cloud-a4.googledomains.com: 2001:4860:4802:38::6a	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)

14. CAA - Entries

Domainname	Value	∑ Queries
www2.ipv6-things.com	no CAA entry found	1
ipv6-things.com	no CAA entry found	1
com	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
ipv6-things.com	ok	1
www2.ipv6-things.com	ok	1
_acme-challenge.www2.ipv6-things.com	Name Error - The domain name does not exist	1
_acme-challenge.www2.ipv6-things.com.ipv6-things.com	Name Error - The domain name does not exist	1
_acme-challenge.www2.ipv6-things.com.www2.ipv6-things.com	Name Error - The domain name does not exist	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=1eba4e77-1395-4cb2-9d66-fd3aacb0aae7

Last Result: https://check-your-website.server-daten.de/?q=www2.ipv6-things.com - 2020-11-09 12:49:05

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

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

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

Mobile- and other Chrome-Checks

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

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

11. Html-Content - Entries

Summary

Details

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks