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

0 in Queue, 1 of max. 8 Checks (20:38:40)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

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

 

S

 

Server error

 

Checked:
29.11.2024 17:22:06

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
argocd.arnia-bfc.synaltic.app
A
141.94.169.202
Gravelines/Hauts-de-France/France (FR) - OVH SAS
No Hostname found
yes
1
0

AAAA

yes


www.argocd.arnia-bfc.synaltic.app
A
141.94.169.202
Gravelines/Hauts-de-France/France (FR) - OVH SAS
No Hostname found
yes
1
0

AAAA

yes


*.arnia-bfc.synaltic.app
A
141.94.169.202
yes



AAAA

yes



CNAME

yes


*.argocd.arnia-bfc.synaltic.app
A
141.94.169.202
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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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






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






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



Zone: app

app
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 23684, DigestType 2 and Digest OlzIox4CyUq6ZGGRL6u36fXjSVe7YRSlWoZNlq7DGDY=






1 RRSIG RR to validate DS RR found






RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.12.2024, 05:00:00 +, Signature-Inception: 29.11.2024, 04:00:00 +, KeyTag 61050, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 54916, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner app., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 20.12.2024, 11:58:48 +, Signature-Inception: 28.11.2024, 11:58:48 +, KeyTag 23684, Signer-Name: app






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






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



Zone: synaltic.app

synaltic.app
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 58, DigestType 2 and Digest Whc2mOBNcl5Q1GixpPEl4Mpugm2C5vf9dyLK6vQi0lE=






1 RRSIG RR to validate DS RR found






RRSIG-Owner synaltic.app., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 20.12.2024, 11:58:48 +, Signature-Inception: 28.11.2024, 11:58:48 +, KeyTag 54916, Signer-Name: app






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 6883, Flags 256






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner synaltic.app., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 58, Signer-Name: synaltic.app






RRSIG-Owner synaltic.app., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






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






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






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



Zone: arnia-bfc.synaltic.app

arnia-bfc.synaltic.app
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 "orq1gcljgbj085jcta4c6epm99od7tsa" between the hashed NSEC3-owner "orq1gcljgbj085jcta4c6epm99od7tsa" and the hashed NextOwner "picmik0f8lbhl7p7psnis27aplltff1g". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






0 DNSKEY RR found









Zone: argocd.arnia-bfc.synaltic.app

argocd.arnia-bfc.synaltic.app
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 "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "orq1gcljgbj085jcta4c6epm99od7tsa" as Owner. That's the Hash of "arnia-bfc.synaltic.app" with the NextHashedOwnerName "picmik0f8lbhl7p7psnis27aplltff1g". So that domain name is the Closest Encloser of "argocd.arnia-bfc.synaltic.app". Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






The ClosestEncloser says, that "*.arnia-bfc.synaltic.app" with the Hash "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" and the Next Owner "ddhbtotncvpahob9smfule8009vsmae9", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 141.94.169.202. RRSIG Owner has 4 labels, RRSIG Labels = 3, 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 argocd.arnia-bfc.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "38ovhvogrhlkhctmei918s52n7vouna1". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "38ovhvogrhlkhctmei918s52n7vouna1". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "38ovhvogrhlkhctmei918s52n7vouna1". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.argocd.arnia-bfc.synaltic.app) sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "b4n6mtc0s2cvfj9ncehe0560h6p8c2le". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "38ovhvogrhlkhctmei918s52n7vouna1". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






A-Query sends a valid NSEC3 RR as result with the hashed query name "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the zone confirmes the not-existence of that A RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: Validated Data sent, but the NSEC3Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the zone confirmes the not-existence of that CNAME RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the zone confirmes the not-existence of that TXT RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the zone confirmes the not-existence of that AAAA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "38ovhvogrhlkhctmei918s52n7vouna1" between the hashed NSEC3-owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the hashed NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So the zone confirmes the not-existence of that CAA RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC3 covers the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC3-Records, so DNSSEC works.



Zone: www.argocd.arnia-bfc.synaltic.app

www.argocd.arnia-bfc.synaltic.app
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "orq1gcljgbj085jcta4c6epm99od7tsa" as Owner. That's the Hash of "arnia-bfc.synaltic.app" with the NextHashedOwnerName "picmik0f8lbhl7p7psnis27aplltff1g". So that domain name is the Closest Encloser of "www.argocd.arnia-bfc.synaltic.app". Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






The ClosestEncloser says, that "*.arnia-bfc.synaltic.app" with the Hash "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" and the Next Owner "ddhbtotncvpahob9smfule8009vsmae9", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






RRSIG Type 1 validates the A - Result: 141.94.169.202. RRSIG Owner has 5 labels, RRSIG Labels = 3, 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.argocd.arnia-bfc.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






A-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "clforer0b7955v13qerb97rqccnhu4lq". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "clforer0b7955v13qerb97rqccnhu4lq". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "clforer0b7955v13qerb97rqccnhu4lq". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.www.argocd.arnia-bfc.synaltic.app) sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "sb534ilmel978trvi9jst4d668tedngo". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "orq1gcljgbj085jcta4c6epm99od7tsa" (unhashed: arnia-bfc.synaltic.app). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner orq1gcljgbj085jcta4c6epm99od7tsa.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "38ovhvogrhlkhctmei918s52n7vouna1" (unhashed: argocd.arnia-bfc.synaltic.app) with the owner "1vdfipnm2jgplb738tcn6k53mmai9amd" and the NextOwner "3vof4cvu0n57b2su69ctnu0a3ubs6tk1". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: A, RRSIG Validated: RRSIG-Owner 1vdfipnm2jgplb738tcn6k53mmai9amd.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "d6sh2hd9v42q9mjleu0irek2v4mbn3r1" (unhashed: *.arnia-bfc.synaltic.app) as the Wildcard-Expansion of the Closest Encloser of the query name "clforer0b7955v13qerb97rqccnhu4lq". 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 Validated: RRSIG-Owner d6sh2hd9v42q9mjleu0irek2v4mbn3r1.synaltic.app., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 29.12.2024, 01:00:13 +, Signature-Inception: 29.11.2024, 01:00:13 +, KeyTag 6883, Signer-Name: synaltic.app






Status: Good. NoData-Proof required and found.

 

3. Name Servers

DomainNameserverNS-IP
www.argocd.arnia-bfc.synaltic.app
•  dns100.ovh.net
•
argocd.arnia-bfc.synaltic.app
•  dns100.ovh.net
213.251.188.144
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:1:4a90::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•
arnia-bfc.synaltic.app
•  dns100.ovh.net
213.251.188.144
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:1:4a90::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•
synaltic.app
•  dns100.ovh.net
213.251.188.144
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:1:4a90::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

•  ns100.ovh.net
213.251.128.144
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•

• 
2001:41d0:1:1990::1
Roubaix/Hauts-de-France/France (FR) - OVH SAS		•
app
•  ns-tld1.charlestonroadregistry.com
•

•  ns-tld2.charlestonroadregistry.com
•

•  ns-tld3.charlestonroadregistry.com
•

•  ns-tld4.charlestonroadregistry.com
•

•  ns-tld5.charlestonroadregistry.com
•

 

4. SOA-Entries


Domain:app
Zone-Name:app
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:101427
Refresh:21600
Retry:3600
Expire:259200
TTL:900
num Entries:5


Domain:synaltic.app
Zone-Name:synaltic.app
Primary:dns100.ovh.net
Mail:tech.ovh.net
Serial:2024112900
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:4


Domain:arnia-bfc.synaltic.app
Zone-Name:synaltic.app
Primary:dns100.ovh.net
Mail:tech.ovh.net
Serial:2024112900
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:argocd.arnia-bfc.synaltic.app
Zone-Name:synaltic.app
Primary:dns100.ovh.net
Mail:tech.ovh.net
Serial:2024112900
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:2


Domain:www.argocd.arnia-bfc.synaltic.app
Zone-Name:synaltic.app
Primary:dns100.ovh.net
Mail:tech.ovh.net
Serial:2024112900
Refresh:86400
Retry:3600
Expire:3600000
TTL:300
num Entries:1


5. Screenshots

Startaddress: https://argocd.arnia-bfc.synaltic.app/, address used: https://argocd.arnia-bfc.synaltic.app/login?return_url=https%3A%2F%2Fargocd.arnia-bfc.synaltic.app%2Fapplications, Screenshot created 2024-11-29 17:25:27 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

1214 milliseconds

 

Screenshot mobile - https://argocd.arnia-bfc.synaltic.app/login?return_url=https%3A%2F%2Fargocd.arnia-bfc.synaltic.app%2Fapplications
Mobil + Landscape (732px x 412px)

 

1156 milliseconds

 

Screenshot mobile landscape - https://argocd.arnia-bfc.synaltic.app/login?return_url=https%3A%2F%2Fargocd.arnia-bfc.synaltic.app%2Fapplications
Screen (1280px x 1680px)

 

1854 milliseconds

 

Screenshot Desktop - https://argocd.arnia-bfc.synaltic.app/login?return_url=https%3A%2F%2Fargocd.arnia-bfc.synaltic.app%2Fapplications

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

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

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://argocd.arnia-bfc.synaltic.app/
141.94.169.202
503

Html is minified: 100.94 %
0.066
S
Service Unavailable
Cache-Control: no-cache
Content-Length: 107
Content-Type: text/html

• http://www.argocd.arnia-bfc.synaltic.app/
141.94.169.202
503

Html is minified: 100.94 %
0.036
S
Service Unavailable
Cache-Control: no-cache
Content-Length: 107
Content-Type: text/html

• https://argocd.arnia-bfc.synaltic.app/
141.94.169.202 gzip used - 454 / 788 - 42.39 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		200

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0		2.736
N
Certificate error: RemoteCertificateChainErrors
Date: Fri, 29 Nov 2024 16:23:05 GMT
Connection: keep-alive
Accept-Ranges: bytes
Content-Security-Policy: frame-ancestors 'self';
Vary: Accept-Encoding
X-Frame-Options: sameorigin
X-XSS-Protection: 1
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html; charset=utf-8
Content-Length: 454
Content-Encoding: gzip

• https://www.argocd.arnia-bfc.synaltic.app/
141.94.169.202
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0		2.450
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Fri, 29 Nov 2024 16:23:10 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html
Content-Length: 146

• http://argocd.arnia-bfc.synaltic.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
141.94.169.202
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		503

Html is minified: 100.94 %
Other inline scripts (∑/total): 0/0		0.033
S
Service Unavailable
Visible Content:
Cache-Control: no-cache
Content-Length: 107
Content-Type: text/html

• http://www.argocd.arnia-bfc.synaltic.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
141.94.169.202
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		503

Html is minified: 100.94 %
Other inline scripts (∑/total): 0/0		0.033
S
Service Unavailable
Visible Content:
Cache-Control: no-cache
Content-Length: 107
Content-Type: text/html

• https://141.94.169.202/
141.94.169.202
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 110.61 %
Other inline scripts (∑/total): 0/0		3.680
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Date: Fri, 29 Nov 2024 16:23:16 GMT
Connection: keep-alive
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Type: text/html
Content-Length: 146

 

7. Comments


1. General Results, most used to calculate the result

Aname "argocd.arnia-bfc.synaltic.app" is subdomain, public suffix is ".app", top-level-domain is ".app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .app-domains preloaded: 46 (complete: 263653)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: argocd.arnia-bfc.synaltic.app has only one ip address.
Warning: Only one ip address found: www.argocd.arnia-bfc.synaltic.app 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: argocd.arnia-bfc.synaltic.app 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.argocd.arnia-bfc.synaltic.app has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: every https has a Strict Transport Security Header
AHSTS max-age is short - minimum 31536000 = 365 days required, 15724800 seconds = 182 days found, but not a problem because domain has an old preload-entry (Google-Policy: public-suffix)
AGood: HSTS has includeSubdomains - directive
AExcellent: Main Domain is in the Google-Preload-List
AExcellent: Main Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (3 urls)
https://www.argocd.arnia-bfc.synaltic.app/ 141.94.169.202


Url with incomplete Content-Type - header - missing charset
https://141.94.169.202/ 141.94.169.202


Url with incomplete Content-Type - header - missing charset
Ihttps://argocd.arnia-bfc.synaltic.app/ 141.94.169.202
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Mhttps://www.argocd.arnia-bfc.synaltic.app/ 141.94.169.202
404

Misconfiguration - main pages should never send http status 400 - 499
Mhttps://141.94.169.202/ 141.94.169.202
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://argocd.arnia-bfc.synaltic.app/ 141.94.169.202
200

Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://www.argocd.arnia-bfc.synaltic.app/ 141.94.169.202
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://141.94.169.202/ 141.94.169.202
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
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 argocd.arnia-bfc.synaltic.app, 1 ip addresses.
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 www.argocd.arnia-bfc.synaltic.app, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.argocd.arnia-bfc.synaltic.app

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

Aargocd.arnia-bfc.synaltic.app 141.94.169.202
Content-Security-Policy
Ok: Header without syntax errors found: frame-ancestors 'self';
F

Bad: Missing default-src directive. A default-src directive is used if one of the specialized fetch directives (child-src, connect-src, font-src, frame-src, img-src, manifest-src, media-src, object-src, prefetch-src, script-src, style-src, worker-src) isn't defined. Missing default-src, all sources are allowed, that's bad. A default-src with 'none' or 'self' blocks that.
E

Bad: No form-action directive found. Use one to limit the form - action - destinations. form-action is a navigation-directive, so default-src isn't used.
A

Good: frame-ancestors directive found. That limits pages who are allowed to use this page in a frame / iframe / object / embed / applet. frame-ancestors is a navigation-directive, so default-src isn't used.
E

Bad: No base-uri directive found. Use one to limit the URLs which can be used in a document's <base> element. Because it's a document directive, default-src isn't used, so an own directive is required.
F

Critical: No object-src and no default-src as fallback defined. So object / embed / applet can load every resource. That's fatal.
F

Critical: No script-src and no default-src as fallback defined. So scripts are unlimited. That's fatal.
A
X-Frame-Options
Ok: Header without syntax errors found: sameorigin
B

Info: Header is deprecated. May not longer work in modern browsers. sameorigin. Better solution: Use a Content-Security-Policy Header with a frame-ancestors directive. DENY - use 'none', SAMEORIGIN - use 'self'. If you want to allow some domains to frame your page, add these urls.
A
X-Xss-Protection
Ok: Header without syntax errors found: 1
B

Info: Header is deprecated. May not longer work in modern browsers. 1
Fargocd.arnia-bfc.synaltic.app 141.94.169.202
X-Content-Type-Options
Critical: Missing Header:
Fargocd.arnia-bfc.synaltic.app 141.94.169.202
Referrer-Policy
Critical: Missing Header:
Fargocd.arnia-bfc.synaltic.app 141.94.169.202
Permissions-Policy
Critical: Missing Header:
Bargocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Embedder-Policy
Info: Missing Header
Bargocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Opener-Policy
Info: Missing Header
Bargocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Resource-Policy
Info: Missing Header
Fwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Content-Security-Policy
Critical: Missing Header:
Fwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
X-Content-Type-Options
Critical: Missing Header:
Fwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Referrer-Policy
Critical: Missing Header:
Fwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Permissions-Policy
Critical: Missing Header:
Bwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Embedder-Policy
Info: Missing Header
Bwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Opener-Policy
Info: Missing Header
Bwww.argocd.arnia-bfc.synaltic.app 141.94.169.202
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns100.ovh.net, ns100.ovh.net, 2 Name Servers included in Delegation: dns100.ovh.net, ns100.ovh.net, 2 Name Servers included in 1 Zone definitions: dns100.ovh.net, ns100.ovh.net, 1 Name Servers listed in SOA.Primary: dns100.ovh.net.
AGood: Only one SOA.Primary Name Server found.: dns100.ovh.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns100.ovh.net.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns100.ovh.net, ns100.ovh.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: 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: net
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: ovh.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: FR
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 213., 1 different subnets (first two Bytes): 213.251., 2 different subnets (first three Bytes): 213.251.128., 213.251.188.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:41d0:, 1 different subnets (first three blocks): 2001:41d0:0001:, 2 different subnets (first four blocks): 2001:41d0:0001:1990:, 2001:41d0:0001:4a90:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

http://argocd.arnia-bfc.synaltic.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.94.169.202
503

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.argocd.arnia-bfc.synaltic.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.94.169.202
503

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AGood: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 2 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 1 with Cache-Control long enough, 3 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AInfo: No img element found, no alt attribute checked
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
https://www.argocd.arnia-bfc.synaltic.app/ 141.94.169.202
404
2.450 seconds
Warning: 404 needs more then one second
https://141.94.169.202/ 141.94.169.202
404
3.680 seconds
Warning: 404 needs more then one second
ADuration: 209100 milliseconds, 209.100 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
argocd.arnia-bfc.synaltic.app
141.94.169.202
443
Certificate/chain invalid
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
argocd.arnia-bfc.synaltic.app
141.94.169.202
443
Certificate/chain invalid
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=argocd.arnia-bfc.synaltic.app


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


www.argocd.arnia-bfc.synaltic.app
141.94.169.202
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

www.argocd.arnia-bfc.synaltic.app
141.94.169.202
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate

1CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co


141.94.169.202
141.94.169.202
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

141.94.169.202
141.94.169.202
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
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
Self signed certificate

1CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co

 

9. Certificates

1.
1.
CN=argocd.arnia-bfc.synaltic.app
29.08.2024
27.11.2024
5 days expired		argocd.arnia-bfc.synaltic.app - 1 entry
1.
1.
CN=argocd.arnia-bfc.synaltic.app
29.08.2024

27.11.2024
5 days expired


argocd.arnia-bfc.synaltic.app - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03F04BDED8D0B53986775FC057650C498284
Thumbprint:C246DC4EB0DBB782F5EF21E7B3C2AF793C44A1AB
SHA256 / Certificate:/jID/m6Ym5c+rO6X3YVv/mlL2tVilo7apu+aiWDawig=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):61fd8645f74eb00cdaa04d4ffebcaf53e6c4a8214683dbd1d79254faf2de83f2
SHA256 hex / Subject Public Key Information (SPKI):61fd8645f74eb00cdaa04d4ffebcaf53e6c4a8214683dbd1d79254faf2de83f2 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r10.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)


NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.


2.
CN=R10, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 831 days

2.
CN=R10, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 831 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:4BA85293F79A2FA273064BA8048D75D0
Thumbprint:00ABEFD055F9A9C784FFDEABD1DCDD8FED741436
SHA256 / Certificate:nXw/GqatKy7A1c8eJG+NmubLyf0HVa03u5dLHy+2A/M=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):Error find_SubjectPublicKeyInfo_in_Certificate - no result found
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)




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

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

04.06.2035
expires in 3836 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
24.10.2024
24.10.2025
expires in 326 days		ingress.local - 1 entry
2.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
24.10.2024

24.10.2025
expires in 326 days


ingress.local - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:5348D6FF7A8C7E7A4ECC5C2790D03455
Thumbprint:F05B8B96491DBB319C48A8337645CF8700BE5215
SHA256 / Certificate:8wCYmHC8GJLSr2jd2vKlFtsN0MceOH6o9lqYjwoIPw4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):fbe77c08274f2e06fd47254829e150d73eed4f4e0af181caae52102cc80cfc70
SHA256 hex / Subject Public Key Information (SPKI):fbe77c08274f2e06fd47254829e150d73eed4f4e0af181caae52102cc80cfc70 (is buggy, ignore the result)
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)


UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


3.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
19.11.2024
19.11.2025
expires in 352 days		ingress.local - 1 entry
3.
1.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
19.11.2024

19.11.2025
expires in 352 days


ingress.local - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0ACABBAB7F83FF7660B463178F58D04E
Thumbprint:02200018989AE65E54C0112CFBD6FE462186F5BA
SHA256 / Certificate:HQRdJGv0FRo/lGkH9ttbnk7e4/3egk9HPUjlKKb8NMI=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):997b637e2828abd7414696e8a87caa59f951160f1ee910020f06ad4a59bd5b3a
SHA256 hex / Subject Public Key Information (SPKI):997b637e2828abd7414696e8a87caa59f951160f1ee910020f06ad4a59bd5b3a (is buggy, ignore the result)
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)


UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


 

10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found

 

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://argocd.arnia-bfc.synaltic.app/
141.94.169.202		a

1

0


0
0
0


link
stylesheet
1
361 Bytes
0
1
0
0
0
0


link
other
2
3,179 Bytes
0
2
0
0
0
0


meta
other
2

0


0
0
0


script

2
635,646 Bytes
1
2
0
0
0
0

 

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsg∑Status
https://argocd.arnia-bfc.synaltic.app/
141.94.169.202
a

https://argoproj.github.io/argo-cd/cli_installation/


1
ok















link
icon
assets/favicon/favicon-16x16.png
200

1
ok
image/png
missing X-Content-Type-Options nosniff




No Cache-Control header
Wrong Compression (gzip): 984/956 Bytes








link
icon
assets/favicon/favicon-32x32.png
200

1
ok
image/png
missing X-Content-Type-Options nosniff




No Cache-Control header
Wrong Compression (gzip): 2195/2167 Bytes








link
stylesheet
assets/fonts.css
200

1
ok
text/css; charset=utf-8
missing X-Content-Type-Options nosniff




No Cache-Control - header
Compression (gzip): 361/2209 Bytes






local SRI possible, possible hash-values:

 

sha256-s4v7GHrFsMBOSULeDVdoi800amYYhVR3ZeD2RwAKdvY=
sha384-aHeHkQ2iHEm0b1XN2WtXbfUKZN0wYb02zBcwRkuQCPXDfrBVZeH+Npa1UcvAfeDh
sha512-Kw7jh6+OppCsAcT90iiOgaoWZCVIjCvrk6l9+1wwykuEXcIsYYwOVoRver2K7oBBPG+iaRP+af4DyOpEN/0LQw==

 

<link rel="stylesheet" href="assets/fonts.css" crossorigin="anonymous" integrity="sha256-s4v7GHrFsMBOSULeDVdoi800amYYhVR3ZeD2RwAKdvY=" />



meta
charset
 UTF-8


1
ok















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


1
ok















script
src
extensions.js
200

1
Problems with Content-Type - Header - see details
defer attribute found application/javascript
missing X-Content-Type-Options nosniff

This Combination of MediaType "application" and MediaSubType "javascript" is obsolete. Don't use it. See https://www.iana.org/assignments/media-types/media-types.xhtml to find a correct Combination. Use "text/javascript" instead.


No Cache-Control - header
23 Bytes






local SRI possible, possible hash-values:

 

sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
sha384-OLBgp1GsljhM2TJ+sbHjaiH9txEUvgdDTAzHv2P24donTt6/529l+9Ua0vFImLlb
sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==

 

<script src="extensions.js" crossorigin="anonymous" integrity="sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=" />



script
src
main.f14bff1ed334a13aa8c2.js
200

1
ok
defer attribute found text/javascript; charset=utf-8
missing X-Content-Type-Options nosniff




Cache-Control: public, max-age=31536000, immutable - with long duration found.
Compression (gzip): 635623/2479663 Bytes






local SRI possible, possible hash-values:

 

sha256-BptWE5dEBGyw42haQJSMacukprbQ6qH2Hz570Qb35fw=
sha384-rXNnQpY+37w4x9UBIPDx6AjWV/oGnZyYFrEzGzY7Xh+BB12Tq3J00s37u/v78iQt
sha512-uwUysQsRvRep56JTdR+KwqShSmfBDGft/IVL4lgCvlzdPd3I9AMBmhK4qLqnYfU9qvy81S6jhXGR1mIDre+dwQ==

 

<script src="main.f14bff1ed334a13aa8c2.js" crossorigin="anonymous" integrity="sha256-BptWE5dEBGyw42haQJSMacukprbQ6qH2Hz570Qb35fw=" />


 

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

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

Url used (first standard-https-result with http status 200): https://argocd.arnia-bfc.synaltic.app/

Summary

Good: No non-document-errors
1 errors
0 warnings

TypeMessagenum found
1.errorStray start tag script.1

Details


TypeMessage + Sample
1errorStray start tag script.

From line 1, column 724 to line 1, column 772

pp"></div></body><script defer="defer" src="extensions.js"></scri

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns100.ovh.net, ns100.ovh.net

 

QNr.DomainTypeNS used
1
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
2
dns100.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns13.ovh.net
2001:41d0:1:4a84::1, 213.251.188.132

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1, 213.251.128.131

Answer: ns13.ovh.net
2001:41d0:1:1984::1, 213.251.128.132

Answer: ns15.ovh.net
2001:41d0:1:1986::1, 213.251.128.134
3
ns100.ovh.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns10.ovh.net, dns11.ovh.net, dns12.ovh.net, dns13.ovh.net, dns15.ovh.net, ns10.ovh.net, ns11.ovh.net, ns12.ovh.net, ns13.ovh.net, ns15.ovh.net

Answer: dns10.ovh.net
2001:41d0:1:4a81::1, 213.251.188.129

Answer: dns11.ovh.net
2001:41d0:1:4a82::1, 213.251.188.130

Answer: dns12.ovh.net
2001:41d0:1:4a83::1, 213.251.188.131

Answer: dns13.ovh.net
2001:41d0:1:4a84::1, 213.251.188.132

Answer: dns15.ovh.net
2001:41d0:1:4a86::1, 213.251.188.134

Answer: ns10.ovh.net
2001:41d0:1:1981::1, 213.251.128.129

Answer: ns11.ovh.net
2001:41d0:1:1982::1, 213.251.128.130

Answer: ns12.ovh.net
2001:41d0:1:1983::1, 213.251.128.131

Answer: ns13.ovh.net
2001:41d0:1:1984::1, 213.251.128.132

Answer: ns15.ovh.net
2001:41d0:1:1986::1, 213.251.128.134
4
dns100.ovh.net: 213.251.188.144
A
dns10.ovh.net (2001:41d0:1:4a81::1)
5
dns100.ovh.net: 2001:41d0:1:4a90::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)
6
ns100.ovh.net: 213.251.128.144
A
dns10.ovh.net (2001:41d0:1:4a81::1)
7
ns100.ovh.net: 2001:41d0:1:1990::1
AAAA
dns10.ovh.net (2001:41d0:1:4a81::1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.argocd.arnia-bfc.synaltic.app
0

no CAA entry found
1
0
argocd.arnia-bfc.synaltic.app
0

no CAA entry found
1
0
arnia-bfc.synaltic.app
0

no CAA entry found
1
0
synaltic.app
0

no CAA entry found
1
0
app
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
arnia-bfc.synaltic.app

ok
1
0
argocd.arnia-bfc.synaltic.app

ok
1
0
www.argocd.arnia-bfc.synaltic.app

ok
1
0
_acme-challenge.argocd.arnia-bfc.synaltic.app

missing entry or wrong length
1
0
_acme-challenge.www.argocd.arnia-bfc.synaltic.app

missing entry or wrong length
1
0
_acme-challenge.argocd.arnia-bfc.synaltic.app.arnia-bfc.synaltic.app

 perhaps wrong
1
0
_acme-challenge.argocd.arnia-bfc.synaltic.app.argocd.arnia-bfc.synaltic.app

 perhaps wrong
1
0
_acme-challenge.www.argocd.arnia-bfc.synaltic.app.argocd.arnia-bfc.synaltic.app

 perhaps wrong
1
0
_acme-challenge.www.argocd.arnia-bfc.synaltic.app.www.argocd.arnia-bfc.synaltic.app

 perhaps wrong
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
argocd.arnia-bfc.synaltic.app
141.94.169.202
443
3 Ciphers40.47 sec
0 without, 3 FS
100.00 %
www.argocd.arnia-bfc.synaltic.app
141.94.169.202
443
3 Ciphers41.37 sec
0 without, 3 FS
100.00 %
Complete

2
6 Ciphers
3.00 Ciphers/Check		81.83 sec40.92 sec/Check
0 without, 6 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
argocd.arnia-bfc.synaltic.app
141.94.169.202
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
3 Ciphers, 40.47 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

www.argocd.arnia-bfc.synaltic.app
141.94.169.202
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
3 Ciphers, 41.37 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

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=b5bafbe1-6238-4d66-a6e0-bdd24afe64b9

 

Last Result: https://check-your-website.server-daten.de/?q=argocd.arnia-bfc.synaltic.app - 2024-11-29 17:22:06

 

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

 

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

 

 

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

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions