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



V

Connect failure - perhaps firewall

Checked:
08.05.2020 17:34:43


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
test-video.m-healthsolutions.com
A
207.35.75.150
Surrey/British Columbia/Canada (CA) - Bell Canada
No Hostname found
yes
1
0

AAAA

yes


www.test-video.m-healthsolutions.com

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



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



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 48903 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 39844, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2020, 18:24:21 +, Signature-Inception: 05.05.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2020, 18:24:21 +, Signature-Inception: 05.05.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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: m-healthsolutions.com
m-healthsolutions.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 "nn3j8q7k5h620al1f3do22u342hfar4i" between the hashed NSEC3-owner "nn3h0a0cm2jo9rkhtaufmqr42vquihh6" and the hashed NextOwner "nn3jaqq18s4h82h0dhackdhme6n340g2". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner nn3h0a0cm2jo9rkhtaufmqr42vquihh6.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 12.05.2020, 04:49:23 +, Signature-Inception: 05.05.2020, 03:39:23 +, KeyTag 39844, Signer-Name: com



1 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 63755, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner m-healthsolutions.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 21.05.2020, 00:00:00 +, Signature-Inception: 30.04.2020, 00:00:00 +, KeyTag 63755, Signer-Name: m-healthsolutions.com



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 63755 used to validate the DNSKEY RRSet



Error: DNSKEY 63755 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: test-video.m-healthsolutions.com
test-video.m-healthsolutions.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "test-video.m-healthsolutions.com" and the NextOwner "video.m-healthsolutions.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 207.35.75.150
Validated: RRSIG-Owner test-video.m-healthsolutions.com., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 21.05.2020, 00:00:00 +, Signature-Inception: 30.04.2020, 00:00:00 +, KeyTag 63755, Signer-Name: m-healthsolutions.com



RRSIG Type 47, expiration 2020-05-21 00:00:00 + validates the NSEC RR that proves the not-existence of the CNAME RR. Owner test-video.m-healthsolutions.com, NextOwner: video.m-healthsolutions.com.
Bitmap: A, RRSIG, NSEC



RRSIG Type 47, expiration 2020-05-21 00:00:00 + validates the NSEC RR that proves the not-existence of the TXT RR. Owner test-video.m-healthsolutions.com, NextOwner: video.m-healthsolutions.com.
Bitmap: A, RRSIG, NSEC



RRSIG Type 47, expiration 2020-05-21 00:00:00 + validates the NSEC RR that proves the not-existence of the AAAA RR. Owner test-video.m-healthsolutions.com, NextOwner: video.m-healthsolutions.com.
Bitmap: A, RRSIG, NSEC



RRSIG Type 47, expiration 2020-05-21 00:00:00 + validates the NSEC RR that proves the not-existence of the TLSA RR. Owner test-video.m-healthsolutions.com, NextOwner: video.m-healthsolutions.com.
Bitmap: A, RRSIG, NSEC



RRSIG Type 47, expiration 2020-05-21 00:00:00 + validates the NSEC RR that proves the not-existence of the CAA RR. Owner test-video.m-healthsolutions.com, NextOwner: video.m-healthsolutions.com.
Bitmap: A, RRSIG, NSEC

Zone: www.test-video.m-healthsolutions.com
www.test-video.m-healthsolutions.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "test-video.m-healthsolutions.com" and the NextOwner "video.m-healthsolutions.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC


3. Name Servers

DomainNameserverNS-IP
www.test-video.m-healthsolutions.com
  dns.wwworks-inc.com

test-video.m-healthsolutions.com
  dns.wwworks-inc.com / dns.wwworks-inc.com
206.130.153.4
Burlington/Ontario/Canada (CA) - Advanced Knowledge Networks

m-healthsolutions.com
  dns.wwworks-inc.com / dns.wwworks-inc.com
206.130.153.4
Burlington/Ontario/Canada (CA) - Advanced Knowledge Networks


  dns2.wwworks-inc.com / dns2.wwworks-inc.com
162.243.249.130
New York/United States (US) - DigitalOcean, LLC

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


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


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


Domain:m-healthsolutions.com
Zone-Name:m-healthsolutions.com
Primary:dns.wwworks-inc.com
Mail:weppler.wwworks.com
Serial:2020033102
Refresh:3600
Retry:600
Expire:1209600
TTL:3600
num Entries:2


Domain:test-video.m-healthsolutions.com
Zone-Name:m-healthsolutions.com
Primary:dns.wwworks-inc.com
Mail:weppler.wwworks.com
Serial:2020033102
Refresh:3600
Retry:600
Expire:1209600
TTL:3600
num Entries:1


Domain:www.test-video.m-healthsolutions.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://test-video.m-healthsolutions.com/
207.35.75.150
-2

1.357
V
ConnectFailure - Unable to connect to the remote server

• https://test-video.m-healthsolutions.com/
207.35.75.150
-2

1.360
V
ConnectFailure - Unable to connect to the remote server

• http://test-video.m-healthsolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
207.35.75.150
-2

1.347
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• https://207.35.75.150/
207.35.75.150
-2

1.346
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "test-video.m-healthsolutions.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
Warning: Only one ip address found: test-video.m-healthsolutions.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: test-video.m-healthsolutions.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
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Vhttp://test-video.m-healthsolutions.com/ 207.35.75.150
-2

connect failure - perhaps firewall
Vhttps://test-video.m-healthsolutions.com/ 207.35.75.150
-2

connect failure - perhaps firewall
Vhttp://test-video.m-healthsolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 207.35.75.150
-2

connect failure - perhaps firewall
Vhttps://207.35.75.150/ 207.35.75.150
-2

connect failure - perhaps firewall
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain test-video.m-healthsolutions.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 2 different Name Servers found: dns.wwworks-inc.com, dns2.wwworks-inc.com, 2 Name Servers included in Delegation: dns.wwworks-inc.com, dns2.wwworks-inc.com, 2 Name Servers included in 1 Zone definitions: dns.wwworks-inc.com, dns2.wwworks-inc.com, 1 Name Servers listed in SOA.Primary: dns.wwworks-inc.com.
AGood: Only one SOA.Primary Name Server found.: dns.wwworks-inc.com.
AGood: SOA.Primary Name Server included in the delegation set.: dns.wwworks-inc.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: dns.wwworks-inc.com, dns2.wwworks-inc.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: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 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: wwworks-inc.com
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 162., 206., 2 different subnets (first two Bytes): 162.243., 206.130., 2 different subnets (first three Bytes): 162.243.249., 206.130.153.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
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
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns.wwworks-inc.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.
Nameserver doesn't pass all EDNS-Checks: dns2.wwworks-inc.com / 162.243.249.130: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (dns2.wwworks-inc.com). COOKIE: ok. CLIENTSUBNET: ok.
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.

3. Content- and Performance-critical Checks

http://test-video.m-healthsolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 207.35.75.150
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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.
AInfo: No img element found, no alt attribute checked
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: 75013 milliseconds, 75.013 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

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

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

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1608087391
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-05-07 19:41:47
2020-08-05 19:41:47
test-video.m-healthsolutions.com - 1 entries


1549169314
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-08 16:20:56
2020-07-07 16:20:56
test-video.m-healthsolutions.com - 1 entries


1548779725
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-08 11:25:17
2020-07-07 11:25:17
test-video.m-healthsolutions.com - 1 entries


1544565190
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-06 14:22:20
2020-07-05 14:22:20
test-video.m-healthsolutions.com - 1 entries


1534831736
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-01 19:32:44
2020-06-30 19:32:44
test-video.m-healthsolutions.com - 1 entries



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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2778644311
precert
Leaf-2778644311
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-05-07 17:41:47
2020-08-05 17:41:47
test-video.m-healthsolutions.com
1 entries


2682755473
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-08 14:20:56
2020-07-07 14:20:56
test-video.m-healthsolutions.com
1 entries


2682255432
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-08 09:25:17
2020-07-07 09:25:17
test-video.m-healthsolutions.com
1 entries


2673855355
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-06 12:22:20
2020-07-05 12:22:20
test-video.m-healthsolutions.com
1 entries


2656290346
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-04-01 17:32:44
2020-06-30 17:32:44
test-video.m-healthsolutions.com
1 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns.wwworks-inc.com, dns2.wwworks-inc.com

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

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
dns.wwworks-inc.com: 206.130.153.4
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: dns2.wwworks-inc.com
162.243.249.130


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
test-video.m-healthsolutions.com
0

no CAA entry found
1
0
m-healthsolutions.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
m-healthsolutions.com
v=spf1 mx include:spf.patientcaresolutions.com include:messaging-master.com ip4:207.35.75.128/27 ip4:206.130.153.97 include:spf.protection.outlook.com ~all
ok
1
0
test-video.m-healthsolutions.com

ok
1
0
_acme-challenge.test-video.m-healthsolutions.com

Name Error - The domain name does not exist
1
0
_acme-challenge.test-video.m-healthsolutions.com.m-healthsolutions.com

Name Error - The domain name does not exist
1
0
_acme-challenge.test-video.m-healthsolutions.com.test-video.m-healthsolutions.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=2d73fda0-3210-4555-937b-914aaa8efb06


Last Result: https://check-your-website.server-daten.de/?q=test-video.m-healthsolutions.com - 2020-05-08 17:34:43


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

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