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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
24.07.2025 19:21:03

Older results

A - 21.03.2023 23:49:26

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
bitwarden.johnson-technologies.com	A	71.67.166.144 Delaware/Ohio/United States (US) - Charter Communications Hostname: syn-071-067-166-144.res.spectrum.com	yes	1	0
	AAAA		yes
www.bitwarden.johnson-technologies.com	A	71.67.166.144 Delaware/Ohio/United States (US) - Charter Communications Hostname: syn-071-067-166-144.res.spectrum.com	yes	1	0
	AAAA		yes
*.johnson-technologies.com	A	71.67.166.144	yes
	AAAA		yes
	CNAME		yes
*.bitwarden.johnson-technologies.com	A	71.67.166.144	yes
	AAAA		yes
	CNAME		yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


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


	• Status: Valid because published


	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 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 53148, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.08.2025, 00:00:00 +, Signature-Inception: 21.07.2025, 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=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.08.2025, 12:00:00 +, Signature-Inception: 24.07.2025, 11:00:00 +, KeyTag 46441, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46441 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 20545, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.08.2025, 14:02:35 +, Signature-Inception: 21.07.2025, 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: johnson-technologies.com
johnson-technologies.com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 35917, DigestType 1 and Digest 8hMLC9hHzuoILN+Ozvd/Wv5AE6E=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.07.2025, 00:51:46 +, Signature-Inception: 20.07.2025, 23:41:46 +, KeyTag 20545, Signer-Name: com


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 27691, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 35917, Signer-Name: johnson-technologies.com


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 35917, DigestType 1 and Digest "8hMLC9hHzuoILN+Ozvd/Wv5AE6E=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: bitwarden.johnson-technologies.com
bitwarden.johnson-technologies.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "*.johnson-technologies.com" and the NextOwner "_acme-challenge.johnson-technologies.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: TXT, RRSIG, NSEC


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 71.67.166.144. RRSIG Owner has 3 labels, RRSIG Labels = 2, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name. Validated: RRSIG-Owner bitwarden.johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 180 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	A-Query sends a valid NSEC RR as result with the query name "bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that A RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the query name "bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that CNAME RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that TXT RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that AAAA RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "_443._tcp.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.bitwarden.johnson-technologies.com) sends a valid NSEC RR as result with the query name "_443._tcp.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.bitwarden.johnson-technologies.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that CAA RR. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.

Zone: www.bitwarden.johnson-technologies.com
www.bitwarden.johnson-technologies.com	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "*.johnson-technologies.com" and the NextOwner "_acme-challenge.johnson-technologies.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the parent zone confirmes the non-existence of a DS RR. Bitmap: TXT, RRSIG, NSEC


	RRSIG Type 1 validates the A - Result: 71.67.166.144. RRSIG Owner has 4 labels, RRSIG Labels = 2, so it's a wildcard expansion, the Query Name doesn't exists. An additional NSEC/NSEC3 is required to confirm the Not-Existence of the query name. Validated: RRSIG-Owner www.bitwarden.johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 180 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	A-Query sends a valid NSEC RR as result with the query name "www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that A RR.A-Query sends a valid NSEC RR as result with the parent Wildcard "*.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "www.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the query name "www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that CNAME RR.CNAME-Query sends a valid NSEC RR as result with the parent Wildcard "*.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "www.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that TXT RR.TXT-Query sends a valid NSEC RR as result with the parent Wildcard "*.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "www.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that AAAA RR.AAAA-Query sends a valid NSEC RR as result with the parent Wildcard "*.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "_443._tcp.www.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.bitwarden.johnson-technologies.com) sends a valid NSEC RR as result with the query name "_443._tcp.www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.www.bitwarden.johnson-technologies.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the owner name .johnson-technologies.com as the Wildcard-Expansion of the Closest Encloser of the query name "www.bitwarden.johnson-technologies.com". So the Wildcard-Expansion of the Closest Encloser confirms that the query name is generated via wildcard expansion (NoError instead of NXDomain). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner .johnson-technologies.com., Algorithm: 13, 2 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that CAA RR.CAA-Query sends a valid NSEC RR as result with the parent Wildcard "*.bitwarden.johnson-technologies.com" between the NSEC-owner "_acme-challenge.johnson-technologies.com" and the NextOwner "hy.johnson-technologies.com". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: TXT, RRSIG, NSEC Validated: RRSIG-Owner _acme-challenge.johnson-technologies.com., Algorithm: 13, 3 Labels, original TTL: 3601 sec, Signature-expiration: 31.07.2025, 00:00:00 +, Signature-Inception: 10.07.2025, 00:00:00 +, KeyTag 27691, Signer-Name: johnson-technologies.com


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.bitwarden.johnson-technologies.com	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1		•
bitwarden.johnson-technologies.com	• dns1.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.132.200 New York/United States (US) - Neustar Security Services	•
	•	2610:a1:1024::200 New York/United States (US) - Neustar Security Services	•
johnson-technologies.com	• dns1.registrar-servers.com / Auth_NC_Host1.Frankfurt_Node1	156.154.132.200 New York/United States (US) - Neustar Security Services	•
	•	2610:a1:1024::200 New York/United States (US) - Neustar Security Services	•
	• dns2.registrar-servers.com / Auth_NC_Host2.Frankfurt_Node1	156.154.133.200 New York/United States (US) - Neustar Security Services	•
	•	2610:a1:1025::200 Herndon/Virginia/United States (US) - Neustar Security Services	•
com	• a.gtld-servers.net / nnn1-mnz5		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-mnz2		•
	• d.gtld-servers.net / nnn1-dca2		•
	• e.gtld-servers.net / nnn1-mnz3		•
	• f.gtld-servers.net / nnn1-ham5		•
	• g.gtld-servers.net / nnn1-wie2		•
	• h.gtld-servers.net / nnn1-wie2		•
	• i.gtld-servers.net / nnn1-wie5		•
	• j.gtld-servers.net / nnn1-sesto-2		•
	• k.gtld-servers.net / nnn1-sesto-2		•
	• l.gtld-servers.net / nnn1-sesto-2		•
	• m.gtld-servers.net / nnn1-sesto-2		•

4. SOA-Entries

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

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

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

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

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

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

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

Domain:	bitwarden.johnson-technologies.com
Zone-Name:	johnson-technologies.com
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1753069679
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	2

Domain:	www.bitwarden.johnson-technologies.com
Zone-Name:	johnson-technologies.com
Primary:	dns1.registrar-servers.com
Mail:	hostmaster.registrar-servers.com
Serial:	1753069679
Refresh:	43200
Retry:	3600
Expire:	604800
TTL:	3601
num Entries:	1

5. Screenshots

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

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://bitwarden.johnson-technologies.com/ 71.67.166.144	-14	10.020	T
Timeout - The operation has timed out.

• http://www.bitwarden.johnson-technologies.com/ 71.67.166.144	-14	10.030	T
Timeout - The operation has timed out.

• https://bitwarden.johnson-technologies.com/ 71.67.166.144	-14	10.030	T
Timeout - The operation has timed out.

• https://www.bitwarden.johnson-technologies.com/ 71.67.166.144	-14	10.023	T
Timeout - The operation has timed out.

• http://bitwarden.johnson-technologies.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 71.67.166.144	-14	10.027	T
Timeout - The operation has timed out.
Visible Content:

• http://www.bitwarden.johnson-technologies.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 71.67.166.144	-14	10.024	T
Timeout - The operation has timed out.
Visible Content:

• https://71.67.166.144/ 71.67.166.144	-14	10.036	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "bitwarden.johnson-technologies.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: 105960 (complete: 271405)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: bitwarden.johnson-technologies.com has only one ip address.
	Warning: Only one ip address found: www.bitwarden.johnson-technologies.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: bitwarden.johnson-technologies.com has no ipv6 address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.bitwarden.johnson-technologies.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain bitwarden.johnson-technologies.com, 1 ip addresses.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.bitwarden.johnson-technologies.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.bitwarden.johnson-technologies.com
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 24 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 24 Queries complete, 24 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 12.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
A	Good: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
A	Good: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.com.
A	Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns1.registrar-servers.com, dns2.registrar-servers.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: registrar-servers.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	http://bitwarden.johnson-technologies.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 71.67.166.144	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.bitwarden.johnson-technologies.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 71.67.166.144	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 164103 milliseconds, 164.103 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

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

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

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
4978651545 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-03-21 21:36:17	2023-06-19 21:36:16	bitwarden.johnson-technologies.com - 1 entries
4631413667 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-01-02 20:36:04	2023-04-02 20:36:03	bitwarden.johnson-technologies.com - 1 entries
4630990947 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-01-02 17:59:02	2023-04-02 17:59:01	bitwarden.johnson-technologies.com - 1 entries
4630955584 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-01-02 17:43:53	2023-04-02 17:43:52	bitwarden.johnson-technologies.com - 1 entries
4615565630 leaf cert	CN=R3, O=Let's Encrypt, C=US	2022-12-30 02:07:00	2023-03-30 02:06:59	bitwarden.johnson-technologies.com - 1 entries

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

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

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
18743587235 precert	CN=E6, O=Let's Encrypt, C=US	2025-06-01 01:06:47	2025-08-30 01:06:46	*.johnson-technologies.com, johnson-technologies.com 2 entries
17556487234 leaf cert	CN=E5, O=Let's Encrypt, C=US	2025-03-11 02:07:36	2025-06-09 01:07:35	*.johnson-technologies.com, johnson-technologies.com 2 entries
11317208586 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-12-04 19:50:36	2024-03-03 19:50:35	*.johnson-technologies.com, johnson-technologies.com 2 entries

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

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

14. CAA - Entries

Domainname	Value	∑ Queries
www.bitwarden.johnson-technologies.com	no CAA entry found	1
bitwarden.johnson-technologies.com	no CAA entry found	1
johnson-technologies.com	no CAA entry found	1
com	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
johnson-technologies.com	v=spf1 mx ~all	ok	1
bitwarden.johnson-technologies.com		ok	1
www.bitwarden.johnson-technologies.com		ok	1
_acme-challenge.bitwarden.johnson-technologies.com		missing entry or wrong length	1
_acme-challenge.www.bitwarden.johnson-technologies.com		missing entry or wrong length	1
_acme-challenge.bitwarden.johnson-technologies.com.johnson-technologies.com		perhaps wrong	1
_acme-challenge.bitwarden.johnson-technologies.com.bitwarden.johnson-technologies.com		perhaps wrong	1
_acme-challenge.www.bitwarden.johnson-technologies.com.bitwarden.johnson-technologies.com		perhaps wrong	1
_acme-challenge.www.bitwarden.johnson-technologies.com.www.bitwarden.johnson-technologies.com		perhaps wrong	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=46e7c935-0bdc-471f-90dc-c327b4bfae49

Last Result: https://check-your-website.server-daten.de/?q=bitwarden.johnson-technologies.com - 2025-07-24 19:21:03

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

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