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

0 in Queue, 0 of max. 8 Checks (02:53:17)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

R

 

Redirect to not existing domain

 

Checked:
28.07.2024 19:48:07

 

Older results

 

A+ - 14.09.2019 00:23:20

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
test.support
A
3.233.108.250
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.
Hostname: ec2-3-233-108-250.compute-1.amazonaws.com
yes
1
0

A
3.233.187.46
Ashburn/Virginia/United States (US) - Amazon Technologies Inc.
Hostname: ec2-3-233-187-46.compute-1.amazonaws.com
yes
1
0

A
54.157.2.211
Ashburn/Virginia/United States (US) - Amazon.com, Inc.
Hostname: ec2-54-157-2-211.compute-1.amazonaws.com
yes
1
0

AAAA

yes


www.test.support

Name Error
yes
1
0
*.test.support
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 20038, 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: 11.08.2024, 00:00:00 +, Signature-Inception: 21.07.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: support

support
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 59704, DigestType 2 and Digest XHiRCPiNNwpW4cYWxCaUpJL6Cz7Xyvt/lWV3fhuFrZY=






1 RRSIG RR to validate DS RR found






RRSIG-Owner support., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 10.08.2024, 05:00:00 +, Signature-Inception: 28.07.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 19701, Flags 256






Public Key with Algorithm 8, KeyTag 50331, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner support., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 15.08.2024, 15:40:36 +, Signature-Inception: 25.07.2024, 14:40:36 +, KeyTag 59704, Signer-Name: support






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






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



Zone: test.support

test.support
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 8647, DigestType 2 and Digest g3EZexlWSiRseguULPcFNFqPp7JK/IVk5YuIKV4VLSU=






1 RRSIG RR to validate DS RR found






RRSIG-Owner test.support., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.08.2024, 15:40:36 +, Signature-Inception: 25.07.2024, 14:40:36 +, KeyTag 50331, Signer-Name: support






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 36373, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner test.support., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 8647, Signer-Name: test.support






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






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






RRSIG Type 1 validates the A - Result: 3.233.108.250 3.233.187.46 54.157.2.211
Validated: RRSIG-Owner test.support., Algorithm: 8, 2 Labels, original TTL: 14400 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






RRSIG Type 16 validates the TXT - Result: v=spf1 mx a:mail.test.support ~all
Validated: RRSIG-Owner test.support., Algorithm: 8, 2 Labels, original TTL: 14400 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" equal the hashed NSEC3-owner "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" and the hashed NextOwner "2dcvkth1a8ddehi5h64j3omnn3buuif1". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 1d5l0j9lkcp25bdh02hk0qdv9dncj9br.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" equal the hashed NSEC3-owner "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" and the hashed NextOwner "2dcvkth1a8ddehi5h64j3omnn3buuif1". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 1d5l0j9lkcp25bdh02hk0qdv9dncj9br.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.test.support) sends a valid NSEC3 RR as result with the hashed owner name "8gtv49ij3gcea8jvl0j8t3mtrbe7pr9g" (unhashed: _tcp.test.support). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner 8gtv49ij3gcea8jvl0j8t3mtrbe7pr9g.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






Status: Good. NXDomain-Proof required and found.






TLSA-Query (_443._tcp.test.support) sends a valid NSEC3 RR as result with the hashed query name "mppdvegk9o6995kjd9udb8oulsm8cfnn" between the hashed NSEC3-owner "lcr04g9fjanu7aj8qjjae3fujg3743mg" and the hashed NextOwner "p1h68p3mkkjdu0o77m1ebhp40mf45qo7". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner lcr04g9fjanu7aj8qjjae3fujg3743mg.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






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 "9q6ngvnp12oka10mgs67h2ajikl6buoq" (unhashed: *._tcp.test.support) with the owner "8leg3t7orq1pi3sg7aipnelthj5hd0gu" and the NextOwner "d4mh4f966oc2j2eduqovb1a2o4ck4emc". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 8leg3t7orq1pi3sg7aipnelthj5hd0gu.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" equal the hashed NSEC3-owner "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" and the hashed NextOwner "2dcvkth1a8ddehi5h64j3omnn3buuif1". 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, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 1d5l0j9lkcp25bdh02hk0qdv9dncj9br.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






Status: Good. NoData-Proof required and found.



Zone: www.test.support

www.test.support
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 "j6n12q7qfm1na59d4lkq1n9jba9g3pic" between the hashed NSEC3-owner "j3adi6s7er923ci6cdgfmjfa3h954jub" and the hashed NextOwner "jnreotu6joni9l531h7id986qoql45i7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner j3adi6s7er923ci6cdgfmjfa3h954jub.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "1d5l0j9lkcp25bdh02hk0qdv9dncj9br" as Owner. That's the Hash of "test.support" with the NextHashedOwnerName "2dcvkth1a8ddehi5h64j3omnn3buuif1". So that domain name is the Closest Encloser of "www.test.support". Opt-Out: False.
Bitmap: A, NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 1d5l0j9lkcp25bdh02hk0qdv9dncj9br.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support






The ClosestEncloser says, that "*.test.support" with the Hash "itqk00iihp504mj6fi058eup7l36drri" 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 "iji52u34e1f8nv1nu0sba11ed9c7jief" and the Next Owner "j3adi6s7er923ci6cdgfmjfa3h954jub", 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: TXT, RRSIG Validated: RRSIG-Owner iji52u34e1f8nv1nu0sba11ed9c7jief.test.support., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.08.2024, 02:44:51 +, Signature-Inception: 27.07.2024, 02:44:51 +, KeyTag 36373, Signer-Name: test.support

 

3. Name Servers

DomainNameserverNS-IP
www.test.support
•  ns-cloud-e1.googledomains.com

test.support
•  ns-cloud-e1.googledomains.com
216.239.32.110
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:32::6e
Mountain View/California/United States (US) - Google LLC		•

•  ns-cloud-e2.googledomains.com
216.239.34.110
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:34::6e
Mountain View/California/United States (US) - Google LLC		•

•  ns-cloud-e3.googledomains.com
216.239.36.110
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:36::6e
Mountain View/California/United States (US) - Google LLC		•

•  ns-cloud-e4.googledomains.com
216.239.38.110
Mountain View/California/United States (US) - Google LLC		•

• 
2001:4860:4802:38::6e
Mountain View/California/United States (US) - Google LLC		•
support
•  v0n0.nic.support / app10.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861
•

•  v0n1.nic.support / app8.lax1.hosts.meta.redstone.afilias-nst.info-1633102198
•

•  v0n2.nic.support / app27.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861
•

•  v0n3.nic.support / cdg1.micro.hosts.meta.redstone.afilias-nst.info-1717104402
•

•  v2n0.nic.support / FRA5
•

•  v2n1.nic.support / FRA5
•

 

4. SOA-Entries


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


Domain:test.support
Zone-Name:test.support
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:64
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.test.support
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://test.support/
3.233.108.250
301
https://test.support/

0.216
A
Location: https://test.support/
Date: Sun, 28 Jul 2024 17:49:10 GMT
Server: envoy
Connection: close
Content-Length: 0

• http://test.support/
3.233.187.46
301
https://test.support/

0.223
A
Location: https://test.support/
Date: Sun, 28 Jul 2024 17:49:11 GMT
Server: envoy
Connection: close
Content-Length: 0

• http://test.support/
54.157.2.211
301
https://test.support/

0.223
A
Location: https://test.support/
Date: Sun, 28 Jul 2024 17:49:11 GMT
Server: envoy
Connection: close
Content-Length: 0

• https://test.support/
3.233.108.250
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening

4.230
N
Certificate error: RemoteCertificateChainErrors
Date: Sun, 28 Jul 2024 17:49:12 GMT
Location: https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
x-envoy-upstream-service-time: 11
Server: envoy
Connection: close
Content-Length: 0

• https://test.support/
3.233.187.46
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening

4.063
N
Certificate error: RemoteCertificateChainErrors
Date: Sun, 28 Jul 2024 17:49:17 GMT
Location: https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
x-envoy-upstream-service-time: 8
Server: envoy
Connection: close
Content-Length: 0

• https://test.support/
54.157.2.211
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening

4.097
N
Certificate error: RemoteCertificateChainErrors
Date: Sun, 28 Jul 2024 17:49:22 GMT
Location: https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
x-envoy-upstream-service-time: 1
Server: envoy
Connection: close
Content-Length: 0

• https://www.twilio.com/docs/messaging/how-to-configure-link-shortening

301
https://www.test.support/docs/messaging/features/link-shortening/onboarding-guide
Html is minified: 100.00 %
3.060
A
Transfer-Encoding: chunked
Connection: close
Cache-Control: public, must-revalidate, max-age=0
X-Vercel-Id: fra1::4wsfk-1722188970262-3245436cb877
Date: Sun, 28 Jul 2024 17:49:30 GMT
Location: /docs/messaging/features/link-shortening/onboarding-guide
Server: Vercel
Set-Cookie: __Host-authjs.csrf-token=b477c491c332dbff0a7304e501245336e5016a26a04e1f9716d7dff855cf0d13%7C271074a820c08d578a9a1707672c320a536ca5297763825d4e464400b3260ad0; Path=/; HttpOnly; Secure; SameSite=Lax, __Secure-authjs.callback-url=https%3A%2F%2Fwww.twilio.com; Path=/; HttpOnly; Secure; SameSite=Lax
Strict-Transport-Security: max-age=63072000
X-Cache: Miss from cloudfront
Via: 1.1 cd23c1917193b2e0c41e6fae756e0912.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: TXL50-P1
X-Amz-Cf-Id: 4yQdS8OPvtZv7UuhQjCXqo2l13Q9VudhvDUNVCO2jNNsQggoTSKHGQ==
Content-Type: text/plain

• https://www.test.support/docs/messaging/features/link-shortening/onboarding-guide

-1


0.013
R
NameResolutionFailure - Der angegebene Host ist unbekannt. (www.test.support:443)

• http://test.support/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.233.108.250
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 100.47 %
Other inline scripts (∑/total): 0/0		0.227
A
Not Found
Visible Content:
Cache-Control: no-store, must-revalidate, no-cache
x-envoy-upstream-service-time: 6
Date: Sun, 28 Jul 2024 17:49:26 GMT
Server: envoy
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 426

• http://test.support/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.233.187.46
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 100.47 %
Other inline scripts (∑/total): 0/0		0.234
A
Not Found
Visible Content:
Cache-Control: no-store, must-revalidate, no-cache
x-envoy-upstream-service-time: 5
Date: Sun, 28 Jul 2024 17:49:27 GMT
Server: envoy
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 426

• http://test.support/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
54.157.2.211
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 100.47 %
Other inline scripts (∑/total): 0/0		0.230
A
Not Found
Visible Content:
Cache-Control: no-store, must-revalidate, no-cache
x-envoy-upstream-service-time: 4
Date: Sun, 28 Jul 2024 17:49:28 GMT
Server: envoy
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 426

• https://3.233.187.46/
3.233.187.46
-16


0.237
P
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

• https://54.157.2.211/
54.157.2.211
-16


0.237
P
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

• https://3.233.108.250/
3.233.108.250
-16


0.227
P
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

 

7. Comments


1. General Results, most used to calculate the result

Aname "test.support" is domain, public suffix is ".support", top-level-domain is ".support", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .support-domains preloaded: 34 (complete: 245733)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: test.support has 3 different ip addresses (authoritative).
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: test.support has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: No cookie sent via http.
AGood: every cookie sent via https is marked as secure
AGood: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None
AExcellent: Domain is in the Google-Preload-List
AExcellent: Domain is in the Mozilla/Firefox-Preload-List
HSTS-Preload-Status: Removed. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://test.support/ 3.233.108.250
301
https://test.support/
Correct redirect http - https with the same domain name
Ahttp://test.support/ 3.233.187.46
301
https://test.support/
Correct redirect http - https with the same domain name
Ahttp://test.support/ 54.157.2.211
301
https://test.support/
Correct redirect http - https with the same domain name
Bhttps://test.support/ 3.233.108.250
307

Missing HSTS-Header
Bhttps://test.support/ 3.233.187.46
307

Missing HSTS-Header
Bhttps://test.support/ 54.157.2.211
307

Missing HSTS-Header
CError - no version with Http-Status 200
HFatal error: No https - result with http-status 200, no encryption
Nhttps://test.support/ 3.233.108.250
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://test.support/ 3.233.187.46
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://test.support/ 54.157.2.211
307
https://www.twilio.com/docs/messaging/how-to-configure-link-shortening
Error - Certificate isn't trusted, RemoteCertificateChainErrors
Otest.support / 3.233.108.250 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 2 Cipher Suites without Forward Secrecy found
Otest.support / 3.233.187.46 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 2 Cipher Suites without Forward Secrecy found
Otest.support / 54.157.2.211 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 2 Cipher Suites without Forward Secrecy found
Rhttps://www.twilio.com/docs/messaging/how-to-configure-link-shortening
301
https://www.test.support/docs/messaging/features/link-shortening/onboarding-guide
Redirect to not existing domain
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain test.support, 3 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 test.support, 3 ip addresses.
BNo _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.test.support

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: 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.
AInfo:: 4 different Name Servers found: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-e1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-e1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-e1.googledomains.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: 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
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
AInfo: 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.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: 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:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-cloud-e1.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.
Nameserver doesn't pass all EDNS-Checks: v0n3.nic.support: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (cdg1.micro.hosts.meta.redstone.afilias-nst.info-1717104402). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: 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.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
AInfo: Different Server-Headers found
ADuration: 348374 milliseconds, 348.374 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
test.support
3.233.108.250
443
Certificate/chain invalid
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
test.support
3.233.108.250
443
Certificate/chain invalid
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=test.support


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


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


test.support
3.233.187.46
443
Certificate/chain invalid
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

test.support
3.233.187.46
443
Certificate/chain invalid
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=test.support


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


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


test.support
54.157.2.211
443
Certificate/chain invalid
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

test.support
54.157.2.211
443
Certificate/chain invalid
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=test.support


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


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


www.twilio.com
www.twilio.com
443
ok
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
supported
ok

www.twilio.com
www.twilio.com
443
ok
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - too much certificates, don't send root certificates

1CN=*.twilio.com


2CN=Amazon RSA 2048 M03, O=Amazon, C=US


3CN=Amazon Root CA 1, O=Amazon, C=US


4CN=Starfield Services Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, C=US, ST=Arizona

 

9. Certificates

1.
1.
CN=test.support
17.05.2023
15.08.2023
640 days expired		test.support - 1 entry
1.
1.
CN=test.support
17.05.2023

15.08.2023
640 days expired


test.support - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03E798A617C67715AE6041F84DF0E14EB3DD
Thumbprint:137579E8C5DEE6B10DA28A193E32E448D9E04B39
SHA256 / Certificate:c5Wx5miYmAGJR5EuOtaRk8sBO0o7C1hX+68LEjQgkgU=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):ab5f5763cfc31b4dca70aa64d993ae559d9025ffd03ac4e67b761573241fd886
SHA256 hex / Subject Public Key Information (SPKI):ab5f5763cfc31b4dca70aa64d993ae559d9025ffd03ac4e67b761573241fd886 (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)


NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.


2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 122 days

2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 122 days




KeyalgorithmRSA 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)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3671 days

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

04.06.2035
expires in 3671 days




KeyalgorithmRSA 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:




2.
1.
CN=*.twilio.com
14.04.2024
14.05.2025
2 days expired		*.twilio.com, twilio.jp, twilio.com, *.twilio.jp - 4 entries
2.
1.
CN=*.twilio.com
14.04.2024

14.05.2025
2 days expired


*.twilio.com, twilio.jp, twilio.com, *.twilio.jp - 4 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:08D10E55E0476D0476C6295F6B44C5E1
Thumbprint:A8FAF7290036F718367D183FFEA9051B31CEB444
SHA256 / Certificate:SeFQ5Pelubt46wt47T45iY0KV3TBCxf4OKx9WlGCkdE=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2eefc7f482a69cb6a0ae599f3dc89e3e31bcc4b733a1b2c6aec799444536cb75
SHA256 hex / Subject Public Key Information (SPKI):2eefc7f482a69cb6a0ae599f3dc89e3e31bcc4b733a1b2c6aec799444536cb75 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.r2m03.amazontrust.com
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)




2.
CN=*.twilio.com
14.04.2024
14.05.2025
2 days expired		*.twilio.com, twilio.jp, twilio.com, *.twilio.jp - 4 entries

2.
CN=*.twilio.com
14.04.2024

14.05.2025
2 days expired


*.twilio.com, twilio.jp, twilio.com, *.twilio.jp - 4 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:08D10E55E0476D0476C6295F6B44C5E1
Thumbprint:A8FAF7290036F718367D183FFEA9051B31CEB444
SHA256 / Certificate:SeFQ5Pelubt46wt47T45iY0KV3TBCxf4OKx9WlGCkdE=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2eefc7f482a69cb6a0ae599f3dc89e3e31bcc4b733a1b2c6aec799444536cb75
SHA256 hex / Subject Public Key Information (SPKI):2eefc7f482a69cb6a0ae599f3dc89e3e31bcc4b733a1b2c6aec799444536cb75 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.r2m03.amazontrust.com
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)




3.
CN=Amazon RSA 2048 M03, O=Amazon, C=US
24.08.2022
24.08.2030
expires in 1926 days

3.
CN=Amazon RSA 2048 M03, O=Amazon, C=US
24.08.2022

24.08.2030
expires in 1926 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0773124CD406D267C0991CDD299A9F38317985
Thumbprint:D9FE0A65FA00CABF61F5120D373A8135E1461F15
SHA256 / Certificate:v4ppAnvMjS1CpubSW91Ic/ajS4+Q7fB+hsXWkW2guTM=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):bf14689ff125e4ab88e2fc797b2d43826b189916349c37790a0e067c9f12f9b8
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.rootca1.amazontrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




4.
CN=Amazon RSA 2048 M03, O=Amazon, C=US
24.08.2022
24.08.2030
expires in 1926 days

4.
CN=Amazon RSA 2048 M03, O=Amazon, C=US
24.08.2022

24.08.2030
expires in 1926 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0773124CD406D267C0991CDD299A9F38317985
Thumbprint:D9FE0A65FA00CABF61F5120D373A8135E1461F15
SHA256 / Certificate:v4ppAnvMjS1CpubSW91Ic/ajS4+Q7fB+hsXWkW2guTM=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):bf14689ff125e4ab88e2fc797b2d43826b189916349c37790a0e067c9f12f9b8
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.rootca1.amazontrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




5.
CN=Amazon Root CA 1, O=Amazon, C=US
25.05.2015
31.12.2037
expires in 4612 days

5.
CN=Amazon Root CA 1, O=Amazon, C=US
25.05.2015

31.12.2037
expires in 4612 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:067F944A2A27CDF3FAC2AE2B01F908EEB9C4C6
Thumbprint:06B25927C42A721631C1EFD9431E648FA62E1E39
SHA256 / Certificate:h9zU3HRkCjIs0gVVJQbRvmTxJZYlgJZUSYa0hQvHJwY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):fbe3018031f9586bcbf41727e417b7d1c45c2f47f93be372a17b96b50757d5a2
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.rootg2.amazontrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




6.
CN=Amazon Root CA 1, O=Amazon, C=US
25.05.2015
31.12.2037
expires in 4612 days

6.
CN=Amazon Root CA 1, O=Amazon, C=US
25.05.2015

31.12.2037
expires in 4612 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:067F944A2A27CDF3FAC2AE2B01F908EEB9C4C6
Thumbprint:06B25927C42A721631C1EFD9431E648FA62E1E39
SHA256 / Certificate:h9zU3HRkCjIs0gVVJQbRvmTxJZYlgJZUSYa0hQvHJwY=
SHA256 hex / Cert (DANE * 0 1):87dcd4dc74640a322cd205552506d1be64f12596258096544986b4850bc72706
SHA256 hex / PublicKey (DANE * 1 1):fbe3018031f9586bcbf41727e417b7d1c45c2f47f93be372a17b96b50757d5a2
SHA256 hex / Subject Public Key Information (SPKI):fbe3018031f9586bcbf41727e417b7d1c45c2f47f93be372a17b96b50757d5a2
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.rootg2.amazontrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




7.
CN=Starfield Services Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.09.2009
01.01.2038
expires in 4613 days

7.
CN=Starfield Services Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.09.2009

01.01.2038
expires in 4613 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00
Thumbprint:925A8F8D2C6D04E0665F596AFF22D863E8256F3F
SHA256 / Certificate:Vo1pBaLIhwikswJRkO3P7bGXSmBqE8blKQ/LKuY+2rU=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):2b071c59a0a0ae76b0eadb2bad23bad4580b69c3601b630c2eaf0613afa83f92
SHA256 hex / Subject Public Key Information (SPKI):
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:





8.
CN=Starfield Services Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
02.09.2009
28.06.2034
expires in 3330 days

8.
CN=Starfield Services Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
02.09.2009

28.06.2034
expires in 3330 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00A70E4A4C3482B77F
Thumbprint:9E99A48A9960B14926BB7F3B02E22DA2B0AB7280
SHA256 / Certificate:KGibMOTDBqq1OwJ7KeNq1t0dz0uVOZRILKhL3B7KyZY=
SHA256 hex / Cert (DANE * 0 1):28689b30e4c306aab53b027b29e36ad6dd1dcf4b953994482ca84bdc1ecac996
SHA256 hex / PublicKey (DANE * 1 1):2b071c59a0a0ae76b0eadb2bad23bad4580b69c3601b630c2eaf0613afa83f92
SHA256 hex / Subject Public Key Information (SPKI):2b071c59a0a0ae76b0eadb2bad23bad4580b69c3601b630c2eaf0613afa83f92
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://o.ss2.us/
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

No CRT - CT-Log entries found

 

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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

 

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns-cloud-e1.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-e2.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-e3.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-e4.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-e1.googledomains.com: 216.239.32.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-e2.googledomains.com: 216.239.34.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-e3.googledomains.com: 216.239.36.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-e4.googledomains.com: 216.239.38.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
test.support
0

no CAA entry found
1
0
support
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
test.support
v=spf1 mx a:mail.test.support ~all
ok
1
0
_acme-challenge.test.support
dCDbWU9QUCh52VNqbfBfwdyVwtr-YdojgrqutABxbRM
looks good, correct length, correct characters
1
0
_acme-challenge.test.support.test.support

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
SPF
TXT
test.support

v=spf1 mx a:mail.test.support ~all
ok

MX
test.support

128PermError: Domainname defined, but no MX entry found.

A
mail.test.support

no A entry found
ok
_dmarc
TXT
_dmarc.test.support

v=DMARC1; p=reject; rua=mailto:admin@test.support; ruf=mailto:admin@test.support; adkim=s; aspf=s
ok

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
test.support
3.233.108.250
443
6 Ciphers70.34 sec
2 without, 4 FS
66.67 %
test.support
3.233.187.46
443
6 Ciphers71.84 sec
2 without, 4 FS
66.67 %
test.support
54.157.2.211
443
6 Ciphers71.45 sec
2 without, 4 FS
66.67 %
Complete

3
18 Ciphers
6.00 Ciphers/Check		213.63 sec71.21 sec/Check
6 without, 12 FS
66.67 %

Details
DomainIPPortCipher (OpenSsl / IANA)
test.support
3.233.108.250
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
6 Ciphers, 

70.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




ECDHE-RSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x14
 FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

ECDH
RSA
AES(256)
SHA1




ECDHE-RSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x13
 FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

ECDH
RSA
AES(128)
SHA1




AES256-SHA
 (Weak)
SSLv3
0x00,0x35
 No FS

TLS_RSA_WITH_AES_256_CBC_SHA

RSA
RSA
AES(256)
SHA1




AES128-SHA
 (Weak)
SSLv3
0x00,0x2F
 No FS

TLS_RSA_WITH_AES_128_CBC_SHA

RSA
RSA
AES(128)
SHA1


3.233.187.46
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
6 Ciphers, 

71.84 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




ECDHE-RSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x14
 FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

ECDH
RSA
AES(256)
SHA1




ECDHE-RSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x13
 FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

ECDH
RSA
AES(128)
SHA1




AES256-SHA
 (Weak)
SSLv3
0x00,0x35
 No FS

TLS_RSA_WITH_AES_256_CBC_SHA

RSA
RSA
AES(256)
SHA1




AES128-SHA
 (Weak)
SSLv3
0x00,0x2F
 No FS

TLS_RSA_WITH_AES_128_CBC_SHA

RSA
RSA
AES(128)
SHA1


54.157.2.211
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
6 Ciphers, 

71.45 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




ECDHE-RSA-AES256-SHA
 (Weak)
TLSv1
0xC0,0x14
 FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

ECDH
RSA
AES(256)
SHA1




ECDHE-RSA-AES128-SHA
 (Weak)
TLSv1
0xC0,0x13
 FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

ECDH
RSA
AES(128)
SHA1




AES256-SHA
 (Weak)
SSLv3
0x00,0x35
 No FS

TLS_RSA_WITH_AES_256_CBC_SHA

RSA
RSA
AES(256)
SHA1




AES128-SHA
 (Weak)
SSLv3
0x00,0x2F
 No FS

TLS_RSA_WITH_AES_128_CBC_SHA

RSA
RSA
AES(128)
SHA1


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=1c05c995-f1ff-40f3-bb7f-74ceee1d78cd

				 
			


Last Result: https://check-your-website.server-daten.de/?q=test.support - 2024-07-28 19:48:07

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

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

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions