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





1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
plexapp.org
A
76.114.42.158
Hostname: c-76-114-42-158.hsd1.ca.comcast.net
yes
2
0

AAAA

yes


www.plexapp.org
C
plexapp.org
yes
1
0

A
76.114.42.158
Hostname: c-76-114-42-158.hsd1.ca.comcast.net
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)
(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: 02.05.2019, 00:00:00, Signature-Inception: 11.04.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
org
2 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.04.2019, 05:00:00, Signature-Inception: 12.04.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

4 DNSKEY RR found

Public Key with Algorithm 7, KeyTag 9062, Flags 256

Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)

Public Key with Algorithm 7, KeyTag 16454, Flags 256

Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)

3 RRSIG RR to validate DNSKEY RR found

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.04.2019, 15:27:52, Signature-Inception: 09.04.2019, 14:27:52, KeyTag 9062, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.04.2019, 15:27:52, Signature-Inception: 09.04.2019, 14:27:52, KeyTag 9795, Signer-Name: org

Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.04.2019, 15:27:52, Signature-Inception: 09.04.2019, 14:27:52, KeyTag 17883, Signer-Name: org

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9062 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet

Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone
plexapp.org
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.

0 DNSKEY RR found


www.plexapp.org
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
plexapp.org
  ns-cloud-d1.googledomains.com
216.239.32.109

 
2001:4860:4802:32::6d

  ns-cloud-d2.googledomains.com
216.239.34.109

 
2001:4860:4802:34::6d

  ns-cloud-d3.googledomains.com
216.239.36.109

 
2001:4860:4802:36::6d

  ns-cloud-d4.googledomains.com
216.239.38.109

 
2001:4860:4802:38::6d
org
  a0.org.afilias-nst.info / ns000b.app12.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 1.fra.pch


  b0.org.afilias-nst.org / ns000b.app11.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 5.fra.pch


  c0.org.afilias-nst.info / ns000b.app20.ams2.afilias-nst.info


  d0.org.afilias-nst.org / ns000b.app20.lax1.afilias-nst.info


4. SOA-Entries


Domain:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013428160
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:org
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013428161
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:plexapp.org
Primary:ns-cloud-d1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:7
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


5. Url-Checks


show header:
Domainname Http-StatusredirectSec.G
• http://plexapp.org/
76.114.42.158
200

0.370
H
Server: nginx/1.14.0 (Ubuntu)
Date: Fri, 12 Apr 2019 16:29:29 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• http://www.plexapp.org/
76.114.42.158
200

0.370
H
Server: nginx/1.14.0 (Ubuntu)
Date: Fri, 12 Apr 2019 16:29:30 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• https://plexapp.org/
76.114.42.158
-2

1.543
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 76.114.42.158:443

• https://www.plexapp.org/
76.114.42.158
-2

1.544
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 76.114.42.158:443

• http://plexapp.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
76.114.42.158
200

3.370

Visible Content: Loading . . .
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<!DOCTYPE html> <html> <head> <!-- bbbbbbbb OOOOOOOOO b::::::b iiii OO:::::::::OO b::::::b i::::i OO:::::::::::::OO b::::::b iiii O:::::::OOO:::::::O b:::::b O::::::O O::::::O mmmmmmm mmmmmmm b:::::bbbbbbbbb iiiiiii O:::::O O:::::O mm:::::::m m:::::::mm b::::::::::::::bb i:::::i O:::::O O:::::Om::::::::::mm::::::::::mb::::::::::::::::b i::::i O:::::O O:::::Om::::::::::::::::::::::mb:::::bbbbb:::::::b i::::i O:::::O O:::::Om:::::mmm::::::mmm:::::mb:::::b b::::::b i::::i O:::::O O:::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O:::::O O:::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O::::::O O::::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O:::::::OOO:::::::Om::::m m::::m m::::mb:::::bbbbbb::::::bi::::::i OO:::::::::::::OO m::::m m::::m m::::mb::::::::::::::::b i::::::i OO:::::::::OO m::::m m::::m m::::mb:::::::::::::::b i::::::i OOOOOOOOO mmmmmm mmmmmm mmmmmmbbbbbbbbbbbbbbbb iiiiiiii --> <meta charset="utf-8" /> <meta http-equiv="x-ua-compatible" content="ie=edge"> <meta name="description" content="Ombi, media request tool"> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Ombi</title> <meta property="og:title" content=“Ombi” /> <meta property="og:image" content="~/images/logo.png" /> <meta property="og:site_name" content=“Ombi” /> <base href="/" /> <link rel="apple-touch-icon" sizes="180x180" href="/images/favicon/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="/images/favicon/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="/images/favicon/favicon-16x16.png"> <link rel="mask-icon" href="/images/favicon/safari-pinned-tab.svg" color="#df691a"> <link rel="shortcut icon" href="/images/favicon/favicon.ico"> <meta name="msapplication-TileColor" content="#df691a"> <meta name="msapplication-config" content="~/images/favicon/browserconfig.xml"> <meta name="theme-color" content="#df691a"> <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="mobile-web-app-capable" content="yes"> <!-- Global site tag (gtag.js) - Google Analytics --> <script async src="https://www.googletagmanager.com/gtag/js?id=UA-89270627-3"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-89270627-3'); </script> <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet"> <link rel="stylesheet" href="/loading.css?v=k33zb3c0-ToEQSx13OJIBKNSzNyG6g4V29uA0YpYiV0" /> <link rel="stylesheet" href="/dist/vendor.css?v=A5VSEkY8uq7pAj1OkaY6vaxKY0-yZsGZSG_UJMjE8Vg" /> <script src="/dist/app.js?v=K9_1EqmVAVzT4mCJmk2JcRcE-bvVj440xb9inZYbfEQ" defer></script> </head> <body> <ombi> <div class="app-loading-container"> <div class="app-loading"> Loading <span class="app-loading-one">.</span> <span class="app-loading-two">.</span> <span class="app-loading-three">.</span> </div> </div> </ombi> </body> </html>
Server: nginx/1.14.0 (Ubuntu)
Date: Fri, 12 Apr 2019 16:29:36 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• http://www.plexapp.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
76.114.42.158
200

0.370

Visible Content: Loading . . .
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
<!DOCTYPE html> <html> <head> <!-- bbbbbbbb OOOOOOOOO b::::::b iiii OO:::::::::OO b::::::b i::::i OO:::::::::::::OO b::::::b iiii O:::::::OOO:::::::O b:::::b O::::::O O::::::O mmmmmmm mmmmmmm b:::::bbbbbbbbb iiiiiii O:::::O O:::::O mm:::::::m m:::::::mm b::::::::::::::bb i:::::i O:::::O O:::::Om::::::::::mm::::::::::mb::::::::::::::::b i::::i O:::::O O:::::Om::::::::::::::::::::::mb:::::bbbbb:::::::b i::::i O:::::O O:::::Om:::::mmm::::::mmm:::::mb:::::b b::::::b i::::i O:::::O O:::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O:::::O O:::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O::::::O O::::::Om::::m m::::m m::::mb:::::b b:::::b i::::i O:::::::OOO:::::::Om::::m m::::m m::::mb:::::bbbbbb::::::bi::::::i OO:::::::::::::OO m::::m m::::m m::::mb::::::::::::::::b i::::::i OO:::::::::OO m::::m m::::m m::::mb:::::::::::::::b i::::::i OOOOOOOOO mmmmmm mmmmmm mmmmmmbbbbbbbbbbbbbbbb iiiiiiii --> <meta charset="utf-8" /> <meta http-equiv="x-ua-compatible" content="ie=edge"> <meta name="description" content="Ombi, media request tool"> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Ombi</title> <meta property="og:title" content=“Ombi” /> <meta property="og:image" content="~/images/logo.png" /> <meta property="og:site_name" content=“Ombi” /> <base href="/" /> <link rel="apple-touch-icon" sizes="180x180" href="/images/favicon/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="/images/favicon/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="/images/favicon/favicon-16x16.png"> <link rel="mask-icon" href="/images/favicon/safari-pinned-tab.svg" color="#df691a"> <link rel="shortcut icon" href="/images/favicon/favicon.ico"> <meta name="msapplication-TileColor" content="#df691a"> <meta name="msapplication-config" content="~/images/favicon/browserconfig.xml"> <meta name="theme-color" content="#df691a"> <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="mobile-web-app-capable" content="yes"> <!-- Global site tag (gtag.js) - Google Analytics --> <script async src="https://www.googletagmanager.com/gtag/js?id=UA-89270627-3"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-89270627-3'); </script> <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet"> <link rel="stylesheet" href="/loading.css?v=k33zb3c0-ToEQSx13OJIBKNSzNyG6g4V29uA0YpYiV0" /> <link rel="stylesheet" href="/dist/vendor.css?v=A5VSEkY8uq7pAj1OkaY6vaxKY0-yZsGZSG_UJMjE8Vg" /> <script src="/dist/app.js?v=K9_1EqmVAVzT4mCJmk2JcRcE-bvVj440xb9inZYbfEQ" defer></script> </head> <body> <ombi> <div class="app-loading-container"> <div class="app-loading"> Loading <span class="app-loading-one">.</span> <span class="app-loading-two">.</span> <span class="app-loading-three">.</span> </div> </div> </ombi> </body> </html>
Server: nginx/1.14.0 (Ubuntu)
Date: Fri, 12 Apr 2019 16:29:36 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

6. Comments

Aname "plexapp.org" is domain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
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: No https - result with http-status 200, no encryption
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.
Vhttps://plexapp.org/ 76.114.42.158
-2

connect failure - perhaps firewall
Vhttps://www.plexapp.org/ 76.114.42.158
-2

connect failure - perhaps firewall
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
http://plexapp.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.114.42.158
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.plexapp.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 76.114.42.158
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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: 35154 milliseconds, 35.154 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check (BETA)

1. Source CertSpotter - active certificates

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
3
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
859543567
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-12 00:04:34
2019-07-11 00:04:34
plexapp.org - 1 entries


811108271
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-14 19:17:34
2019-06-12 19:17:34
*.plexapp.org - 1 entries


811108026
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-14 19:17:30
2019-06-12 19:17:30
plexapp.org - 1 entries


809066575
leaf cert
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-03-13 00:00:00
2020-03-13 12:00:00
*.plexapp.org, plexapp.org, sni.cloudflaressl.com - 3 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
3
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
0
2
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1536530856
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-06-02 22:00:00
2020-06-02 10:00:00
*.plexapp.org, plexapp.org, sni.cloudflaressl.com
3 entries


1380269620
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-11 22:04:34
2019-07-10 22:04:34
plexapp.org
1 entries


1293103043
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-14 18:17:34
2019-06-12 17:17:34
*.plexapp.org
1 entries


1293102900
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-03-14 18:17:30
2019-06-12 17:17:30
plexapp.org
1 entries


1290226103
CN=CloudFlare Inc ECC CA-2, O="CloudFlare, Inc.", L=San Francisco, C=US, ST=CA
2019-03-12 23:00:00
2020-03-13 11:00:00
*.plexapp.org, CloudFlare, Inc., plexapp.org, sni.cloudflaressl.com
3 entries



10. Html-Content - Entries (BETA - mixed content and other checks)

No Html-Content entries found. Only checked if https + status 200/401/403/404


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.plexapp.org



1
0
plexapp.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
plexapp.org

ok
1
0
www.plexapp.org


1
0
_acme-challenge.plexapp.org

Name Error - The domain name does not exist
1
0
_acme-challenge.www.plexapp.org

Name Error - The domain name does not exist
1
0
_acme-challenge.plexapp.org.plexapp.org

Name Error - The domain name does not exist
1
0
_acme-challenge.www.plexapp.org.www.plexapp.org

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=8018d476-4282-4624-886e-e0ced929bbd3


Last Result: https://check-your-website.server-daten.de/?q=plexapp.org - 2019-06-03 16:00:30


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

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