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


 

 

A

 

Top config

 

Checked:
18.08.2021 01:09:40

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
blog.mushdragon.com
A
64.98.114.236
Holly Springs/North Carolina/United States (US) - TF-178-HSNC, Ting Fiber Inc.
Hostname: hs-nc-f6e99a26b3-125782-1.tingfiber.com
yes
1
0

AAAA

yes


www.blog.mushdragon.com

Name Error
yes
1
0
*.mushdragon.com
A
64.98.114.236
yes



AAAA

yes



CNAME

yes


*.blog.mushdragon.com
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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 26838, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=






1 RRSIG RR to validate DS RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.08.2021, 16:00:00 +, Signature-Inception: 17.08.2021, 15:00:00 +, KeyTag 26838, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 39343, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.08.2021, 18:24:21 +, Signature-Inception: 08.08.2021, 18:19:21 +, 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: mushdragon.com

mushdragon.com
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 16466, DigestType 2 and Digest rCf1MmLKiSvaBJXgZgIMgiyC7CslfmPd4ISUL9Q5INE=






1 RRSIG RR to validate DS RR found






RRSIG-Owner mushdragon.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 24.08.2021, 05:27:30 +, Signature-Inception: 17.08.2021, 04:17:30 +, KeyTag 39343, Signer-Name: com






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 4593, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner mushdragon.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 16466, Signer-Name: mushdragon.com






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






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



Zone: blog.mushdragon.com

blog.mushdragon.com
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 "k2eh7h0eqo798ulblivksonh80nh0ru2" between the hashed NSEC3-owner "k2eh7h0eqo798ulblivksonh80nh0ru2" and the hashed NextOwner "kb4kq9csggk49ma2ojkvvamm4s2ugeub". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 64.98.114.236
Validated: RRSIG-Owner blog.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "k2eh7h0eqo798ulblivksonh80nh0ru2" equal the hashed NSEC3-owner "k2eh7h0eqo798ulblivksonh80nh0ru2" and the hashed NextOwner "kb4kq9csggk49ma2ojkvvamm4s2ugeub". 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 Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "k2eh7h0eqo798ulblivksonh80nh0ru2" equal the hashed NSEC3-owner "k2eh7h0eqo798ulblivksonh80nh0ru2" and the hashed NextOwner "kb4kq9csggk49ma2ojkvvamm4s2ugeub". 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 Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "k2eh7h0eqo798ulblivksonh80nh0ru2" equal the hashed NSEC3-owner "k2eh7h0eqo798ulblivksonh80nh0ru2" and the hashed NextOwner "kb4kq9csggk49ma2ojkvvamm4s2ugeub". 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 Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.blog.mushdragon.com) sends a valid NSEC3 RR as result with the hashed owner name "k2eh7h0eqo798ulblivksonh80nh0ru2" (unhashed: blog.mushdragon.com). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "ei94j6omitfkejiekq5l26ddj0um1gcq" (unhashed: _tcp.blog.mushdragon.com) with the owner "9a6j34ee4ub5kcdm7o3n15ve5uf07p7q" and the NextOwner "fus13a543oefuit1gt9i302h8cgkiijc". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner 9a6j34ee4ub5kcdm7o3n15ve5uf07p7q.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "fvj4gorai8gergv6pjbk0hq734uv6hna" (unhashed: *.blog.mushdragon.com) with the owner "fus13a543oefuit1gt9i302h8cgkiijc" and the NextOwner "g780shatkc924ati31v3d4de2s7m1a40". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner fus13a543oefuit1gt9i302h8cgkiijc.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "k2eh7h0eqo798ulblivksonh80nh0ru2" equal the hashed NSEC3-owner "k2eh7h0eqo798ulblivksonh80nh0ru2" and the hashed NextOwner "kb4kq9csggk49ma2ojkvvamm4s2ugeub". 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 Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






Status: Good. NoData-Proof required and found.



Zone: www.blog.mushdragon.com

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






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k2eh7h0eqo798ulblivksonh80nh0ru2" as Owner. That's the Hash of "blog.mushdragon.com" with the NextHashedOwnerName "kb4kq9csggk49ma2ojkvvamm4s2ugeub". So that domain name is the Closest Encloser of "www.blog.mushdragon.com". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner k2eh7h0eqo798ulblivksonh80nh0ru2.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com






The ClosestEncloser says, that "*.blog.mushdragon.com" with the Hash "fvj4gorai8gergv6pjbk0hq734uv6hna" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "fus13a543oefuit1gt9i302h8cgkiijc" and the Next Owner "g780shatkc924ati31v3d4de2s7m1a40", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner fus13a543oefuit1gt9i302h8cgkiijc.mushdragon.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 05.09.2021, 03:19:20 +, Signature-Inception: 14.08.2021, 03:19:20 +, KeyTag 4593, Signer-Name: mushdragon.com

 

3. Name Servers

DomainNameserverNS-IP
www.blog.mushdragon.com
  ns-cloud-b1.googledomains.com

blog.mushdragon.com
  ns-cloud-b1.googledomains.com
216.239.32.107
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6b
Mountain View/California/United States (US) - Google LLC

mushdragon.com
  ns-cloud-b1.googledomains.com
216.239.32.107
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6b
Mountain View/California/United States (US) - Google LLC


  ns-cloud-b2.googledomains.com
216.239.34.107
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:34::6b
Mountain View/California/United States (US) - Google LLC


  ns-cloud-b3.googledomains.com
216.239.36.107
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:36::6b
Mountain View/California/United States (US) - Google LLC


  ns-cloud-b4.googledomains.com
216.239.38.107
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:38::6b
Mountain View/California/United States (US) - Google LLC

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-ein2


  k.gtld-servers.net / nnn1-ein4


  l.gtld-servers.net / nnn1-ein4


  m.gtld-servers.net / nnn1-ein5

 

4. SOA-Entries


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


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


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


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


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


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


Domain:mushdragon.com
Zone-Name:mushdragon.com
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:22
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:blog.mushdragon.com
Zone-Name:mushdragon.com
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:22
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:2


Domain:www.blog.mushdragon.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

Startaddress: https://blog.mushdragon.com, address used: https://blog.mushdragon.com/, Screenshot created 2021-08-18 01:11:19 +00:0

 

Mobil (412px x 732px)

 

391 milliseconds

 

Screenshot mobile - https://blog.mushdragon.com/
Mobil + Landscape (732px x 412px)

 

386 milliseconds

 

Screenshot mobile landscape - https://blog.mushdragon.com/
Screen (1280px x 1680px)

 

1037 milliseconds

 

Screenshot Desktop - https://blog.mushdragon.com/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport412732
content Size412732

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_128_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://blog.mushdragon.com/
64.98.114.236
301
https://blog.mushdragon.com/
Html is minified: 100.00 %
0.227
A
Location: https://blog.mushdragon.com/
Date: Tue, 17 Aug 2021 23:10:37 GMT
Content-Length: 17
Content-Type: text/plain; charset=utf-8
Connection: close

• https://blog.mushdragon.com/
64.98.114.236
Inline-JavaScript (∑/total): 2/0 Inline-CSS (∑/total): 2/1295
200

Html is minified: 140.85 %
Other inline scripts (∑/total): 1/585
3.686
A
small visible content (num chars: 377)
O.M. - Projects Home Projects Subscribe Apple Google Spotify Overcast Stitcher RSS Home Projects Automated Media Server Guide Aug 16, 2021 This entire project started off as a way for me to just save some money by "cutting the cord" and dropping my cable service provider. Read more Load more Apple Google Spotify Overcast Stitcher RSS Powered by Ghost ... 1x 00:00:00 00:00:00
Cache-Control: public, max-age=0
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Date: Tue, 17 Aug 2021 23:10:38 GMT
Etag: W/"2fb9-2yRtbv0qFzFVdE31R+Tl/RhgCtI"
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Vary: Accept-Encoding
X-Powered-By: Express
Connection: close
Transfer-Encoding: chunked

• http://blog.mushdragon.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
64.98.114.236
-14


10.017
T
Timeout - The operation has timed out
Visible Content:

• https://64.98.114.236/
64.98.114.236
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
Other inline scripts (∑/total): 0/0
3.597
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 18)
404 page not found
Content-Type: text/plain; charset=utf-8
X-Content-Type-Options: nosniff
Date: Tue, 17 Aug 2021 23:10:52 GMT
Content-Length: 19
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "blog.mushdragon.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 61113 (complete: 168171)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: blog.mushdragon.com 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: blog.mushdragon.com has no ipv6 address.
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: No cookie sent via http.
AGood: HSTS has preload directive
Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Ahttp://blog.mushdragon.com/ 64.98.114.236
301
https://blog.mushdragon.com/
Correct redirect http - https with the same domain name
Mhttps://64.98.114.236/ 64.98.114.236
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://64.98.114.236/ 64.98.114.236
404

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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain blog.mushdragon.com, 1 ip addresses.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-b1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-b1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-b1.googledomains.com.
AGood: Consistency 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. Ordered list of name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 Name Servers, 1 Top Level Domain: com
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: googledomains.com
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
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: ns-cloud-b1.googledomains.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

http://blog.mushdragon.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 64.98.114.236
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://blog.mushdragon.com/ 64.98.114.236
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://blog.mushdragon.com/ 64.98.114.236
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.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
AGood: Some script Elements (type text/javascript) with a src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output.
https://blog.mushdragon.com/ 64.98.114.236
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 2 script elements without defer/async.
AGood: All CSS / JavaScript files are sent compressed (gzip, deflate, br checked). That reduces the content of the files. 5 external CSS / JavaScript files found
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 1 with Cache-Control max-age too short (minimum 7 days), 3 with Cache-Control long enough, 5 complete.
Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
AGood: Some img-elements have a valid alt-attribute.: 2 img-elements found, 1 img-elements with correct alt-attributes (defined, not an empty value).
Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 1 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
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://64.98.114.236/ 64.98.114.236
404
3.597 seconds
Warning: 404 needs more then one second
ADuration: 105763 milliseconds, 105.763 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
blog.mushdragon.com
64.98.114.236
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
blog.mushdragon.com
64.98.114.236
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=mushdragon.com


2CN=R3, O=Let's Encrypt, C=US


3CN=ISRG Root X1, O=Internet Security Research Group, C=US


64.98.114.236
64.98.114.236
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

64.98.114.236
64.98.114.236
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
Self signed certificate

1CN=TRAEFIK DEFAULT CERT

 

9. Certificates

1.
1.
CN=mushdragon.com
17.08.2021
15.11.2021
1218 days expired
*.mushdragon.com, mushdragon.com - 2 entries
1.
1.
CN=mushdragon.com
17.08.2021

15.11.2021
1218 days expired


*.mushdragon.com, mushdragon.com - 2 entries

KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:04D43C9CE39DF384811C38D8C341851FCA06
Thumbprint:B561C88A5309752FFD51B7A51BFE2673AACBFB9B
SHA256 / Certificate:UXGqKJxBxhCyNkPkngQ9izD9B2q8xLy44Xto07Tj/BU=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):004bcede94322864661cc54eccbc34526a9624acd9d3a34f7d8a2094b638780a
SHA256 hex / Subject Public Key Information (SPKI):004bcede94322864661cc54eccbc34526a9624acd9d3a34f7d8a2094b638780a
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r3.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 182 days


2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 182 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
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:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3731 days


3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3731 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
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:




2.
1.
CN=TRAEFIK DEFAULT CERT
18.08.2021
18.08.2022
942 days expired
64ba94e53ff63232b3ff5424a68b0d7e.e702c2c3d5b63538ca3a3d77823d23ff.traefik.default - 1 entry
2.
1.
CN=TRAEFIK DEFAULT CERT
18.08.2021

18.08.2022
942 days expired


64ba94e53ff63232b3ff5424a68b0d7e.e702c2c3d5b63538ca3a3d77823d23ff.traefik.default - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00EF47CCA32D7CE741DC1D94D85D2447A9
Thumbprint:3EE59FA71C20770E42EE2DA603DD810681B4A42E
SHA256 / Certificate:fINAdEX2P+BnBn97XbcVKPW9LwZxZir5vCQJf5z4Rr0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):da6574c83892655aee6ab5df04a0615d344cb4af264d4f7e9d4bb76b11b4bb3a
SHA256 hex / Subject Public Key Information (SPKI):da6574c83892655aee6ab5df04a0615d344cb4af264d4f7e9d4bb76b11b4bb3a
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:Serverauthentifizierung (1.3.6.1.5.5.7.3.1)


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)

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

Small Code Update - wait one minute

 

11. Html-Content - Entries

Summary

No data found or small Code-update

 

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

 

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com

 

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (2001:500:2d::d)

Answer: 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
2
ns-cloud-b1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
3
ns-cloud-b2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
4
ns-cloud-b3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-b4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10
6
ns-cloud-b1.googledomains.com: 216.239.32.107
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-b1.googledomains.com: 2001:4860:4802:32::6b
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-b2.googledomains.com: 216.239.34.107
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-b2.googledomains.com: 2001:4860:4802:34::6b
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-b3.googledomains.com: 216.239.36.107
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-b3.googledomains.com: 2001:4860:4802:36::6b
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-b4.googledomains.com: 216.239.38.107
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-b4.googledomains.com: 2001:4860:4802:38::6b
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
blog.mushdragon.com
0

no CAA entry found
1
0
mushdragon.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mushdragon.com
v=spf1 include:_spf.google.com ~all
ok
1
0
blog.mushdragon.com

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

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

perhaps wrong
1
0
_acme-challenge.blog.mushdragon.com.blog.mushdragon.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 open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=ee20cf69-b93c-41d4-a7ff-f85913b63a82

 

Last Result: https://check-your-website.server-daten.de/?q=blog.mushdragon.com - 2021-08-18 01:09:40

 

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.mushdragon.com" target="_blank">Check this Site: blog.mushdragon.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.mushdragon.com