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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
24.11.2022 14:57:44


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ewoud-weijmans.nl
A
87.210.240.135
Eindhoven/North Brabant/Netherlands (NL) - T-Mobile Thuis WBA Services
Hostname: 135-240-210-87.ftth.glasoperator.nl
yes
1
0

AAAA

yes


www.ewoud-weijmans.nl
A
87.210.240.135
Eindhoven/North Brabant/Netherlands (NL) - T-Mobile Thuis WBA Services
Hostname: 135-240-210-87.ftth.glasoperator.nl
yes
1
0

AAAA

yes


*.ewoud-weijmans.nl
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



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



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 18733, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 34112, DigestType 2 and Digest PFtfmzVXRVxQdRqb6evpI4yI4Z9fB/kwl2kXtRuVzSI=



1 RRSIG RR to validate DS RR found



RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.12.2022, 05:00:00 +, Signature-Inception: 24.11.2022, 04:00:00 +, KeyTag 18733, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3786, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner nl., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 03.12.2022, 21:27:28 +, Signature-Inception: 20.11.2022, 01:08:23 +, KeyTag 34112, Signer-Name: nl



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



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

Zone: ewoud-weijmans.nl
ewoud-weijmans.nl
2 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 6211, DigestType 2 and Digest j55PbG0Du6bUOV9QhGt5tF4Pu/pvh1ZRU6S1VaLOr7s=



DS with Algorithm 13, KeyTag 47590, DigestType 2 and Digest ap3KPPQV076B6eT1WZ7n0G3SHUFF93AVRQWuG10+x3c=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ewoud-weijmans.nl., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.12.2022, 16:20:09 +, Signature-Inception: 21.11.2022, 12:38:41 +, KeyTag 3786, Signer-Name: nl



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



2 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 6211, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 47590, Signer-Name: ewoud-weijmans.nl



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 6211, DigestType 2 and Digest "j55PbG0Du6bUOV9QhGt5tF4Pu/pvh1ZRU6S1VaLOr7s=" validates local Key with the same values



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



RRSIG Type 1 validates the A - Result: 87.210.240.135
Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



RRSIG Type 16 validates the TXT - Result: v=spf1 a mx include:_spf.transip.email ~all
Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



CNAME-Query sends a valid NSEC RR as result with the query name "ewoud-weijmans.nl" equal the NSEC-owner "ewoud-weijmans.nl" and the NextOwner "_dmarc.ewoud-weijmans.nl". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "ewoud-weijmans.nl" equal the NSEC-owner "ewoud-weijmans.nl" and the NextOwner "_dmarc.ewoud-weijmans.nl". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.ewoud-weijmans.nl) sends a valid NSEC RR as result with the owner name ewoud-weijmans.nl. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "ewoud-weijmans.nl" and the NextOwner "_dmarc.ewoud-weijmans.nl". So that NSEC confirms the not-existence of the Wildcard expansion.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NXDomain-Proof required and found.



TLSA-Query (_443._tcp.ewoud-weijmans.nl) sends a valid NSEC RR as result with the query name "_443._tcp.ewoud-weijmans.nl" between the NSEC-owner "transip-C._domainkey.ewoud-weijmans.nl" and the NextOwner "ftp.ewoud-weijmans.nl". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.ewoud-weijmans.nl) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.ewoud-weijmans.nl" between the NSEC-owner "transip-C._domainkey.ewoud-weijmans.nl" and the NextOwner "ftp.ewoud-weijmans.nl". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: CNAME, RRSIG, NSEC Validated: RRSIG-Owner transip-c._domainkey.ewoud-weijmans.nl., Algorithm: 13, 4 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "ewoud-weijmans.nl" equal the NSEC-owner "ewoud-weijmans.nl" and the NextOwner "_dmarc.ewoud-weijmans.nl". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner ewoud-weijmans.nl., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.

Zone: www.ewoud-weijmans.nl
www.ewoud-weijmans.nl
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC



RRSIG Type 1 validates the A - Result: 87.210.240.135
Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



CNAME-Query sends a valid NSEC RR as result with the query name "www.ewoud-weijmans.nl" equal the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "www.ewoud-weijmans.nl" equal the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "www.ewoud-weijmans.nl" equal the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.ewoud-weijmans.nl) sends a valid NSEC RR as result with the owner name www.ewoud-weijmans.nl. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.ewoud-weijmans.nl) sends a valid NSEC RR as result with the query name "_443._tcp.www.ewoud-weijmans.nl" between the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.www.ewoud-weijmans.nl) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.www.ewoud-weijmans.nl" between the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "www.ewoud-weijmans.nl" equal the NSEC-owner "www.ewoud-weijmans.nl" and the NextOwner "x-transip-mail-auth.ewoud-weijmans.nl". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner www.ewoud-weijmans.nl., Algorithm: 13, 3 Labels, original TTL: 86400 sec, Signature-expiration: 29.12.2022, 12:44:12 +, Signature-Inception: 24.11.2022, 12:44:12 +, KeyTag 6211, Signer-Name: ewoud-weijmans.nl



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.ewoud-weijmans.nl
  87.210.240.135

ewoud-weijmans.nl
  87.210.240.135


  ns1.i24.host
37.97.166.105
Amsterdam/North Holland/Netherlands (NL) - Signet B.V.


 
2a01:7c8:aac0:1cd::1
Leiden/South Holland/Netherlands (NL) - TransIP B.V. Amsterdam network


  ns2.i24.host
185.10.49.136
Amsterdam/North Holland/Netherlands (NL) - TransIP BV


 
2a01:7c8:aaaf:1a5::1
Leiden/South Holland/Netherlands (NL) - TransIP B.V. Amsterdam network

nl
  ns1.dns.nl / eqx-fr2-ns01-82


  ns2.dns.nl / s2.sof


  ns3.dns.nl / tld-all-fam1@53024


  ns4.dns.nl / FRA2


4. SOA-Entries


Domain:nl
Zone-Name:nl
Primary:ns1.dns.nl
Mail:hostmaster.domain-registry.nl
Serial:2022112426
Refresh:3600
Retry:600
Expire:2419200
TTL:600
num Entries:1


Domain:nl
Zone-Name:nl
Primary:ns1.dns.nl
Mail:hostmaster.domain-registry.nl
Serial:2022112427
Refresh:3600
Retry:600
Expire:2419200
TTL:600
num Entries:3


Domain:ewoud-weijmans.nl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:ewoud-weijmans.nl
Zone-Name:ewoud-weijmans.nl
Primary:87.210.240.135
Mail:hostmaster.ewoud-weijmans.nl
Serial:2022112409
Refresh:3600
Retry:3600
Expire:1209600
TTL:86400
num Entries:4


Domain:www.ewoud-weijmans.nl
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://ewoud-weijmans.nl/, address used: https://ewoud-weijmans.nl/, Screenshot created 2022-11-24 14:59:46 +00:0 url is insecure, certificate invalid

Mobil (412px x 732px)

154 milliseconds

Screenshot mobile - https://ewoud-weijmans.nl/
Mobil + Landscape (732px x 412px)

160 milliseconds

Screenshot mobile landscape - https://ewoud-weijmans.nl/
Screen (1280px x 1680px)

320 milliseconds

Screenshot Desktop - https://ewoud-weijmans.nl/

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://ewoud-weijmans.nl/
87.210.240.135 GZip used - 246 / 468 - 47.44 %
200

Html is minified: 377.42 %
0.063
H
small visible content (num chars: 49)
<!DOCTYPE html> Ewoud Weijmans Under Construction
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:12 GMT
Content-Type: text/html
Last-Modified: Thu, 24 Nov 2022 12:44:50 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637f6742-1d4"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip

• http://www.ewoud-weijmans.nl/
87.210.240.135 GZip used - 246 / 468 - 47.44 %
200

Html is minified: 377.42 %
0.060
H
small visible content (num chars: 49)
<!DOCTYPE html> Ewoud Weijmans Under Construction
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:12 GMT
Content-Type: text/html
Last-Modified: Thu, 24 Nov 2022 12:44:50 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637f6742-1d4"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip

• https://ewoud-weijmans.nl/
87.210.240.135 GZip used - 246 / 468 - 47.44 %
Inline-JavaScript (∑/total): 1/272 Inline-CSS (∑/total): 0/0
200

Html is minified: 377.42 %
2.350
N
Certificate error: RemoteCertificateChainErrors
small visible content (num chars: 49)
<!DOCTYPE html> Ewoud Weijmans Under Construction
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:13 GMT
Content-Type: text/html
Last-Modified: Thu, 24 Nov 2022 12:44:50 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637f6742-1d4"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip

• https://www.ewoud-weijmans.nl/
87.210.240.135 GZip used - 246 / 468 - 47.44 %
Inline-JavaScript (∑/total): 1/272 Inline-CSS (∑/total): 0/0
200

Html is minified: 377.42 %
2.284
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 49)
<!DOCTYPE html> Ewoud Weijmans Under Construction
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:16 GMT
Content-Type: text/html
Last-Modified: Thu, 24 Nov 2022 12:44:50 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637f6742-1d4"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip

• http://ewoud-weijmans.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.210.240.135 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.063
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:20 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• http://www.ewoud-weijmans.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.210.240.135 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.113
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:20 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://87.210.240.135/
87.210.240.135 GZip used - 246 / 468 - 47.44 %
Inline-JavaScript (∑/total): 1/272 Inline-CSS (∑/total): 0/0
200

Html is minified: 377.42 %
2.266
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 49)
<!DOCTYPE html> Ewoud Weijmans Under Construction
Server: nginx/1.18.0 (Ubuntu)
Date: Thu, 24 Nov 2022 13:58:20 GMT
Content-Type: text/html
Last-Modified: Thu, 24 Nov 2022 12:44:50 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637f6742-1d4"
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Encoding: gzip

7. Comments


1. General Results, most used to calculate the result

Aname "ewoud-weijmans.nl" is domain, public suffix is ".nl", top-level-domain is ".nl", top-level-domain-type is "country-code", Country is Netherlands (the), tld-manager is "SIDN (Stichting Internet Domeinregistratie Nederland)", num .nl-domains preloaded: 4513 (complete: 210599)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: ewoud-weijmans.nl has only one ip address.
Warning: Only one ip address found: www.ewoud-weijmans.nl 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: ewoud-weijmans.nl 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.ewoud-weijmans.nl has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. 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):0 complete Content-Type - header (7 urls)
http://ewoud-weijmans.nl/ 87.210.240.135


Url with incomplete Content-Type - header - missing charset
http://www.ewoud-weijmans.nl/ 87.210.240.135


Url with incomplete Content-Type - header - missing charset
https://ewoud-weijmans.nl/ 87.210.240.135


Url with incomplete Content-Type - header - missing charset
https://www.ewoud-weijmans.nl/ 87.210.240.135


Url with incomplete Content-Type - header - missing charset
http://ewoud-weijmans.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.210.240.135


Url with incomplete Content-Type - header - missing charset
http://www.ewoud-weijmans.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 87.210.240.135


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


Url with incomplete Content-Type - header - missing charset
Bhttps://ewoud-weijmans.nl/ 87.210.240.135
200

Missing HSTS-Header
Bhttps://www.ewoud-weijmans.nl/ 87.210.240.135
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Nhttps://ewoud-weijmans.nl/ 87.210.240.135
200

Error - Certificate isn't trusted, RemoteCertificateChainErrors
Nhttps://www.ewoud-weijmans.nl/ 87.210.240.135
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nhttps://87.210.240.135/ 87.210.240.135
200

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 the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain ewoud-weijmans.nl, 1 ip addresses, 1 different http results.
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.ewoud-weijmans.nl, 1 ip addresses, 1 different http results.
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.ewoud-weijmans.nl

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

Aewoud-weijmans.nl 87.210.240.135
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
A
X-Frame-Options
Ok: Header without syntax errors found: DENY
B

Info: Header is deprecated. May not longer work in modern browsers. DENY. 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; mode=block
B

Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
Awww.ewoud-weijmans.nl 87.210.240.135
X-Content-Type-Options
Ok: Header without syntax errors found: nosniff
A
X-Frame-Options
Ok: Header without syntax errors found: DENY
B

Info: Header is deprecated. May not longer work in modern browsers. DENY. 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; mode=block
B

Info: Header is deprecated. May not longer work in modern browsers. 1; mode=block
Fewoud-weijmans.nl 87.210.240.135
Content-Security-Policy
Critical: Missing Header:
Fewoud-weijmans.nl 87.210.240.135
Referrer-Policy
Critical: Missing Header:
Fewoud-weijmans.nl 87.210.240.135
Permissions-Policy
Critical: Missing Header:
Fwww.ewoud-weijmans.nl 87.210.240.135
Content-Security-Policy
Critical: Missing Header:
Fwww.ewoud-weijmans.nl 87.210.240.135
Referrer-Policy
Critical: Missing Header:
Fwww.ewoud-weijmans.nl 87.210.240.135
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.i24.host (2a01:7c8:aac0:1cd::1, 37.97.166.105), ns2.i24.host (185.10.49.136, 2a01:7c8:aaaf:1a5::1)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: 87.210.240.135, ns1.i24.host, ns2.i24.host, 2 Name Servers included in Delegation: ns1.i24.host, ns2.i24.host, 1 Name Servers included in 2 Zone definitions: 87.210.240.135, 1 Name Servers listed in SOA.Primary: 87.210.240.135.
AGood: Only one SOA.Primary Name Server found.: 87.210.240.135.
Error: SOA.Primary Name Server not included in the delegation set.: 87.210.240.135.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.i24.host (37.97.166.105): Delegation: ns1.i24.host, ns2.i24.host, Zone: 87.210.240.135. Name Servers defined in Delegation, missing in Zone: ns1.i24.host, ns2.i24.host.Name Servers defined in Zone, missing in Delegation: 87.210.240.135.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.i24.host (2a01:7c8:aac0:1cd::1): Delegation: ns1.i24.host, ns2.i24.host, Zone: 87.210.240.135. Name Servers defined in Delegation, missing in Zone: ns1.i24.host, ns2.i24.host.Name Servers defined in Zone, missing in Delegation: 87.210.240.135.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.i24.host (185.10.49.136): Delegation: ns1.i24.host, ns2.i24.host, Zone: 87.210.240.135. Name Servers defined in Delegation, missing in Zone: ns1.i24.host, ns2.i24.host.Name Servers defined in Zone, missing in Delegation: 87.210.240.135.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.i24.host (2a01:7c8:aaaf:1a5::1): Delegation: ns1.i24.host, ns2.i24.host, Zone: 87.210.240.135. Name Servers defined in Delegation, missing in Zone: ns1.i24.host, ns2.i24.host.Name Servers defined in Zone, missing in Delegation: 87.210.240.135.


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

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: i24.host
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: NL
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 185., 37., 2 different subnets (first two Bytes): 185.10., 37.97., 2 different subnets (first three Bytes): 185.10.49., 37.97.166.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a01:, 1 different subnets (first two blocks): 2a01:07c8:, 2 different subnets (first three blocks): 2a01:07c8:aaaf:, 2a01:07c8:aac0:, 2 different subnets (first four blocks): 2a01:07c8:aaaf:01a5:, 2a01:07c8:aac0:01cd:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: 87.210.240.135: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: 87.210.240.135: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
https://ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://www.ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://87.210.240.135/ 87.210.240.135
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://www.ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://87.210.240.135/ 87.210.240.135
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://www.ewoud-weijmans.nl/ 87.210.240.135
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://87.210.240.135/ 87.210.240.135
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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
ADuration: 132530 milliseconds, 132.530 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
ewoud-weijmans.nl
87.210.240.135
443
Certificate/chain invalid
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
ewoud-weijmans.nl
87.210.240.135
443
Certificate/chain invalid
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=ewoud-weijmans.nl, O=Ewoud Weijmans, L=Eindhoven, C=NL, emailAddress=mongoosh.motion@gmail.com


www.ewoud-weijmans.nl
87.210.240.135
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok

www.ewoud-weijmans.nl
87.210.240.135
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=ewoud-weijmans.nl, O=Ewoud Weijmans, L=Eindhoven, C=NL, emailAddress=mongoosh.motion@gmail.com


87.210.240.135
87.210.240.135
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok

87.210.240.135
87.210.240.135
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
384
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=ewoud-weijmans.nl, O=Ewoud Weijmans, L=Eindhoven, C=NL, emailAddress=mongoosh.motion@gmail.com


9. Certificates

1.
1.
E=mongoosh.motion@gmail.com, CN=ewoud-weijmans.nl, O=Ewoud Weijmans, L=Eindhoven, S=Brabant, C=NL
24.11.2022
24.11.2023
expires in 363 days

1.
1.
E=mongoosh.motion@gmail.com, CN=ewoud-weijmans.nl, O=Ewoud Weijmans, L=Eindhoven, S=Brabant, C=NL
24.11.2022

24.11.2023
expires in 363 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:34A573DDFCBC36D24BA038EAB0510A09AC4757E2
Thumbprint:04B06A633A49C70F20DD702D781C280E2276AD0F
SHA256 / Certificate:uMtuY9j3bcpoixuSSUuNV5FQLNX1bnu73So5DHo7GlY=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):ae6aafa1a7a0b18ccff5ede067c6aab6e41a61b769dcb95e5983fbdfdb847d18
SHA256 hex / Subject Public Key Information (SPKI):ae6aafa1a7a0b18ccff5ede067c6aab6e41a61b769dcb95e5983fbdfdb847d18 (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:

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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
1
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4450423546
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 13:08:03
2023-02-19 13:08:02
ewoud-weijmans.nl, www.ewoud-weijmans.nl - 2 entries
duplicate nr. 1


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

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
1 /0 new
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8029534479
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-21 12:08:03
2023-02-19 12:08:02
ewoud-weijmans.nl, www.ewoud-weijmans.nl
2 entries
duplicate nr. 1


11. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://ewoud-weijmans.nl/
87.210.240.135
meta
other
1

0


0
0
0

https://www.ewoud-weijmans.nl/
87.210.240.135
meta
other
1

0


0
0
0

https://87.210.240.135/
87.210.240.135
meta
other
1

0


0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://ewoud-weijmans.nl/
87.210.240.135
meta

utf-8


1
ok







https://www.ewoud-weijmans.nl/
87.210.240.135
meta

utf-8


1
ok







https://87.210.240.135/
87.210.240.135
meta

utf-8


1
ok








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.i24.host, ns2.i24.host

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

Answer: a.nic.host, b.nic.host, e.nic.host, f.nic.host
2
ns1.i24.host: 2a01:7c8:aac0:1cd::1, 37.97.166.105
NS
a.nic.host (2001:67c:13cc::1:53)

Answer: ns2.i24.host
185.10.49.136, 2a01:7c8:aaaf:1a5::1


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.ewoud-weijmans.nl
0

no CAA entry found
1
0
ewoud-weijmans.nl
0

no CAA entry found
1
0
nl
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ewoud-weijmans.nl
v=spf1 a mx include:_spf.transip.email ~all
ok
1
0
www.ewoud-weijmans.nl

ok
1
0
_acme-challenge.ewoud-weijmans.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ewoud-weijmans.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.ewoud-weijmans.nl.ewoud-weijmans.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ewoud-weijmans.nl.ewoud-weijmans.nl

Name Error - The domain name does not exist
1
0
_acme-challenge.www.ewoud-weijmans.nl.www.ewoud-weijmans.nl

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

ewoud-weijmans.nl
10
87.210.240.135
0
1
ok


CNAME



-3
0
ok

_dmarc
TXT
_dmarc.ewoud-weijmans.nl

v=DMARC1;p=quarantine; sp=none; rua=mailto:dmarc@i24.host
0
1
ok



16. Cipher Suites

DomainIPPortCipher (OpenSsl / IANA)
ewoud-weijmans.nl
87.210.240.135
443
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 27.93 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ECDH
RSA
AESGCM(256)
AEAD



ECDHE-RSA-AES256-SHA384
(Weak)
TLSv1.2
0xC0,0x28
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
ECDH
RSA
AES(256)
SHA384
www.ewoud-weijmans.nl
87.210.240.135
443
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 29.14 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ECDH
RSA
AESGCM(256)
AEAD



ECDHE-RSA-AES256-SHA384
(Weak)
TLSv1.2
0xC0,0x28
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
ECDH
RSA
AES(256)
SHA384


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=d9eb7be8-ec0f-4ded-8107-e53ab3096d6a


Last Result: https://check-your-website.server-daten.de/?q=ewoud-weijmans.nl - 2022-11-24 14:57:44


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

<a href="https://check-your-website.server-daten.de/?q=ewoud-weijmans.nl" target="_blank">Check this Site: ewoud-weijmans.nl</a>

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