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




D

Wrong redirect http ⇒ http

Checked:
12.06.2019 20:26:23


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
seline.app
A
70.35.199.155
/US
No Hostname found
yes
1
0

AAAA

yes


www.seline.app
A
70.35.199.155
/US
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



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: app
app
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.06.2019, 17:00:00, Signature-Inception: 12.06.2019, 16: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 23684, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 63243, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 02.07.2019, 00:40:32, Signature-Inception: 10.06.2019, 00:40:32, 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: seline.app
seline.app
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.07.2019, 00:40:32, Signature-Inception: 10.06.2019, 00:40:32, KeyTag 63243, Signer-Name: app



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 57366, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 03.07.2019, 12:04:38, Signature-Inception: 11.06.2019, 12:04:38, KeyTag 45572, Signer-Name: seline.app



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



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



RRSIG Type 1, expiration 2019-07-03 12:04:38 validates the A - Result: 70.35.199.155



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the CNAME RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the TXT RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the AAAA RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the TLSA RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the CAA RR

Zone: www.seline.app
www.seline.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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



RRSIG Type 1, expiration 2019-07-03 12:04:38 validates the A - Result: 70.35.199.155



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the CNAME RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the TXT RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the AAAA RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the TLSA RR



RRSIG Type 50, expiration 2019-07-03 12:04:38 validates the NSEC3 RR that proves the not-existence of the CAA RR


3. Name Servers

DomainNameserverNS-IP
www.seline.app
  ns-cloud-b1.googledomains.com

seline.app
  ns-cloud-b1.googledomains.com
216.239.32.107
Bellevue/Nebraska/US


 
2001:4860:4802:32::6b
Mountain View/California/US


  ns-cloud-b2.googledomains.com
216.239.34.107
Bellevue/Nebraska/US


 
2001:4860:4802:34::6b
Mountain View/California/US


  ns-cloud-b3.googledomains.com
216.239.36.107
Bellevue/Nebraska/US


 
2001:4860:4802:36::6b
Mountain View/California/US


  ns-cloud-b4.googledomains.com
216.239.38.107
Bellevue/Nebraska/US


 
2001:4860:4802:38::6b
Mountain View/California/US

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
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:seline.app
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:4
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:www.seline.app
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:4
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:1


5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://seline.app/
70.35.199.155
301
https://seline.app/
0.267
A
Server: nginx
Date: Wed, 12 Jun 2019 18:27:07 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 227
Connection: close
Location: https://seline.app/

• http://www.seline.app/
70.35.199.155
301
http://seline.app/
0.266
D
Server: nginx
Date: Wed, 12 Jun 2019 18:27:07 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: http://seline.app/

• https://www.seline.app/
70.35.199.155
301
https://seline.app/
1.237
B
Server: nginx
Date: Wed, 12 Jun 2019 18:27:09 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://seline.app/

• https://seline.app/
70.35.199.155
200

1.500
B
Server: nginx
Date: Wed, 12 Jun 2019 18:27:08 GMT
Content-Type: text/html
Content-Length: 195
Connection: close
X-Accel-Version: 0.01
Last-Modified: Sun, 31 Mar 2019 14:37:12 GMT
ETag: "c3-58564d6ef353d"
Accept-Ranges: bytes
X-Powered-By: PleskLin

• http://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
70.35.199.155
301
https://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.267
A
Visible Content:
Server: nginx
Date: Wed, 12 Jun 2019 18:27:10 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 296
Connection: close
Location: https://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
70.35.199.155
301
http://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
0.264
D
Visible Content:
Server: nginx
Date: Wed, 12 Jun 2019 18:27:10 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: http://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• https://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

404

1.104
A
Not Found
Visible Content:
Server: nginx
Date: Wed, 12 Jun 2019 18:27:11 GMT
Content-Type: text/html
Content-Length: 1020
Connection: close
Last-Modified: Sun, 31 Mar 2019 13:34:21 GMT
ETag: "3fc-58563f62c22d8"
Accept-Ranges: bytes
X-Powered-By: PleskLin

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "seline.app" is domain, public suffix is "app", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc."
Agood: All ip addresses are public addresses
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
AExcellent: Domain is in 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 (2 urls)
https://seline.app/ 70.35.199.155


Url with incomplete Content-Type - header - missing charset
https://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de


Url with incomplete Content-Type - header - missing charset
Ahttp://seline.app/ 70.35.199.155
301
https://seline.app/
correct redirect http - https with the same domain name
Bhttps://seline.app/ 70.35.199.155
200

Missing HSTS-Header
Bhttps://www.seline.app/ 70.35.199.155
301

Missing HSTS-Header
Dhttp://www.seline.app/ 70.35.199.155
301
http://seline.app/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 70.35.199.155
301
http://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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.
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://seline.app/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
1.104 seconds
Warning: 404 needs more then one second
ADuration: 51494 milliseconds, 51.494 seconds


7. Connections (http/2- and additional Tls.1.0/1.1/1.2 checks are BETA)

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
seline.app
70.35.199.155
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
seline.app
70.35.199.155
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
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 (complete)
1CN=seline.app

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
www.seline.app
70.35.199.155
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
www.seline.app
70.35.199.155
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
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 (complete)
1CN=seline.app

2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
seline.app
seline.app
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
seline.app
seline.app
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
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 (complete)
1CN=seline.app

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


8. Certificates

1.
1.
CN=seline.app
31.03.2019
29.06.2019
142 days expired
seline.app, www.seline.app - 2 entries
1.
1.
CN=seline.app
31.03.2019

29.06.2019
142 days expired
seline.app, www.seline.app - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0497BF16AFB1CE4AB22F99A6151A4EAD0103
Thumbprint:5AB4AEE22404D8A6E5F6175F6FD26140C64D35A9
SHA256 / Certificate:v6MyXaoPsnEDSeQcm7JMrVPWgpUCW+5PYzLR7JCKtHs=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):997a9eaed6335a127adcb02ea216c633bb3fc7451c7f0cc152c279b8dff73e3c
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 485 days


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

17.03.2021
expires in 485 days


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
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 682 days


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

30.09.2021
expires in 682 days


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
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no



9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
839492403
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-31 12:43:22
2019-06-29 12:43:22
seline.app, www.seline.app - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow.

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1341110196
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-31 10:43:22
2019-06-29 10:43:22
seline.app, www.seline.app
2 entries



10. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://seline.app/
70.35.199.155
a

1

0






Details (GZip part is BETA, may be wrong / incomplete)

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
https://seline.app/
70.35.199.155
a

https://amidioinc.com/seline


1
ok








11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.seline.app
0

no CAA entry found
1
0
seline.app
0

no CAA entry found
1
0
app
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
seline.app

ok
1
0
www.seline.app

ok
1
0
_acme-challenge.seline.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.seline.app

Name Error - The domain name does not exist
1
0
_acme-challenge.seline.app.seline.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.seline.app.seline.app

Name Error - The domain name does not exist
1
0
_acme-challenge.www.seline.app.www.seline.app

Name Error - The domain name does not exist
1
0


13. Portchecks (BETA)

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=0c7bd329-a2f4-4413-aeda-ed12c44add1f


Last Result: https://check-your-website.server-daten.de/?q=seline.app - 2019-06-12 20:26:23


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

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