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

0 in Queue, 0 of max. 8 Checks (20:41:58)
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 |

 

B

 

Missing HSTS or Cookie-warnings

 

Checked:
19.01.2019 10:35:31

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
blog.ohanacruises.com
A
52.2.10.120
Hostname: ec2-52-2-10-120.compute-1.amazonaws.com
yes
1
0

AAAA

yes


www.blog.ohanacruises.com

Name Error
yes
1
0

 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






• Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16749, Flags 256






Public Key with Algorithm 8, KeyTag 19164, Flags 385






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






2 RRSIG RR to validate DNSKEY RR found






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






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






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






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






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



Zone: com

com
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






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






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 16883, Flags 256






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






Public Key with Algorithm 8, KeyTag 37490, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2019, 19:25:33 +, Signature-Inception: 12.01.2019, 19:20:33 +, KeyTag 30909, Signer-Name: com






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






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



Zone: ohanacruises.com

ohanacruises.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: blog.ohanacruises.com

blog.ohanacruises.com
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.blog.ohanacruises.com

www.blog.ohanacruises.com
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.blog.ohanacruises.com
•  ns17.domaincontrol.com

blog.ohanacruises.com
•  ns17.domaincontrol.com

ohanacruises.com
•  ns17.domaincontrol.com


•  ns18.domaincontrol.com

com
•  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

No SOA informations found. The feature is new (startet 2019-02-05), so recheck this domain.

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://blog.ohanacruises.com/
52.2.10.120
302
https://blog.ohanacruises.com/

0.226
A
Date: Sat, 19 Jan 2019 09:35:38 GMT
Server: Apache/2.4.34 (Amazon) OpenSSL/1.0.2k-fips PHP/5.6.38
Location: https://blog.ohanacruises.com/
Content-Length: 214
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://blog.ohanacruises.com/
52.2.10.120
200


2.613
B
Date: Sat, 19 Jan 2019 09:35:39 GMT
Server: Apache/2.4.34 (Amazon) OpenSSL/1.0.2k-fips PHP/5.6.38
Last-Modified: Sat, 19 Jan 2019 08:35:00 GMT
ETag: "238f7-57fcb80dbf883"
Accept-Ranges: bytes
Content-Length: 145655
Cache-Control: max-age=0
Expires: Sat, 19 Jan 2019 09:35:39 GMT
Vary: Accept-Encoding,Cookie,User-Agent
Referrer-Policy:
X-Powered-By: W3 Total Cache/0.9.7
Connection: close
Content-Type: text/html; charset=UTF-8

• http://blog.ohanacruises.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
52.2.10.120
302
https://blog.ohanacruises.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

0.203
A
Visible Content:
Date: Sat, 19 Jan 2019 09:35:41 GMT
Server: Apache/2.4.34 (Amazon) OpenSSL/1.0.2k-fips PHP/5.6.38
Location: https://blog.ohanacruises.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Length: 283
Connection: close
Content-Type: text/html; charset=iso-8859-1

• https://blog.ohanacruises.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404


6.643
A
Not Found
Visible Content:
Date: Sat, 19 Jan 2019 09:35:42 GMT
Server: Apache/2.4.34 (Amazon) OpenSSL/1.0.2k-fips PHP/5.6.38
X-Powered-By: W3 Total Cache/0.9.7
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Link: <https://blog.ohanacruises.com/wp-json/>; rel="https://api.w.org/"
Referrer-Policy:
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

 

7. Comments


1. General Results, most used to calculate the result

Aname "blog.ohanacruises.com" is subdomain, public suffix is "com", 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
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://blog.ohanacruises.com/ 52.2.10.120
302
https://blog.ohanacruises.com/
Correct redirect http - https with the same domain name
Bhttps://blog.ohanacruises.com/ 52.2.10.120
200

Missing HSTS-Header

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


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
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
https://blog.ohanacruises.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
6.643 seconds
Warning: 404 needs more then one second
ADuration: 16554 milliseconds, 16.554 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
blog.ohanacruises.com
52.2.10.120
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
blog.ohanacruises.com
52.2.10.120
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
not 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

 

9. Certificates

1.
1.
CN=blog.ohanacruises.com
19.01.2019
19.04.2019
2054 days expired		blog.ohanacruises.com - 1 entry
1.
1.
CN=blog.ohanacruises.com
19.01.2019

19.04.2019
2054 days expired


blog.ohanacruises.com - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:033542E562AB6BAC305B96E56FE9150F736B
Thumbprint:B54985A039EDC089B91CDE7ED3022D800F65BF4B
SHA256 / Certificate:jUhqyXs3IXVKGEZt3BBqCsIRzSA4zOOQoLLRc0E1PhQ=
SHA256 hex / Cert (DANE * 0 1):8d486ac97b3721754a18466ddc106a0ac211cd2038cce390a0b2d17341353e14
SHA256 hex / PublicKey (DANE * 1 1):127e49069345245fa6bd5faf3bd66d36275caae82f20fb1a337bfda94e387291
SHA256 hex / Subject Public Key Information (SPKI):127e49069345245fa6bd5faf3bd66d36275caae82f20fb1a337bfda94e387291
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
1356 days expired

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

17.03.2021
1356 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
1159 days expired

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

30.09.2021
1159 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)

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.

 

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

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.

 

11. Html-Content - Entries

No Html-Content informations found. The feature is new (startet 2019-01-22), so recheck this domain.

 

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
blog.ohanacruises.com
0

no CAA entry found
1
0
ohanacruises.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
blog.ohanacruises.com

ok
1
0
_acme-challenge.blog.ohanacruises.com

Name Error - The domain name does not exist
1
0
_acme-challenge.blog.ohanacruises.com.blog.ohanacruises.com

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=4b944e28-717c-46b2-b627-828b174b943b

 

Last Result: https://check-your-website.server-daten.de/?q=blog.ohanacruises.com - 2019-01-19 10:35:31

 

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

 

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

 

 

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

 

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

 

 

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