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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
29.06.2026 19:41:31

Older results

A - 29.06.2026 19:13:37

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
cdn.studio.f5.com	CNAME	cdn.sanity-host.com	yes	1	0
	A	34.149.250.58 Kansas City/Missouri/United States (US) - Google LLC Hostname: 58.250.149.34.bc.googleusercontent.com	yes
www.cdn.studio.f5.com		Name Error	yes	1	0
*.studio.f5.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.cdn.studio.f5.com	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 54393, Flags 256


	Public Key with Algorithm 8, KeyTag 57780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2026, 00:00:00 +, Signature-Inception: 20.06.2026, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	2 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 27677, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.07.2026, 14:02:35 +, Signature-Inception: 26.06.2026, 13:57:35 +, KeyTag 19718, Signer-Name: com


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


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

Zone: f5.com
f5.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "4re5vmhjchitu844stgl0hb9qu3b2303" between the hashed NSEC3-owner "4re5v11aq3m9t44evlghjfn60bpjejfg" and the hashed NextOwner "4re63sjdspk1infrpk8kvjbouv02q3b7". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 4re5v11aq3m9t44evlghjfn60bpjejfg.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.07.2026, 02:44:28 +, Signature-Inception: 26.06.2026, 01:34:28 +, KeyTag 27677, Signer-Name: com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "f5.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 05.07.2026, 00:26:25 +, Signature-Inception: 27.06.2026, 23:16:25 +, KeyTag 27677, Signer-Name: com


	0 DNSKEY RR found




Zone: studio.f5.com
studio.f5.com	0 DS RR in the parent zone found

Zone: cdn.studio.f5.com
cdn.studio.f5.com	0 DS RR in the parent zone found

Zone: www.cdn.studio.f5.com
www.cdn.studio.f5.com	0 DS RR in the parent zone found

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 54393, Flags 256


	Public Key with Algorithm 8, KeyTag 57780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.07.2026, 00:00:00 +, Signature-Inception: 20.06.2026, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	2 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 27677, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.07.2026, 14:02:35 +, Signature-Inception: 26.06.2026, 13:57:35 +, KeyTag 19718, Signer-Name: com


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


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

Zone: sanity-host.com
sanity-host.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "vsrn1sgqekm2brp1njd4fqk25u03h69t" between the hashed NSEC3-owner "vsrmvm3b9huigu4ie88seu5igv6tfsna" and the hashed NextOwner "vsrnen4qtglcp95c0lvmlg86aclkrp6g". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vsrmvm3b9huigu4ie88seu5igv6tfsna.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 06.07.2026, 00:55:48 +, Signature-Inception: 28.06.2026, 23:45:48 +, KeyTag 27677, Signer-Name: com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "sanity-host.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 05.07.2026, 00:26:25 +, Signature-Inception: 27.06.2026, 23:16:25 +, KeyTag 27677, Signer-Name: com


	0 DNSKEY RR found




Zone: cdn.sanity-host.com
cdn.sanity-host.com	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 54393, Flags 256


	Public Key with Algorithm 8, KeyTag 57780, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 57355, DigestType 2 and Digest laV8O6t4SdvN33xyracaiBRrFBEQMYylvmcgV+hlw+I=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.07.2026, 05:00:00 +, Signature-Inception: 29.06.2026, 04:00:00 +, KeyTag 54393, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 7704, Flags 256


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


	Public Key with Algorithm 8, KeyTag 65493, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner io., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 16.07.2026, 15:56:26 +, Signature-Inception: 25.06.2026, 14:56:26 +, KeyTag 57355, Signer-Name: io


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


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

Zone: ves.io
ves.io	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 5930, DigestType 2 and Digest /nHMJIePBuoHMt1xk4HKQ68ja+/SNuivc6gB/u1JXuk=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ves.io., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.07.2026, 15:56:26 +, Signature-Inception: 25.06.2026, 14:56:26 +, KeyTag 7704, Signer-Name: io


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 42094, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ves.io., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 20.07.2026, 13:10:25 +, Signature-Inception: 28.06.2026, 13:10:25 +, KeyTag 5930, Signer-Name: ves.io


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


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

Zone: vh.ves.io
vh.ves.io	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 "gvqpsu2ie3gbr8om26r1lbt45ama5h0l" between the hashed NSEC3-owner "gvqpsu2ie3gbr8om26r1lbt45ama5h0l" and the hashed NextOwner "h4gvshojnhakndam3l8bp32i5d8l3d3p". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner gvqpsu2ie3gbr8om26r1lbt45ama5h0l.ves.io., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.07.2026, 13:10:25 +, Signature-Inception: 28.06.2026, 13:10:25 +, KeyTag 42094, Signer-Name: ves.io


	0 DNSKEY RR found




Zone: ac.vh.ves.io
ac.vh.ves.io	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 "8ba7de5l6g5h039786btle3ilku94prl" between the hashed NSEC3-owner "8ba7de5l6g5h039786btle3ilku94prl" and the hashed NextOwner "8joievugretuegirssnsdqdebcru44q8". So the parent zone confirmes the not-existence of a DS RR. Bitmap: No Bitmap? Validated: RRSIG-Owner 8ba7de5l6g5h039786btle3ilku94prl.ves.io., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 20.07.2026, 13:10:25 +, Signature-Inception: 28.06.2026, 13:10:25 +, KeyTag 42094, Signer-Name: ves.io


	0 DNSKEY RR found




Zone: ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io
ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io	0 DS RR in the parent zone found


	0 DNSKEY RR found

3. Name Servers

Domain	Nameserver	NS-IP
www.cdn.studio.f5.com	• pdns130.f5.com
f5.com	• pdns130.f5.com	104.219.104.131 Seattle/Washington/United States (US) - F5 Networks, Inc.	•
	T	2620:0:c12:f5f5:1::c3 Seattle/Washington/United States (US) - SEA-HQ	•
	T pdns131.f5.com	104.219.105.131 Seattle/Washington/United States (US) - F5 Networks, Inc.	•
	•	2620:0:c13:f5f5:1::c3 Seattle/Washington/United States (US) - SEA-HQ	•
	• pdns150.f5.com	104.219.106.131 Seattle/Washington/United States (US) - F5 Networks, Inc.	•
	•	2620:0:c14:f5f5:1::c3 Seattle/Washington/United States (US) - SEA-HQ	•
	• pdns151.f5.com	104.219.107.131 San Jose/California/United States (US) - F5 Networks, Inc.	•
	•	2620:0:c15:f5f5:1::c3 Seattle/Washington/United States (US) - SEA-HQ	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-defra-5		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-ein2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io	• ns-1673.awsdns-17.co.uk / 4c17a6fb9eefabf7052aea32d70e3ecb -	205.251.198.137 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:8900::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
cdn.sanity-host.com	• ns-715.awsdns-25.net / 67bc168c2fefb74789790d337a83e6fd -	205.251.194.203 San Jose/California/United States (US) - Amazon.com	•
	•	2600:9000:5302:cb00::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
sanity-host.com	• ns-1229.awsdns-25.org / c736848fb76e28587b84f31a999c22ff -	205.251.196.205 Herndon/Virginia/United States (US) - Amazon.com
	•	2600:9000:5304:cd00::1 San Jose/California/United States (US) - Amazon.com, Inc.	•
	• ns-1598.awsdns-07.co.uk / 29695433da964ab7066b061aba1b3a06 -	205.251.198.62 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:3e00::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
	• ns-209.awsdns-26.com / c7c10fb11d73dd07beeed4e6c7fc2cfb -	205.251.192.209 Herndon/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5300:d100::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
	• ns-715.awsdns-25.net / 5bab9cb00943b43a1959ed4db0f5a033 -	205.251.194.203 San Jose/California/United States (US) - Amazon.com	•
	•	2600:9000:5302:cb00::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
ac.vh.ves.io	• ns-1119.awsdns-11.org / 2875e11a69a0daf4be3a0d71e8740bb9 -	205.251.196.95 Herndon/Virginia/United States (US) - Amazon.com	•
	T	2600:9000:5304:5f00::1 San Jose/California/United States (US) - Amazon.com, Inc.	•
	• ns-1673.awsdns-17.co.uk / 4c17a6fb9eefabf7052aea32d70e3ecb -	205.251.198.137 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5306:8900::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
	• ns-279.awsdns-34.com / 5fd9e706b78cfdbdbc4672ee6b37628c -	205.251.193.23 Ashburn/Virginia/United States (US) - Amazon.com	•
	•	2600:9000:5301:1700::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
	• ns-830.awsdns-39.net / 2069effcb85fab816bc5f60d1e55f385 -	205.251.195.62 San Jose/California/United States (US) - Amazon.com	•
	•	2600:9000:5303:3e00::1 London/England/United Kingdom (GB) - Amazon.com, Inc.	•
vh.ves.io	• ns-cloud-b1.googledomains.com / hex:DA FA 94 D9 CA DB C1 15 5A 97 94 E3 F0 D6 52 83	216.239.32.107 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6b Montreal/Quebec/Canada (CA) - Google LLC	•
ves.io	• ns-cloud-b1.googledomains.com / hex:EC 44 9C 56 EE 10 C5 B2 E9 F0 9F AD 72 87 CC 74	216.239.32.107 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6b Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-b2.googledomains.com / hex:A0 FA 82 B7 59 18 AB 32 88 67 52 34 1A EC AF AA	216.239.34.107 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6b Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-b3.googledomains.com / hex:6B DC 43 68 9C 43 47 DC 48 DB 14 99 47 1C 21 F6	216.239.36.107 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6b Montreal/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-b4.googledomains.com / hex:D7 51 88 57 6B E7 34 B4 79 C9 3D 3F 08 97 ED 1A	216.239.38.107 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6b Montreal/Quebec/Canada (CA) - Google LLC	•
com	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-defra-5		•
	• d.gtld-servers.net / nnn1-defra-5		•
	• e.gtld-servers.net / nnn1-defra-5		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-nlams-2e		•
io	• a0.nic.io / fra1.micro.hosts.meta.redstone.afilias-nst.info-1740000113		•
	• a2.nic.io / FRA4		•
	• b0.nic.io / app5.lax1.hosts.meta.redstone.afilias-nst.info-1633102198		•
	• c0.nic.io / app9.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•

4. SOA-Entries

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

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

Domain:	f5.com
Zone-Name:	f5.com
Primary:	pdns130.f5.com
Mail:	dnsadmin.f5.com
Serial:	12650
Refresh:	3600
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	8

Domain:	www.cdn.studio.f5.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1


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

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

Domain:	sanity-host.com
Zone-Name:	sanity-host.com
Primary:	ns-715.awsdns-25.net
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	8

Domain:	cdn.sanity-host.com
Zone-Name:	sanity-host.com
Primary:	ns-715.awsdns-25.net
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	2


Domain:	io
Zone-Name:	io
Primary:	a0.nic.io
Mail:	hostmaster.donuts.email
Serial:	1782754427
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	4

Domain:	ves.io
Zone-Name:	ves.io
Primary:	ns-cloud-b1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	355
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	8

Domain:	vh.ves.io
Zone-Name:	ves.io
Primary:	ns-cloud-b1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	355
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	2

Domain:	ac.vh.ves.io
Zone-Name:	ac.vh.ves.io
Primary:	ns-1673.awsdns-17.co.uk
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	8

Domain:	ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io
Zone-Name:	ac.vh.ves.io
Primary:	ns-1673.awsdns-17.co.uk
Mail:	awsdns-hostmaster.amazon.com
Serial:	1
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	86400
num Entries:	2

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://cdn.studio.f5.com/ 34.149.250.58	308	https://cdn.studio.f5.com/	0.026	A
Cache-Control: private
Location: https://cdn.studio.f5.com/
Date: Mon, 29 Jun 2026 17:47:45 GMT
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• https://cdn.studio.f5.com/ 34.149.250.58 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	200	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	2.053	A
Date: Mon, 29 Jun 2026 17:47:45 GMT
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Vary: origin
X-Varnish-Age: 0
Accept-Ranges: bytes
Via: 1.1 google
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Content-Type: application/json; charset=utf-8
Content-Length: 19

• http://cdn.studio.f5.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.149.250.58	308	https://cdn.studio.f5.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	0.020	A
Visible Content:
Cache-Control: private
Location: https://cdn.studio.f5.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Date: Mon, 29 Jun 2026 17:47:48 GMT
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• https://cdn.studio.f5.com/.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: 110.07 % Other inline scripts (∑/total): 0/0	2.133	A
Not Found
Visible Content:
Server: nginx/1.24.0
Date: Mon, 29 Jun 2026 17:47:52 GMT
Vary: origin
traceparent: 00-f3dcd108c51ca01856ce86f0e5aca504-a9758567fc95f78b-00
sanity-gateway: k8s-gcp-eu-w1-prod-ing-01
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Via: 1.1 google
Alt-Svc: h3=":443"; ma=2592000
Content-Type: text/html; charset=UTF-8
Content-Length: 153

• https://34.149.250.58/ 34.149.250.58 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	200	Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	2.047	N
Certificate error: RemoteCertificateNameMismatch
Date: Mon, 29 Jun 2026 17:47:49 GMT
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
Vary: origin
X-Varnish-Age: 0
Accept-Ranges: bytes
Via: 1.1 google
Alt-Svc: h3=":443"; ma=2592000
Content-Type: application/json; charset=utf-8
Content-Length: 19

7. Comments

	1. General Results, most used to calculate the result
A	name "cdn.studio.f5.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 108094 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: cdn.studio.f5.com 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: cdn.studio.f5.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: No cookie sent via http.
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 63072000 seconds = 730 days
A	Good: HSTS has includeSubdomains - directive
A	Good: HSTS has preload directive
	Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should immediately add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
A	http://cdn.studio.f5.com/ 34.149.250.58	308	https://cdn.studio.f5.com/	Correct redirect http - https with the same domain name
N	https://34.149.250.58/ 34.149.250.58	200		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
X	Fatal error: Nameserver doesn't support TCP connection: ns-1229.awsdns-25.org / 205.251.196.205: Timeout
	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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain cdn.studio.f5.com, 1 ip addresses.
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.cdn.studio.f5.com
	2. Header-Checks
F	cdn.studio.f5.com 34.149.250.58	Content-Security-Policy		Critical: Missing Header:
F	cdn.studio.f5.com 34.149.250.58	X-Content-Type-Options		Critical: Missing Header:
F	cdn.studio.f5.com 34.149.250.58	Referrer-Policy		Critical: Missing Header:
F	cdn.studio.f5.com 34.149.250.58	Permissions-Policy		Critical: Missing Header:
B	cdn.studio.f5.com 34.149.250.58	Cross-Origin-Embedder-Policy		Info: Missing Header
B	cdn.studio.f5.com 34.149.250.58	Cross-Origin-Opener-Policy		Info: Missing Header
B	cdn.studio.f5.com 34.149.250.58	Cross-Origin-Resource-Policy		Info: Missing Header
	3. DNS- and NameServer - Checks
A	Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.pdns130.f5.com (104.219.104.131, 2620:0:c12:f5f5:1::c3), pdns131.f5.com (104.219.105.131, 2620:0:c13:f5f5:1::c3), pdns150.f5.com (104.219.106.131, 2620:0:c14:f5f5:1::c3), pdns151.f5.com (104.219.107.131, 2620:0:c15:f5f5:1::c3)
A	Good (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: pdns130.f5.com, pdns131.f5.com, pdns150.f5.com, pdns151.f5.com, 4 Name Servers included in Delegation: pdns130.f5.com, pdns131.f5.com, pdns150.f5.com, pdns151.f5.com, 4 Name Servers included in 1 Zone definitions: pdns130.f5.com, pdns131.f5.com, pdns150.f5.com, pdns151.f5.com, 1 Name Servers listed in SOA.Primary: pdns130.f5.com.
A	Good: Only one SOA.Primary Name Server found.: pdns130.f5.com.
A	Good: SOA.Primary Name Server included in the delegation set.: pdns130.f5.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	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 104., 1 different subnets (first two Bytes): 104.219., 4 different subnets (first three Bytes): 104.219.104., 104.219.105., 104.219.106., 104.219.107.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2620:, 1 different subnets (first two blocks): 2620:0000:, 4 different subnets (first three blocks): 2620:0000:0c12:, 2620:0000:0c13:, 2620:0000:0c14:, 2620:0000:0c15:, 4 different subnets (first four blocks): 2620:0000:0c12:f5f5:, 2620:0000:0c13:f5f5:, 2620:0000:0c14:f5f5:, 2620:0000:0c15:f5f5:
A	Good: Name Server IPv6 addresses from different subnets found.
X	Nameserver Timeout checking Echo Capitalization: pdns131.f5.com / 104.219.105.131
X	Nameserver Timeout checking EDNS512: pdns130.f5.com / 2620:0:c12:f5f5:1::c3
	Nameserver doesn't pass all EDNS-Checks: a0.nic.io: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (fra1.micro.hosts.meta.redstone.afilias-nst.info-1740000113). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: c0.nic.io: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (app9.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-1119.awsdns-11.org / 2600:9000:5304:5f00::1: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (f5f2dc13d4f281e3467a1e7dd7f5a32a -). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-1229.awsdns-25.org / 2600:9000:5304:cd00::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (f44c5e57398c2098ebc0abb3ce373764 -). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-715.awsdns-25.net / 2600:9000:5302:cb00::1: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (83457b82e8023a151e2650d260f5c481 -). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-715.awsdns-25.net / 2600:9000:5302:cb00::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (9675e31ed4e71c0ce402cbf98d26d034 -). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns-830.awsdns-39.net / 2600:9000:5303:3e00::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (212f52e4c22e2a5d75ece3476d81ca82 -). COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: pdns130.f5.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: amazon.com is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: comodoca.com is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: entrust.net is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates
A	Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create 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: No https + http status 200 with inline CSS / JavaScript found
A	Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
A	Good: Every https connection via port 443 supports the http/2 protocol via ALPN.
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://cdn.studio.f5.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	404	2.133 seconds	Warning: 404 needs more then one second
A	Duration: 430533 milliseconds, 430.533 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

cdn.studio.f5.com

34.149.250.58

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

cdn.studio.f5.com

34.149.250.58

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported
SNI required

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

http/2 via ALPN supported
SNI required

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

Chain (complete)	1	CN=letsencrypt01.cdn.sanity-host.com
	2	CN=R12, O=Let's Encrypt, C=US

cdn.studio.f5.com

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

cdn.studio.f5.com

443

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

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 (complete)	1	CN=letsencrypt01.cdn.sanity-host.com
	2	CN=R12, O=Let's Encrypt, C=US

34.149.250.58

443

name does not match

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

34.149.250.58

443

name does not match

Tls12

ECDH Ephermal

255

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

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

http/2 via ALPN supported
Cert sent without SNI

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

Chain - too much certificates, don't send root certificates	1	CN=*.sanity.io
	2	CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB
	3	CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB

9. Certificates

CN=letsencrypt01.cdn.sanity-host.com

26.04.2026

25.07.2026
expires in 4 days

assets.curetoday.com, assets.unilever.com, cdn-s.lmno.care, cdn.8x8.com, cdn.autofoos.com, cdn.content.foolcdn.com, cdn.equinor.com, cdn.mrmarvis.com, cdn.reco.ai, cdn.stackoverflow.co, cdn.studio.f5.com, images.buoyhealth.com, images.staging.buoyhealth.com, letsencrypt01.cdn.sanity-host.com, media.curetoday.com - 15 entries

CN=letsencrypt01.cdn.sanity-host.com

26.04.2026

25.07.2026
expires in 4 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	06EAE4A35106014CB34DEF4A6556CC6D2022
Thumbprint:	3654D0B0CD19DEB0ED1FE60C6FEF2CD79CEBE967
SHA256 / Certificate:	mbwCGj1oaCTsRU5FQCQ5GU3UDSTxuWYT2sfZjLqJT24=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	9c9610f7a84624e6b55677f6fa99c26bdfcfa68ffd4a4fc388cf6ac1e68069c7
SHA256 hex / Subject Public Key Information (SPKI):	9c9610f7a84624e6b55677f6fa99c26bdfcfa68ffd4a4fc388cf6ac1e68069c7 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1)

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

13.03.2024

13.03.2027
expires in 235 days

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

13.03.2024

13.03.2027
expires in 235 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	00C212324B70A9B49171DC40F7E285263C
Thumbprint:	EE44782835D8FB31394DA5CEB840DC93849BCF5A
SHA256 / Certificate:	Ex/Od4QBaJmloAIDqe/IDxjrvXVYBxftwVU1gJMINuw=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	919c0df7a787b597ed056ace654b1de9c0387acf349f73734a4fd7b58cf612a4
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:	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 3240 days

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

04.06.2015

04.06.2035
expires in 3240 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:

CN=*.sanity.io

21.08.2025

19.09.2026
expires in 60 days

*.sanity.io, sanity.io - 2 entries

CN=*.sanity.io

21.08.2025

19.09.2026
expires in 60 days

*.sanity.io, sanity.io - 2 entries

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	1105F720E1DCA0706ACF57CBE625CFC5
Thumbprint:	0C8E04FA7AE83CE3650CEF9B20BEE0B73528DF31
SHA256 / Certificate:	7OqAsXZNWiohTRTCaZsZplgfza1iQ9VmyYyqR6s7+as=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	4b820c1cfd6b89ebaf0ae08786a2cfcd5cecd57ffe2634fe57714a5ed98ec04e
SHA256 hex / Subject Public Key Information (SPKI):	4b820c1cfd6b89ebaf0ae08786a2cfcd5cecd57ffe2634fe57714a5ed98ec04e (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.sectigo.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)

CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB

22.03.2021

22.03.2036
expires in 3532 days

CN=Sectigo Public Server Authentication CA DV R36, O=Sectigo Limited, C=GB

22.03.2021

22.03.2036
expires in 3532 days

Keyalgorithm	RSA encryption ( bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	397A66CC2756362E0DAA87CA6EABE3B1
Thumbprint:	DD55B4520291E276588F0DD02FAFD83A7368E0FA
SHA256 / Certificate:	jFTDNLZrpOQmdyr0o/kTbBmhrscp/bKMU1wHpaTvIuA=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	6bd9212ce649c659c9cabc6cb60fcffac7a20c29be61fdceb2b5f2168701688d
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.sectigo.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)

CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB

22.03.2021

22.03.2046
expires in 7184 days

CN=Sectigo Public Server Authentication Root R46, O=Sectigo Limited, C=GB

22.03.2021

22.03.2046
expires in 7184 days

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA384 With RSA Encryption
Serial Number:	758DFD8BAE7C0700FAA925A7E1C7AD14
Thumbprint:	AD98F9F3E47D753B65D482B3A45217BB6EF5E438
SHA256 / Certificate:	e7ZHpirurIi/JXqlItAf/qOV4KtFxz+T9lZU7DjyWgY=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	0e8bb18bbeefb381be21bfc1a206d317298462ad104855f04a0542699708d3d4
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:

10. Last Certificates - Certificate Transparency Log Check

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

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

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
14664979643 leaf cert	CN=R12, O=Let's Encrypt, C=US	2026-04-26 19:56:59	2026-07-25 19:56:58	assets.curetoday.com, assets.unilever.com, cdn.8x8.com, cdn.autofoos.com, cdn.content.foolcdn.com, cdn.equinor.com, cdn.mrmarvis.com, cdn.reco.ai, cdn.stackoverflow.co, cdn.studio.f5.com, cdn-s.lmno.care, images.buoyhealth.com, images.staging.buoyhealth.com, letsencrypt01.cdn.sanity-host.com, media.curetoday.com - 15 entries

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/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: pdns130.f5.com, pdns131.f5.com, pdns150.f5.com, pdns151.f5.com

QNr.	Domain	Type	NS used
1	com	NS	b.root-servers.net (2001:500:200::b)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	pdns130.f5.com: 104.219.104.131, 2620:0:c12:f5f5:1::c3	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: pdns131.f5.com 104.219.105.131, 2620:0:c13:f5f5:1::c3
	Answer: pdns150.f5.com 104.219.106.131, 2620:0:c14:f5f5:1::c3
	Answer: pdns151.f5.com 104.219.107.131, 2620:0:c15:f5f5:1::c3

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries
ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io	0		no CAA entry found	1
cdn.sanity-host.com	5	issue	letsencrypt.org	1
cdn.studio.f5.com				1
sanity-host.com	5	issue	letsencrypt.org	1
studio.f5.com				1
ac.vh.ves.io	0		no CAA entry found	1
vh.ves.io	0		no CAA entry found	1
ves.io	0		no CAA entry found	1
f5.com	5	issue	amazon.com	1
	5	issue	comodoca.com	1
	5	issue	digicert.com	1
	5	issue	entrust.net	1
	5	issue	letsencrypt.org	1
	5	iodef	mailto:dnsadmin@f5.com	1
	5	issue	pki.goog	1
	5	issue	sectigo.com	1
com	0		no CAA entry found	1
	0		no CAA entry found	1
io	0		no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
studio.f5.com		1
cdn.studio.f5.com		1
_acme-challenge.cdn.studio.f5.com	Name Error - The domain name does not exist	1
_acme-challenge.cdn.sanity-host.com		1
_acme-challenge.cdn.studio.f5.com.studio.f5.com	Name Error - The domain name does not exist	1
_acme-challenge.cdn.studio.f5.com.cdn.studio.f5.com	Name Error - The domain name does not exist	1
_acme-challenge.cdn.sanity-host.com.cdn.sanity-host.com		1
_acme-challenge.ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io	Name Error - The domain name does not exist	1
_acme-challenge.ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io.ves-io-59be2ec3-27e8-406e-a44b-9a535a0dcbf3.ac.vh.ves.io	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
cdn.studio.f5.com	34.149.250.58	443	5 Ciphers	33.69 sec		0 without, 5 FS	100.00 %
Complete		1	5 Ciphers 5.00 Ciphers/Check	33.69 sec	33.69 sec/Check	0 without, 5 FS	100.00 %

Details
Domain	IP	Port	Cipher (OpenSsl / IANA)
cdn.studio.f5.com	34.149.250.58	443	ECDHE-RSA-CHACHA20-POLY1305		(Secure)	TLSv1.2	0xCC,0xA8	FS
5 Ciphers, 33.69 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-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	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

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=aa78da44-712c-40f6-9747-fe959298b3f6

Last Result: https://check-your-website.server-daten.de/?q=cdn.studio.f5.com - 2026-06-29 19:41:31

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=cdn.studio.f5.com

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

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

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