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

0 in Queue, 0 of max. 8 Checks (13:11:29)
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 |

 

A

 

Top config

 

Checked:
17.06.2019 15:42:51

 

Older results

 

A - 26.05.2019 09:19:39
A - 26.05.2019 09:15:04

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
boldos.ddns.net
A
86.241.60.183
La Gonfriere/Normandy/FR
Hostname: lfbn-1-2630-183.w86-241.abo.wanadoo.fr
yes
1
0

AAAA

yes


www.boldos.ddns.net

Name Error
yes
1
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• 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 25266, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

net
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.06.2019, 05:00:00 +, Signature-Inception: 17.06.2019, 04:00:00 +, KeyTag 25266, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 2129, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2019, 15:38:57 +, Signature-Inception: 09.06.2019, 15:33:57 +, KeyTag 35886, Signer-Name: net






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






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



Zone: ddns.net

ddns.net
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 "e51o1pdujacqu01c7sqi76kt359m7agm" between the hashed NSEC3-owner "e51bv4d4bjgchtkajq9ma0d2h40e40dq" and the hashed NextOwner "e51u896vsufh8m1l4q9ihevtrl9ne1r7". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e51bv4d4bjgchtkajq9ma0d2h40e40dq.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2019, 05:45:37 +, Signature-Inception: 17.06.2019, 04:35:37 +, KeyTag 2129, Signer-Name: net






0 DNSKEY RR found









Zone: boldos.ddns.net

boldos.ddns.net
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.boldos.ddns.net

www.boldos.ddns.net
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.boldos.ddns.net
•  nf1.no-ip.com

boldos.ddns.net
•  nf1.no-ip.com / f2.fra.hv.as29997.net
194.62.182.53
Dearing/Kansas/US		•

• 
2a07:dc00:1820::53
Dearing/Kansas/US		•
ddns.net
•  nf1.no-ip.com / f2.fra.hv.as29997.net
•

•  nf2.no-ip.com / f1.ams.hv.as29997.net
•

•  nf3.no-ip.com / f1.ams.vr.as29997.net
•

•  nf4.no-ip.com / f1.ams.vr.as29997.net
•
net
•  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
•

 

4. SOA-Entries


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


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


Domain:ddns.net
Zone-Name:
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2252441396
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:1


Domain:ddns.net
Zone-Name:
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2252442593
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:1


Domain:ddns.net
Zone-Name:
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2252442813
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:2


Domain:boldos.ddns.net
Zone-Name:
Primary:nf1.no-ip.com
Mail:hostmaster.no-ip.com
Serial:2252442593
Refresh:10800
Retry:1800
Expire:604800
TTL:1800
num Entries:2


Domain:www.boldos.ddns.net
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://boldos.ddns.net/
86.241.60.183
301
https://boldos.ddns.net/

0.120
A
Date: Mon, 17 Jun 2019 13:43:30 GMT
Server: Apache/2.4.25
Location: https://boldos.ddns.net/
Content-Length: 232
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://boldos.ddns.net/
86.241.60.183
301
https://boldos.ddns.net/index.html/

1.027
A
Date: Mon, 17 Jun 2019 13:43:31 GMT
Server: Apache/2.4.25
Strict-Transport-Security: max-age=15768000
X-Frame-Options: SAMEORIGIN
Location: https://boldos.ddns.net/index.html/
Content-Length: 243
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://boldos.ddns.net/index.html/

200


0.710
A
Date: Mon, 17 Jun 2019 13:43:32 GMT
Server: Apache/2.4.25
Strict-Transport-Security: max-age=15768000
X-Frame-Options: SAMEORIGIN
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Vary: Accept-Encoding
Set-Cookie: PHPSESSID=qvj2p9d8bouimlv13iq9uvgke7; Path=/; Domain=boldos.ddns.net; HttpOnly; Secure
Content-Security-Policy: frame-src 'self' boldos.ddns.net
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
Content-Length: 4696
Connection: close
Content-Type: text/html; charset=utf-8

• http://boldos.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
86.241.60.183
301
https://boldos.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.123
A
Visible Content:
Date: Mon, 17 Jun 2019 13:43:32 GMT
Server: Apache/2.4.25
Location: https://boldos.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 301
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://boldos.ddns.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


0.633
A
Not Found
Visible Content:
Date: Mon, 17 Jun 2019 13:43:33 GMT
Server: Apache/2.4.25
Strict-Transport-Security: max-age=15768000
X-Frame-Options: SAMEORIGIN
Content-Length: 267
Connection: close
Content-Type: text/html; charset=iso-8859-1

 

7. Comments


1. General Results, most used to calculate the result

Aname "boldos.ddns.net" is domain, public suffix is "ddns.net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Ahttps://boldos.ddns.net/ 86.241.60.183
301
https://boldos.ddns.net/index.html/
Correct redirect https to https
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every cookie sent via https is marked as secure
AGood: every https has a Strict Transport Security Header
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://boldos.ddns.net/ 86.241.60.183
301
https://boldos.ddns.net/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found

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


3. DNS- and NameServer - Checks

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
Nameserver doesn't pass all EDNS-Checks: nf1.no-ip.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

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

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
boldos.ddns.net
boldos.ddns.net
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
supported
ok
boldos.ddns.net
boldos.ddns.net
443
ok
Tls12

DiffieHellman
2048
Aes128
128
Sha256
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=boldos.ddns.net


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


boldos.ddns.net
86.241.60.183
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
supported
ok

boldos.ddns.net
86.241.60.183
443
ok
Tls12

DiffieHellman
2048
Aes128
128
Sha256
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=boldos.ddns.net


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=boldos.ddns.net
08.04.2019
07.07.2019
1979 days expired		boldos.ddns.net - 1 entry
1.
1.
CN=boldos.ddns.net
08.04.2019

07.07.2019
1979 days expired


boldos.ddns.net - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:03E8C6AC6FFE23F2E6913FCDB3EA0B6F336C
Thumbprint:BB4FC1AC0A2767A81731DDF0A089938463DAC989
SHA256 / Certificate:faRpXfMSk+mcZqD2zHTQpp4xvIQfqUic5BhFN9apR+M=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d6ac5d4dca011738c2db9b20fcc089bfb6b565e910520a9cc70ae2eb2c452027
SHA256 hex / Subject Public Key Information (SPKI):d6ac5d4dca011738c2db9b20fcc089bfb6b565e910520a9cc70ae2eb2c452027
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1360 days expired

2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1360 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1163 days expired

3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1163 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:




 

10. Last Certificates - Certificate Transparency Log Check

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

Small Code Update - wait one minute

 

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

No data found or small Code-update

 

Details

Small Code Update - wait one minute

 

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.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

 

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
boldos.ddns.net
0

no CAA entry found
1
0
ddns.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
boldos.ddns.net

ok
1
0
_acme-challenge.boldos.ddns.net

Name Error - The domain name does not exist
1
0
_acme-challenge.boldos.ddns.net.boldos.ddns.net

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

 

 

Permalink: https://check-your-website.server-daten.de/?i=b7530900-4b56-4ea8-918a-377b64e04ddd

 

Last Result: https://check-your-website.server-daten.de/?q=boldos.ddns.net - 2019-06-17 15:42:51

 

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

 

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

 

 

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