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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
12.05.2024 01:02:56

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
dpc.casa	A	8.17.89.134 San Jose/California/United States (US) - Paxio Inc. Hostname: 8-17-89-134.paxio.net	yes	1	0
	AAAA		yes
www.dpc.casa	A	8.17.89.134 San Jose/California/United States (US) - Paxio Inc. Hostname: 8-17-89-134.paxio.net	yes	1	0
	AAAA		yes
*.dpc.casa	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 5613, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 39931, DigestType 2 and Digest mHCUD0CbKp0iq4flI5+KGLHESptlKOzTGN140j6sdhs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner casa., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.05.2024, 17:00:00 +, Signature-Inception: 11.05.2024, 16:00:00 +, KeyTag 5613, Signer-Name: (root)


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 36348, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner casa., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 05.06.2024, 06:16:29 +, Signature-Inception: 06.05.2024, 05:42:33 +, KeyTag 36348, Signer-Name: casa


	RRSIG-Owner casa., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 05.06.2024, 06:16:29 +, Signature-Inception: 06.05.2024, 05:42:33 +, KeyTag 39931, Signer-Name: casa


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


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


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

Zone: dpc.casa
dpc.casa	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 17601, DigestType 1 and Digest rQ/G5qywIbtu//fy+p2qaCE/z/A=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dpc.casa., Algorithm: 8, 2 Labels, original TTL: 172800 sec, Signature-expiration: 10.06.2024, 08:30:50 +, Signature-Inception: 11.05.2024, 07:48:32 +, KeyTag 36348, Signer-Name: casa


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 1919, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 17601, Signer-Name: dpc.casa


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 17601, DigestType 1 and Digest "rQ/G5qywIbtu//fy+p2qaCE/z/A=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone


	RRSIG Type 1 validates the A - Result: 8.17.89.134 Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 180 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	RRSIG Type 257 validates the CAA - Result: 9\|issuewildletsencrypt.org Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 1799 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	CNAME-Query sends a valid NSEC RR as result with the query name "dpc.casa" equal the NSEC-owner "dpc.casa" and the NextOwner "chat.dpc.casa". 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, RRSIG, NSEC, DNSKEY, CAA Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "dpc.casa" equal the NSEC-owner "dpc.casa" and the NextOwner "chat.dpc.casa". 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, NS, SOA, RRSIG, NSEC, DNSKEY, CAA Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "dpc.casa" equal the NSEC-owner "dpc.casa" and the NextOwner "chat.dpc.casa". 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, RRSIG, NSEC, DNSKEY, CAA Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.dpc.casa) sends a valid NSEC RR as result with the owner name dpc.casa. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "dpc.casa" and the NextOwner "chat.dpc.casa". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.dpc.casa) sends a valid NSEC RR as result with the query name "_443._tcp.dpc.casa" between the NSEC-owner "dpc.casa" and the NextOwner "chat.dpc.casa". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.dpc.casa) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.dpc.casa" between the NSEC-owner "dpc.casa" and the NextOwner "chat.dpc.casa". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY, CAA Validated: RRSIG-Owner dpc.casa., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NXDomain-Proof required and found.

Zone: www.dpc.casa
www.dpc.casa	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.dpc.casa" and the NextOwner "dpc.casa". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	RRSIG Type 1 validates the A - Result: 8.17.89.134 Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 180 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	CNAME-Query sends a valid NSEC RR as result with the query name "www.dpc.casa" equal the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.dpc.casa" equal the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "www.dpc.casa" equal the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.dpc.casa) sends a valid NSEC RR as result with the owner name www.dpc.casa. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "www.dpc.casa" and the NextOwner "dpc.casa". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.dpc.casa) sends a valid NSEC RR as result with the query name "_443._tcp.www.dpc.casa" between the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.www.dpc.casa) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.www.dpc.casa" between the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.dpc.casa" equal the NSEC-owner "www.dpc.casa" and the NextOwner "dpc.casa". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.dpc.casa., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 23.05.2024, 00:00:00 +, Signature-Inception: 02.05.2024, 00:00:00 +, KeyTag 1919, Signer-Name: dpc.casa


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.dpc.casa	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1		•
dpc.casa	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.200 New York/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1024::200 Herndon/Virginia/United States (US) - NeuStar	•
	• dns2.registrar-servers.com / Auth_NC_Host1.Frankfurt_Node1	156.154.133.200 New York/United States (US) - NeuStar, Inc.	•
	•	2610:a1:1025::200 Ashburn/Virginia/United States (US) - NeuStar	•
casa	• a.nic.casa / dns4.defra1		•
	• b.nic.casa / dns2.defra1		•
	• c.nic.casa / dns1.defra1		•
	• x.nic.casa / Auth_Host3.Frankfurt_Node1		•
	• y.nic.casa / Auth_Host2.Frankfurt_Node1		•
	• z.nic.casa / Auth_Host2.Frankfurt_Node1		•

4. SOA-Entries

Domain:	casa
Zone-Name:	casa
Primary:	a.nic.casa
Mail:	admin.tldns.godaddy
Serial:	1715467535
Refresh:	1800
Retry:	300
Expire:	604800
TTL:	1800
num Entries:	6

Domain:	dpc.casa
Zone-Name:	dpc.casa
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1715386579
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	4

Domain:	www.dpc.casa
Zone-Name:	dpc.casa
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1715386579
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	1

5. Screenshots

Startaddress: https://www.dpc.casa/, address used: https://www.dpc.casa/, Screenshot created 2024-05-12 01:07:50 +00:0

Mobil (412px x 732px)

1042 milliseconds

Screenshot mobile - https://www.dpc.casa/

Mobil + Landscape (732px x 412px)

1059 milliseconds

Screenshot mobile landscape - https://www.dpc.casa/

Screen (1280px x 1680px)

1161 milliseconds

Screenshot Desktop - https://www.dpc.casa/

Mobile- and other Chrome-Checks

	width	height
visual Viewport	412	732
content Size	412	732

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://dpc.casa/ 8.17.89.134	301	https://dpc.casa/ Html is minified: 100.00 %	0.336	A
Date: Sat, 11 May 2024 23:03:28 GMT
Server: Apache
Location: https://dpc.casa/
Connection: close
Content-Length: 225
Content-Type: text/html; charset=iso-8859-1

• http://www.dpc.casa/ 8.17.89.134	301	https://www.dpc.casa/ Html is minified: 100.00 %	0.337	A
Date: Sat, 11 May 2024 23:03:28 GMT
Server: Apache
Location: https://www.dpc.casa/
Connection: close
Content-Length: 229
Content-Type: text/html; charset=iso-8859-1

• https://dpc.casa/ 8.17.89.134	301	https://www.dpc.casa/ Html is minified: 100.00 %	5.460	A
Date: Sat, 11 May 2024 23:03:29 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000
Location: https://www.dpc.casa/
Connection: close
Content-Length: 229
Content-Type: text/html; charset=iso-8859-1

• https://www.dpc.casa/ 8.17.89.134 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1180	200	Html is minified: 267.76 % Other inline scripts (∑/total): 0/0	5.244	A
Date: Sat, 11 May 2024 23:03:36 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000
Upgrade: h2, h2c
Connection: Upgrade, close
Cache-Control: no-store, must-revalidate, no-cache
Pragma: no-cache
Set-Cookie: PHPSESSID=d9d4tt1e19t8dsdefpg9tkrlqh; path=/; secure; httponly; SameSite=Lax
Vary: Accept-Encoding
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Content-Encoding: gzip
Content-Length: 806
Content-Type: text/html; charset=utf-8

• http://dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 8.17.89.134 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.340	A
Visible Content:
Date: Sat, 11 May 2024 23:03:41 GMT
Server: Apache
Location: https://dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 294
Content-Type: text/html; charset=iso-8859-1

• http://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 8.17.89.134 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.340	A
Visible Content:
Date: Sat, 11 May 2024 23:03:42 GMT
Server: Apache
Location: https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 298
Content-Type: text/html; charset=iso-8859-1

• https://dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	5.270	A
Visible Content:
Date: Sat, 11 May 2024 23:03:49 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000
Location: https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 298
Content-Type: text/html; charset=iso-8859-1

• https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	5.257	A
Not Found
Visible Content:
Date: Sat, 11 May 2024 23:03:55 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000
Upgrade: h2, h2c
Connection: Upgrade, close
Content-Length: 196
Content-Type: text/html; charset=UTF-8

• https://8.17.89.134/ 8.17.89.134 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	5.234	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Date: Sat, 11 May 2024 23:03:43 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000
Upgrade: h2, h2c
Connection: Upgrade, close
Cache-Control: no-store, must-revalidate, no-cache
Pragma: no-cache
Set-Cookie: PHPSESSID=9mijd2iffncj65r3crat7qu9fi; path=/; secure; httponly; SameSite=Lax
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Content-Length: 196
Content-Type: text/html; charset=utf-8

7. Comments

	1. General Results, most used to calculate the result
A	name "dpc.casa" is domain, public suffix is ".casa", top-level-domain is ".casa", top-level-domain-type is "generic", tld-manager is "Minds + Machines Group Limited", num .casa-domains preloaded: 26 (complete: 244198)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: dpc.casa has only one ip address.
	Warning: Only one ip address found: www.dpc.casa 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: dpc.casa 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.dpc.casa has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: www is preferred
A	Good: No cookie sent via http.
A	Good: every cookie sent via https is marked as secure
A	Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 63072000 seconds = 730 days
	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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
A	http://dpc.casa/ 8.17.89.134	301	https://dpc.casa/	Correct redirect http - https with the same domain name
A	http://www.dpc.casa/ 8.17.89.134	301	https://www.dpc.casa/	Correct redirect http - https with the same domain name
M	https://8.17.89.134/ 8.17.89.134	404		Misconfiguration - main pages should never send http status 400 - 499
N	https://8.17.89.134/ 8.17.89.134	404		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 dpc.casa, 1 ip addresses, 1 different http results.
	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 www.dpc.casa, 1 ip addresses, 1 different http results.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.dpc.casa
	2. Header-Checks
F	www.dpc.casa 8.17.89.134	Content-Security-Policy		Critical: Missing Header:
F	www.dpc.casa 8.17.89.134	X-Content-Type-Options		Critical: Missing Header:
F	www.dpc.casa 8.17.89.134	Referrer-Policy		Critical: Missing Header:
F	www.dpc.casa 8.17.89.134	Permissions-Policy		Critical: Missing Header:
	3. DNS- and NameServer - Checks
A	Info:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
A	Good: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
A	Good: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.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: dns1.registrar-servers.com, dns2.registrar-servers.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
A	Good: 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: registrar-servers.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: 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: c.nic.casa: OP100: ok. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns1.defra1). COOKIE: ok. CLIENTSUBNET: ok.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
	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://www.dpc.casa/ 8.17.89.134	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://www.dpc.casa/ 8.17.89.134	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://www.dpc.casa/ 8.17.89.134	200		Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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
	https://www.dpc.casa/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	5.257 seconds	Warning: 404 needs more then one second
	https://8.17.89.134/ 8.17.89.134	404	5.234 seconds	Warning: 404 needs more then one second
A	Duration: 309710 milliseconds, 309.710 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

dpc.casa

8.17.89.134

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

dpc.casa

8.17.89.134

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

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

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

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

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=dpc.casa
	2	CN=R3, O=Let's Encrypt, C=US

www.dpc.casa

8.17.89.134

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

www.dpc.casa

8.17.89.134

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

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

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

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

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=dpc.casa
	2	CN=R3, O=Let's Encrypt, C=US

dpc.casa

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

dpc.casa

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=dpc.casa
	2	CN=R3, O=Let's Encrypt, C=US

www.dpc.casa

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

www.dpc.casa

443

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

no http/2 via ALPN

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=dpc.casa
	2	CN=R3, O=Let's Encrypt, C=US

8.17.89.134

443

name does not match

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

8.17.89.134

443

name does not match

Tls12

ECDH Ephermal

255

Aes256

256

Sha384

not supported

no http/2 via ALPN
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

no http/2 via ALPN
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain (complete)	1	CN=dpc.casa
	2	CN=R3, O=Let's Encrypt, C=US

9. Certificates

CN=dpc.casa

13.03.2024

11.06.2024
607 days expired

dpc.casa, www.dpc.casa - 2 entries

CN=dpc.casa

13.03.2024

11.06.2024
607 days expired

dpc.casa, www.dpc.casa - 2 entries

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0482B9C387508F5E3303348C28301E237F8E
Thumbprint:	DD59B6D8C2EFDEDE45B1BB06D594D880CFBAF68F
SHA256 / Certificate:	0dzomnstzPQyxN7D2oFV6P2XTnTGYs5xz3QY0nPaiOY=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	4f1810e0291b78043e0d01f67fec297b1b5dbeea0ffca099e51444961517ba7f
SHA256 hex / Subject Public Key Information (SPKI):	4f1810e0291b78043e0d01f67fec297b1b5dbeea0ffca099e51444961517ba7f (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://r3.o.lencr.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=R3, O=Let's Encrypt, C=US

04.09.2020

15.09.2025
146 days expired

CN=R3, O=Let's Encrypt, C=US

04.09.2020

15.09.2025
146 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:	A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:	Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):	8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

CN=ISRG Root X1, O=Internet Security Research Group, C=US

04.06.2015

04.06.2035
expires in 3403 days

CN=ISRG Root X1, O=Internet Security Research Group, C=US

04.06.2015

04.06.2035
expires in 3403 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	008210CFB0D240E3594463E0BB63828B00
Thumbprint:	CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:	lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):	96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):	0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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)

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0	0	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6924156245 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-13 05:57:12	2024-06-11 05:57:11	dpc.casa, www.dpc.casa - 2 entries
6798037469 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-02-21 23:09:19	2024-05-21 23:09:18	*.dpc.casa, dpc.casa - 2 entries

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

Issuer				last 7 days	active	num Certs
CN=R3, O=Let's Encrypt, C=US				0 /0 new	0	6

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
12366097958 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-03-13 04:57:12	2024-06-11 03:57:11	dpc.casa, www.dpc.casa 2 entries
12151731355 precert	CN=R3, O=Let's Encrypt, C=US	2024-02-21 22:09:19	2024-05-21 21:09:18	*.dpc.casa, dpc.casa 2 entries
11819921879 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-21 09:17:13	2024-04-20 08:17:12	*.dpc.casa, dpc.casa 2 entries
11728251554 leaf cert	CN=R3, O=Let's Encrypt, C=US	2024-01-13 02:07:58	2024-04-12 01:07:57	dpc.casa, www.dpc.casa 2 entries
11198901770 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-11-23 18:32:42	2024-02-21 18:32:41	*.dpc.casa, dpc.casa 2 entries
11093828952 precert	CN=R3, O=Let's Encrypt, C=US	2023-11-14 01:50:50	2024-02-12 01:50:49	dpc.casa, www.dpc.casa 2 entries

11. Html-Content - Entries

Summary

							Subresource Integrity (SRI)
Domainname	HtmlElement	rel/property	∑	∑ size	∑ problems	∑ int.	∑ ext.	∑ Origin poss.	∑ SRI ParseErrors	∑ SRI valid	∑ SRI missing
https://www.dpc.casa/ 8.17.89.134	form		1		0			0	0	0
	meta	other	1		0			0	0	0

Details (currently limited to 500 rows - some problems with spam users)

Domainname	Html-Element	name/equiv/ property/rel	href/src/content
https://www.dpc.casa/ 8.17.89.134	form	post		1	ok
					ok


	meta	viewport	width=device-width, initial-scale=1.0	1	ok
					ok

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: dns1.registrar-servers.com, dns2.registrar-servers.com

QNr.	Domain	Type	NS used
1	com	NS	l.root-servers.net (2001:500:9f::42)
	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	dns1.registrar-servers.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
3	dns2.registrar-servers.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
4	edns4.registrar-servers.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: edns1.registrar-servers.com, edns2.registrar-servers.com, edns3.registrar-servers.com, edns4.registrar-servers.com, edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org
	Answer: edns1.registrar-servers.com 2001:41d0:800:2d2c::2, 51.89.217.44
	Answer: edns2.registrar-servers.com 2607:5300:203:7f53::2, 51.222.46.83
	Answer: edns3.registrar-servers.com 193.108.91.149, 2.16.130.65, 2600:1401:2::95, 2600:1480:9800::41, 2a02:26f0:67::43, 95.100.175.67
	Answer: edns4.ultradns.com 2001:502:f3ff::204, 204.74.66.4
5	biz	NS	k.root-servers.net (2001:7fd::1)
	Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, m.gtld.biz, n.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
6	edns4.ultradns.biz	NS	a.gtld.biz (2001:502:ad09::30)
	Answer: pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.biz 156.154.66.196, 2610:a1:1015::e8
7	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
8	edns4.ultradns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: pdns196.ultradns.net 156.154.65.196, 2610:a1:1014::e8
9	org	NS	f.root-servers.net (2001:500:2f::f)
	Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
10	edns4.ultradns.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: ns61.ultradns2.com, ns61.ultradns2.org, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org
	Answer: ns61.ultradns2.org 204.74.106.61, 2610:a1:323d::53
	Answer: pdns196.ultradns.org 156.154.67.196, 2001:502:4612::e8
11	uk	NS	b.root-servers.net (2001:500:200::b)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
12	pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8	NS	dns1.nic.uk (2a01:618:400::1)
13	pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns61.ultradns2.com 204.74.104.61, 2610:a1:313d::53
14	info	NS	a.root-servers.net (2001:503:ba3e::2:30)
	Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
15	pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8	NS	a0.info.afilias-nst.info (2001:500:19::1)
16	edns4.registrar-servers.com: 2.22.230.67, 23.211.132.64, 96.7.49.64	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
17	edns4.registrar-servers.com: 2600:1406:1b::40, 2600:1408:1c::40, 2600:1480:800::43	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
18	edns4.ultradns.biz: 204.74.67.4	A	pdns196.ultradns.biz (2610:a1:1015::e8)
19	edns4.ultradns.biz: 2610:a1:1015::204	AAAA	pdns196.ultradns.biz (2610:a1:1015::e8)
20	edns4.ultradns.net: 204.74.110.4	A	ns61.ultradns2.com (2610:a1:313d::53)
21	edns4.ultradns.net: 2610:a1:1014::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
22	edns4.ultradns.org: 204.74.111.4	A	ns61.ultradns2.com (2610:a1:313d::53)
23	edns4.ultradns.org: 2001:502:4612::204	AAAA	ns61.ultradns2.com (2610:a1:313d::53)
24	dns1.registrar-servers.com: 156.154.132.200	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
25	dns1.registrar-servers.com: 2610:a1:1024::200	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
26	dns2.registrar-servers.com: 156.154.133.200	A	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)
27	dns2.registrar-servers.com: 2610:a1:1025::200	AAAA	edns1.registrar-servers.com (2001:41d0:800:2d2c::2)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries
www.dpc.casa	0		no CAA entry found	1
dpc.casa	9	issuewild	letsencrypt.org	1
casa	0		no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
dpc.casa	ok	1
www.dpc.casa	ok	1
_acme-challenge.dpc.casa	Name Error - The domain name does not exist	1
_acme-challenge.www.dpc.casa	Name Error - The domain name does not exist	1
_acme-challenge.dpc.casa.dpc.casa	Name Error - The domain name does not exist	1
_acme-challenge.www.dpc.casa.dpc.casa	Name Error - The domain name does not exist	1
_acme-challenge.www.dpc.casa.www.dpc.casa	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

Summary
Domain	IP	Port	num Ciphers	time	Std.Protocol	Forward Secrecy
dpc.casa	8.17.89.134	443	5 Ciphers	91.54 sec		0 without, 5 FS	100.00 %
www.dpc.casa	8.17.89.134	443	5 Ciphers	91.34 sec		0 without, 5 FS	100.00 %
Complete		2	10 Ciphers 5.00 Ciphers/Check	182.88 sec	91.44 sec/Check	0 without, 10 FS	100.00 %

Details
Domain	IP	Port	Cipher (OpenSsl / IANA)
dpc.casa	8.17.89.134	443	ECDHE-RSA-CHACHA20-POLY1305		(Secure)	TLSv1.2	0xCC,0xA8	FS
5 Ciphers, 91.54 sec			TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
			ECDH		RSA	CHACHA20/POLY1305(256)	AEAD
			ECDHE-RSA-AES256-GCM-SHA384		(Secure)	TLSv1.2	0xC0,0x30	FS
			TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
			ECDH		RSA	AESGCM(256)	AEAD
			DHE-RSA-AES256-GCM-SHA384		(Secure)	TLSv1.2	0x00,0x9F	FS
			TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
			DH		RSA	AESGCM(256)	AEAD
			ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
www.dpc.casa	8.17.89.134	443	ECDHE-RSA-CHACHA20-POLY1305		(Secure)	TLSv1.2	0xCC,0xA8	FS
5 Ciphers, 91.34 sec			TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
			ECDH		RSA	CHACHA20/POLY1305(256)	AEAD
			ECDHE-RSA-AES256-GCM-SHA384		(Secure)	TLSv1.2	0xC0,0x30	FS
			TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
			ECDH		RSA	AESGCM(256)	AEAD
			DHE-RSA-AES256-GCM-SHA384		(Secure)	TLSv1.2	0x00,0x9F	FS
			TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
			DH		RSA	AESGCM(256)	AEAD
			ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=375ea0b8-57d5-4ebf-8ac0-6828f204c02c

Last Result: https://check-your-website.server-daten.de/?q=dpc.casa - 2024-05-12 01:02:56

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

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

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

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 (currently limited to 500 rows - some problems with spam users)

12. Html-Parsing via https://validator.w3.org/nu/

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks