FAQ

The FAQ section contains useful guides to technical product settings and information about your contract. Use the "Topics" selection field to narrow down your search.

E-Mail

In the webmail client, you can set a new password under Settings -> Password.

A mailbox can be managed either directly in the browser or via a mail client. The configuration settings are as follows:

Name: Shown as the sender name in e-mails.
E-mail address: Your e-mail address or an alias of it
Server type: IMAP (recommended) or POP3
Username: The full e-mail address (e-mail aliases are not allowed!)
Password: The mailbox password set in the MyWebspace Panel
Incoming mail server (IMAP): email.my-webspace.at
Incoming mail server (IMAP) port: 993
Incoming server authentication: Password
Outgoing mail server (SMTP): email.my-webspace.at
Outgoing mail server (SMTP) port: 465
Outgoing server authentication: Password
Encryption: Enable SSL/TLS
Webmail access: email.my-webspace.at

Unfortunately, the e-mails you receive always include some spam e-mails. If spam e-mails are also answered automatically, the senders learn that there really is a person behind this e-mail address. As a result, even more spam is sent to this person. Those automatic replies are sent by our mail server, which then gets a bad "digital reputation" on the internet – in the worst case, e-mails no longer reach their recipients at all.

Did you know that around 160 billion spam e-mails are sent every day? That is almost half of all e-mails sent each day.

Our spam & virus filter reliably detects spam and attached viruses sent to your e-mail addresses. Messages identified as spam with 100% certainty are discarded automatically. All others end up in the junk folder of the respective mailbox. E-mails with attached viruses are discarded automatically to keep you safe.

Due to the volume and complexity of many spam e-mails, it can still happen that some end up in your mailbox. We are constantly working to improve our spam filter.

An e-mail can be sent to a maximum of 35 recipients (including CC and BCC). If you choose more, the e-mail gets stuck when sending and cannot be delivered.

Did you know that you can also use MyWebspace e-mail addresses like this

j.doe+anyword@example.com

and that those e-mails also end up in your mailbox?

Why is this useful?

Let's say your e-mail address is j.doe@example.com and you sign up for an online account at Contoso. With plus addressing, you can enter j.doe+contoso@example.com instead of your actual e-mail address.

Or you want to go on a trip and book a ticket at Margie's Travel. To do so, you could use this e-mail address, for example: j.doe+margiestravel@example.com

If Contoso is then hacked for whatever reason and all customer data is stolen, it is very likely that you will receive all kinds of obscure e-mails afterwards – fake e-mails that look as if they came from your bank, for example. If the recipient address is j.doe+contoso@example.com instead of your regular e-mail address, you know that you had better not open this e-mail or click any links. Instead, you should create a filter in your mail client or your webmail that deletes such e-mails in the future.

Using different e-mail addresses for different websites and services therefore has the following advantages:

  • Traceability: you know which e-mail belongs to which website
  • Privacy: if companies exchange your personal data, it is much harder to link it together because you used different e-mail addresses.
  • Security: you can use not only different passwords but also different e-mail addresses.

Unfortunately, some websites consider the "+" character in e-mail addresses invalid. In that case, you can use the tilde (~), the equals sign (=), the percent sign (%) or the digit 8 instead of the plus sign.

This is because the digit 8 is used as an alternative separator for plus addresses.

If you still want to use an "8" in your e-mail address, e.g. "user1980@example.com", create your address as "user19@example.com". You will then receive all e-mails sent to "user198...", i.e. not only "user1980@example.com" but also "user1988@example.com" or "user198helloworld@example.com".

Filter rules can be set up in our webmail under the filter settings. The login details are the e-mail address and its password.

Log in there with the respective e-mail address, then go to Settings and then Filters. In the lower left corner, you will find a plus icon that lets you create a rule.

The filter rules you create then apply on all devices with a mail client such as Thunderbird or Outlook.

All our hosting products include access via POP3, IMAP and webmail. We recommend using IMAP.

IMAP: If you use IMAP, your computer synchronises your mail with our servers and the e-mails remain on our servers. If you access your mailbox from more than one computer or from a smartphone, IMAP is also the better choice, as all folders (including sent messages) are available on all devices and the mail status (read/unread) is synchronised between devices. The e-mail spam folder can only be accessed via IMAP and the webmail interface.

POP3: With POP3, e-mails are transferred from our servers to your computer and then deleted from our servers. This saves storage space at MyWebspace. At the same time, however, your e-mails are then only on that one device.

In the MyWebspace Panel, you can add forwardings to an internal e-mail address under E-mail alias.

If you want to forward to an external address such as Gmail or Hotmail, you need a so-called distribution list. You can create one by clicking "Create new distribution list". First enter the e-mail address to be forwarded; in the next step you can enter one or more forwarding addresses. This also lets you forward e-mails automatically to several recipients. The maximum number of recipients per distribution list is 30.

Automatically forwarding e-mails to an external address via a filter rule is not allowed. The reason is explained in the FAQ entry on out-of-office assistants.

MyWebspace Panel

Open the following link and confirm your MyWebspace account by entering the username or e-mail address stored in the panel:

Reset password

You will then receive an e-mail. Click the link in the e-mail and set a new password on the website.

You can change it in the MyWebspace Panel under "Files". Simply click the key icon and enter the new password twice. Once saved, the new password can be used immediately for accessing the webspace via SFTP and SSH.

We offer the following services for transferring files to/from your webspace:

SFTP, SCP and rsync (via SSH). There is also a web-based file manager in the customer panel – however, it is only recommended for transferring individual files.

Please note that plain FTP is disabled by default! FTP is a security risk because everything is transferred unencrypted, and it also often causes problems with firewalls.

Since all common programs can also handle SFTP [for example Cyberduck (Mac), WinSCP and FileZilla (Windows) or Nautilus/Thunar/Konqueror (Linux)], this should not be a limitation.

The access details for our web server are as follows:

Web server address: webhost.my-webspace.at
Username: [username]-www (example: mustermann-www)
Password: Automatically assigned / self-chosen password (sent by e-mail after the webspace was created)

We assign you a password for SFTP access via an SFTP client such as FileZilla. You can change it in the "File Manager" in the MyWebspace Panel by clicking the key icon.

Further products such as domains, e-mails or larger MyWebspace packages can easily be obtained via our MyWebspace Panel.

You can also contact us if you would like us to activate an upgrade or a new product for you.

A subdomain such as "xyz.example.com" can be created under the menu item "Domain" in the MyWebspace Panel.

Enter the corresponding name in the "Subdomain" field, e.g. xyz.example.com.

The path points to the content location of the created subdomain. The directory is created automatically.

An entry with the prefix "www." is also added. (For example, if you enter "xyz" as a subdomain for example.com, your website will be reachable at xyz.example.com and www.xyz.example.com.)

When you create new subdomains, DNS records are added automatically. You should always check the DNS configuration to make sure they were added correctly and that no outdated records remain if you rename something.

2FA protects your MyWebspace Panel access in addition to your password: after logging in with your username and password, you enter a one-time code. You can receive it by e-mail or generate it with an authenticator app (TOTP). This keeps your MyWebspace account protected even if someone knows your password.

You can create it in the MyWebspace Panel at the very bottom of the "Profile" menu item. You will receive it signed by e-mail within three business days.

In the MyWebspace Panel, you can set the version under "PHP". By default, we only support PHP versions from 8.1 upwards.

Do you have a website/web app running on an old PHP version 5.x - 8.0?

No problem – with our PHP Extended Support package, it can continue to be hosted and displayed without any issues. The cost is 5,99 €/ month (incl. VAT). PHP versions older than 8.1 may have security issues and therefore need additional protection. You can find more information about PHP versions here.


In the MyWebspace Panel, under Profile, you will find an overview of the storage used on the web and mail server.

You can pay via PayPal or bank transfer.

Via PayPal, we also accept common credit cards such as VISA and Mastercard. Please note that PayPal incurs an additional 5% transaction fee! We currently do not offer direct debit. All transactions are made exclusively by invoice with payment in advance.

You can also pay in your banking app by scanning the QR code on the invoice. Contracts are renewed automatically before they expire. You can find all further information on payment terms in our terms and conditions.

Every website hosted at MyWebspace automatically receives a Let's Encrypt SSL certificate and is automatically redirected from HTTP to HTTPS. For websites not hosted at MyWebspace, Let's Encrypt SSL certificates cannot be issued for technical reasons.

HTTPS redirects can be set up as follows:

In the MyWebspace Panel, go to the menu item "Domain" -> select the domain -> click the name under "Webhosts on ...". In the SSL encryption field, you can then make the appropriate setting.

All communication within the MyWebspace infrastructure runs over encrypted SSL connections.

Yes, you can host as many websites as you like on your account. However, reselling to third parties is not permitted.

You can also buy as many domains as you like for your hosting package. For each domain, the server directory from which the domain is served (DocumentRoot) can be set individually under "Domain" in the MyWebspace Panel.

Help on record types

A is used to point records to IPv4 addresses.
AAAA is used to point records to IPv6 addresses.
ALIAS fetches AAAA and A records from another domain and inserts them here. This works similarly to a CNAME but can be used at the domain apex and together with other records such as TXT. Please note that MyWebspace servers in Austria are used to resolve the records, which may affect geography-based routing. The domain is interpreted as it is and, unlike a CNAME, does not need to end with a dot.
CNAME is used to point a record to another record. Note that the data must end with a dot (.) to point to another domain.
MX is used to specify a mail server for the domain. The record data must be in the format \priority domainname\. Example: \20 mail.my-webspace.at.\. Note that the data must end with a dot (.) to point to another domain.
NS is used to point to another name server.
TXT is used to add arbitrary text to the DNS system. Google and other providers use this as a method to verify domain ownership.

MyWebcloud

A guide will help you set up your Nextcloud client.

You need the following details for the setup:

Server address: https://mywebcloud.at
Username: the username chosen in the MyWebspace Panel under the Webcloud tab
Password: the password chosen for the user in the MyWebspace Panel
Local folder The folder on your PC/Mac that should be synchronised. For example, you can create a new folder called MyWebcloud for this.

The following steps are required:

  • On your PC, go to MyWebcloud and log in with your Nextcloud user
  • Click your user icon in the top right corner -> Settings -> Security -> select "Enable TOTP"
  • Switch to your phone and open or install your authenticator app – we recommend Google Authenticator, MS Authenticator or Aegis
  • Tap the + sign at the bottom right of the app (a Google or MS login is not required) -> Scan QR code -> scan the QR code shown on your PC
  • Then enter the 6-digit code shown in the app on your PC to confirm the 2FA activation
  • In the last step, save the backup codes so you can use them as an alternative to 2FA. To do this, click "Generate Backup Code" on your PC. Each of these 10 codes can be used once instead of 2FA to log in. Store these codes in a safe place

That's it – 2FA is now set up for your MyWebcloud user! The second factor is only requested in the web browser, not in the Nextcloud client.

Webhosting

You can change it in the MyWebspace Panel under "Files". Simply click the key icon and enter the new password twice. Once saved, the new password can be used immediately for accessing the webspace via SFTP and SSH.

In the MyWebspace Panel, under CMS, there is a one-click installer for WordPress & DokuWiki.

To install, do the following:

Click "Install CMS". In the next step, choose the desired CMS and confirm with Next, then select the domain on which the application should be installed. In the directory field, you can optionally install the application in a subdirectory such as "wordpress". The application's URL would then be: www.[yourdomain]/wordpress/ . Usually you can leave this field empty so that it is installed directly under www.[yourdomain]. Clicking Next again installs the application. Important: open it right away and complete the final website settings manually!

We offer the following services for transferring files to/from your webspace:

SFTP, SCP and rsync (via SSH). There is also a web-based file manager in the customer panel – however, it is only recommended for transferring individual files.

Please note that plain FTP is disabled by default! FTP is a security risk because everything is transferred unencrypted, and it also often causes problems with firewalls.

Since all common programs can also handle SFTP [for example Cyberduck (Mac), WinSCP and FileZilla (Windows) or Nautilus/Thunar/Konqueror (Linux)], this should not be a limitation.

The access details for our web server are as follows:

Web server address: webhost.my-webspace.at
Username: [username]-www (example: mustermann-www)
Password: Automatically assigned / self-chosen password (sent by e-mail after the webspace was created)

We assign you a password for SFTP access via an SFTP client such as FileZilla. You can change it in the "File Manager" in the MyWebspace Panel by clicking the key icon.

Not directly, but we have partners who can take on such projects for you. Tell us what you need via the contact form and we will be happy to forward your request to our partners.

Yes. Common CMS systems such as WordPress, Drupal, Joomla, Backdrop, DokuWiki, Discourse, Typo3 and many others can be installed on our web server. All other systems based on PHP that require a MySQL or SQLite database should also install without any problems.

For Drupal or Backdrop pros, we have also installed the administration tools "Drush" and "Bee", which can be used via the shell.

Yes, you can host as many websites as you like on your account. However, reselling to third parties is not permitted.

You can also buy as many domains as you like for your hosting package. For each domain, the server directory from which the domain is served (DocumentRoot) can be set individually under "Domain" in the MyWebspace Panel.

Further products such as domains, e-mails or larger MyWebspace packages can easily be obtained via our MyWebspace Panel.

You can also contact us if you would like us to activate an upgrade or a new product for you.

Every website hosted at MyWebspace automatically receives a Let's Encrypt SSL certificate and is automatically redirected from HTTP to HTTPS. For websites not hosted at MyWebspace, Let's Encrypt SSL certificates cannot be issued for technical reasons.

HTTPS redirects can be set up as follows:

In the MyWebspace Panel, go to the menu item "Domain" -> select the domain -> click the name under "Webhosts on ...". In the SSL encryption field, you can then make the appropriate setting.

All communication within the MyWebspace infrastructure runs over encrypted SSL connections.

This is of course annoying and should not happen.

There can be many reasons for an outage:

  • First of all, a great many AI bots/crawlers are roaming the internet and cause very high traffic. If they crawl too many websites on one server for content, the server can become overloaded and go down for a short time. We are constantly trying to stay ahead of the AI bots with technical measures. Unfortunately, this often turns into a "cat-and-mouse game", which is why it requires continuous intervention on our part.
  • Websites and the CMS behind them (WordPress, Joomla, Backdrop, Drupal, ...) can also cause errors that make a website unreachable
  • Faulty software updates or the PHP version in use can also be a reason for an outage. You can set the PHP version in the MyWebspace Panel under PHP.

You have probably tried to log in to our server several times. We have increased the security of our access points, so logins to the server are blocked after several failed attempts. In this case, please wait about 10 minutes; access will then be unblocked again.

In the MyWebspace Panel, you can set the version under "PHP". By default, we only support PHP versions from 8.1 upwards.

Do you have a website/web app running on an old PHP version 5.x - 8.0?

No problem – with our PHP Extended Support package, it can continue to be hosted and displayed without any issues. The cost is 5,99 €/ month (incl. VAT). PHP versions older than 8.1 may have security issues and therefore need additional protection. You can find more information about PHP versions here.


Our entire server infrastructure is backed up daily. If you have accidentally deleted or lost data, we can restore it for a corresponding fee. To do so, send us a message via our contact form with a detailed description of which data should be restored and from which time period.

Domain

Yes, your domain will be renewed automatically, and the e-mail is an annual standard e-mail from our domain provider confirming the automatic domain renewal once again.

All domains at MyWebspace are renewed automatically unless customers want to cancel them.

The e-mail usually looks roughly like this:

....

Domainname | Exp.-Date | Last Ren.-Date | Autorenewal
-------------------+------------+----------------+------------
domainnamen.net | 2026-08-08 | 2026-08-08 | yes
....

The "yes" confirms the domain renewal once again. You can ignore the e-mail.

Great! We're glad to hear that :)

To transfer a domain to MyWebspace, you need the following:

  • Removal of the domain lock at your current domain provider
  • The so-called auth code (authorisation code) for transferring the domain from your current domain provider. This can usually be requested in their dashboard or via their contact form.
  • MyWebspace account: during the domain transfer, you will be asked to create an account if you do not have one with us yet.

Apart from the domain costs mentioned, there are no extra fees for the domain transfer.

If you already have a website or e-mail address with your old domain provider, we can take these over as well. Depending on the effort involved, migration costs may apply, which we will clarify with you in advance.

If you would rather we handle the domain transfer for you, you can contact us via the contact form.

A subdomain such as "xyz.example.com" can be created under the menu item "Domain" in the MyWebspace Panel.

Enter the corresponding name in the "Subdomain" field, e.g. xyz.example.com.

The path points to the content location of the created subdomain. The directory is created automatically.

An entry with the prefix "www." is also added. (For example, if you enter "xyz" as a subdomain for example.com, your website will be reachable at xyz.example.com and www.xyz.example.com.)

When you create new subdomains, DNS records are added automatically. You should always check the DNS configuration to make sure they were added correctly and that no outdated records remain if you rename something.

Yes, you can. Simply send us a message with the desired domain extension via the contact form and we will get in touch with you.

When registering a domain, you have to provide some data such as your postal address, an existing e-mail address, phone number, etc. This data is required by the domain registry! Without it, domains unfortunately cannot be purchased. Please make sure the data is correct and complete so that you also have full legal rights to the domains you register. Of course, we handle your data with care and will never pass it on to third parties without asking, except for registering domains.

Data protection is very important to us!

Help on record types

A is used to point records to IPv4 addresses.
AAAA is used to point records to IPv6 addresses.
ALIAS fetches AAAA and A records from another domain and inserts them here. This works similarly to a CNAME but can be used at the domain apex and together with other records such as TXT. Please note that MyWebspace servers in Austria are used to resolve the records, which may affect geography-based routing. The domain is interpreted as it is and, unlike a CNAME, does not need to end with a dot.
CNAME is used to point a record to another record. Note that the data must end with a dot (.) to point to another domain.
MX is used to specify a mail server for the domain. The record data must be in the format \priority domainname\. Example: \20 mail.my-webspace.at.\. Note that the data must end with a dot (.) to point to another domain.
NS is used to point to another name server.
TXT is used to add arbitrary text to the DNS system. Google and other providers use this as a method to verify domain ownership.

MyWebspace provides a simple REST API to update DNS entries automatically. This allows you to do a number of things:

  • Dynamic DNS (if you are behind a dynamic IP)
  • Automatic updating of TXT for Letsencrypt (if you are running your own webserver)
  • Round Robin DNS for Loadbalancing / Failover (if you are running your own webservers)

The REST API can only update existing entries, not create new ones, so you have to create the entry in the my-webspace.at panel first.
Please keep in mind that the key must be kept private! With the key anyone could change your DNS records. If you think you key has been compromised, please delete the DNS entry in the my-webspace.at panel and re-create it. A new key will be provided for you.

At the moment you can use the API to update A, AAAA and TXT records. The API can be accessed via HTTPS (preferred) or plain HTTP:

Endpoint https http
Default protocol https://panel.my-webspace.at/dns http://panel.my-webspace.at/dns
IPv4 https://4.panel.my-webspace.at/dns http://4.panel.my-webspace.at/dns
IPv6 https://6.panel.my-webspace.at/dns http://6.panel.my-webspace.at/dns

You can supply the following parameters, either via GET or POST:

Parameter Value
key Autoupdate-Key from the panel, mandatory to query or change DNS-records
a Only for A records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv4 address. When using the "remote" feature the endpoint 4.panel.my-webspace.at should be used to ensure IPv4 is being used for the request and a valid IP address is returned for the record type.
aaaa Only for AAAA records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv6 address. When using the "remote" feature the endpoint 6.panel.my-webspace.at should be used to ensure IPv6 is being used for the request and a valid IP address is returned for the record type.
txt Only for TXT records, the new content of the record

If no new record data is provided, only the existing data is returned.
The response is a JSON object with the following values:

Key Value
status "error": In case of an error, more information is provided in the "error" key
"unchanged": The current value was already stored in the DNS record
"updated": The DNS record has been updated and the changes will be reflected in the DNS soon
error Only if status == "error", the error message. One of "bad key", "key missing", "invalid A data" or "invalid AAAA data"
domain The top-level domain being changed or queried
name The subdomain being changed or queried
type The type of the DNS record
data The (new) value of the DNS record
remote-ip The IP the query originated from. This is always included, even if no parameters are supplied.

Examples

Dynamic DNS

If you have a Linux (or BSD) server behind a dynamic IP Address you can use the following entry in your crontab to update a DNS entry on my-webspace.at to always point to your server:

 15  *  *   *   *    wget -O - 'https://4.panel.my-webspace.at/dns-update.php?key=Key to your A record&a=remote' > /dev/null 2>&1

If you have an IPv6 enabled connection you probably want to update IPv6 entries as well:

 15  *  *   *   *    wget -O - 'https://6.panel.my-webspace.at/dns-update.php?key=Key to your AAAA record&aaaa=remote' > /dev/null 2>&1

Fetch IP address

This API can also be used to fetch the current IP Address. For example with jQuery:

jQuery.get("https://panel.my-webspace.at/dns", function(data) { 
    var your_ip = data["remote-ip"];
    alert("Your IP is " + your_ip);
}, "JSON");

Using the API with Letsencrypt DNS Challenges

A DNS challenge is currently the only way to get wildcard certificates. The MyWebspace DNS API allows you to use this feature.

Step 1: Create a TXT record in the panel, named _acme-challenge.example.com, replace example.com with your actual domain or subdomain. Wildcards only work for one level, so the above entry will work for example.com, foo.example.com and bar.example.com, but not foo.bar.example.com. The data entry of the txt dns-record can be a random string. Note, the entries Autoupdate-key for the next step. This is the key, which you have to use in the 2nd step.

Step 2: Create a file /root/dns-hook.sh on the machine which will receive the certificate. Note that this does not have to be the server which will host the content, but most likely it is:

#!/bin/sh
wget -O - "https://panel.my-webspace.at/dns?key=**key-here**&sync=true&txt=$CERTBOT_VALIDATION" >&2

Don't forget to make it executable: chmod +x /root/dns-hook.sh

Step 3: Run certbot, replace example.com with your actual domain. Remove the -d *.example.com part if you only want a regular certificate, not a wildcard certificate.

certbot certonly --manual --preferred-challenges dns -d 'example.com' -d '*.example.com' --agree-tos --manual-auth-hook /root/dns-hook.sh

Note: You can also use this if your domain is not hosted by MyWebspace, as long as you have at least one MyWebspace hosted domain. Let's assume example.com is at MyWebspace but example.org isn't. You want to create a Certificate for *.example.org. The way you can do this, is that you first create a TXT record in example.com, for example _org-validation.example.com. Use its Autoupdate key in the steps above. Then you create a CNAME record on your other provider. Call it _acme-challenge.example.org and have it point to this new TXT record _org-validation.example.com at MyWebspace. Take into consideration that your external provider may take a while to publish the CNAME, so verify it has before continuing with Step 2.

Server/Docker

Fair sharing of shared resources is important to us. Fair use means unlimited data transfer. However, there is an upper limit for excessive use if other customers are affected by it or the server becomes overloaded. In this case, the customer will be notified and bandwidth may be limited.

MyWebspace provides a simple REST API to update DNS entries automatically. This allows you to do a number of things:

  • Dynamic DNS (if you are behind a dynamic IP)
  • Automatic updating of TXT for Letsencrypt (if you are running your own webserver)
  • Round Robin DNS for Loadbalancing / Failover (if you are running your own webservers)

The REST API can only update existing entries, not create new ones, so you have to create the entry in the my-webspace.at panel first.
Please keep in mind that the key must be kept private! With the key anyone could change your DNS records. If you think you key has been compromised, please delete the DNS entry in the my-webspace.at panel and re-create it. A new key will be provided for you.

At the moment you can use the API to update A, AAAA and TXT records. The API can be accessed via HTTPS (preferred) or plain HTTP:

Endpoint https http
Default protocol https://panel.my-webspace.at/dns http://panel.my-webspace.at/dns
IPv4 https://4.panel.my-webspace.at/dns http://4.panel.my-webspace.at/dns
IPv6 https://6.panel.my-webspace.at/dns http://6.panel.my-webspace.at/dns

You can supply the following parameters, either via GET or POST:

Parameter Value
key Autoupdate-Key from the panel, mandatory to query or change DNS-records
a Only for A records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv4 address. When using the "remote" feature the endpoint 4.panel.my-webspace.at should be used to ensure IPv4 is being used for the request and a valid IP address is returned for the record type.
aaaa Only for AAAA records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv6 address. When using the "remote" feature the endpoint 6.panel.my-webspace.at should be used to ensure IPv6 is being used for the request and a valid IP address is returned for the record type.
txt Only for TXT records, the new content of the record

If no new record data is provided, only the existing data is returned.
The response is a JSON object with the following values:

Key Value
status "error": In case of an error, more information is provided in the "error" key
"unchanged": The current value was already stored in the DNS record
"updated": The DNS record has been updated and the changes will be reflected in the DNS soon
error Only if status == "error", the error message. One of "bad key", "key missing", "invalid A data" or "invalid AAAA data"
domain The top-level domain being changed or queried
name The subdomain being changed or queried
type The type of the DNS record
data The (new) value of the DNS record
remote-ip The IP the query originated from. This is always included, even if no parameters are supplied.

Examples

Dynamic DNS

If you have a Linux (or BSD) server behind a dynamic IP Address you can use the following entry in your crontab to update a DNS entry on my-webspace.at to always point to your server:

 15  *  *   *   *    wget -O - 'https://4.panel.my-webspace.at/dns-update.php?key=Key to your A record&a=remote' > /dev/null 2>&1

If you have an IPv6 enabled connection you probably want to update IPv6 entries as well:

 15  *  *   *   *    wget -O - 'https://6.panel.my-webspace.at/dns-update.php?key=Key to your AAAA record&aaaa=remote' > /dev/null 2>&1

Fetch IP address

This API can also be used to fetch the current IP Address. For example with jQuery:

jQuery.get("https://panel.my-webspace.at/dns", function(data) { 
    var your_ip = data["remote-ip"];
    alert("Your IP is " + your_ip);
}, "JSON");

Using the API with Letsencrypt DNS Challenges

A DNS challenge is currently the only way to get wildcard certificates. The MyWebspace DNS API allows you to use this feature.

Step 1: Create a TXT record in the panel, named _acme-challenge.example.com, replace example.com with your actual domain or subdomain. Wildcards only work for one level, so the above entry will work for example.com, foo.example.com and bar.example.com, but not foo.bar.example.com. The data entry of the txt dns-record can be a random string. Note, the entries Autoupdate-key for the next step. This is the key, which you have to use in the 2nd step.

Step 2: Create a file /root/dns-hook.sh on the machine which will receive the certificate. Note that this does not have to be the server which will host the content, but most likely it is:

#!/bin/sh
wget -O - "https://panel.my-webspace.at/dns?key=**key-here**&sync=true&txt=$CERTBOT_VALIDATION" >&2

Don't forget to make it executable: chmod +x /root/dns-hook.sh

Step 3: Run certbot, replace example.com with your actual domain. Remove the -d *.example.com part if you only want a regular certificate, not a wildcard certificate.

certbot certonly --manual --preferred-challenges dns -d 'example.com' -d '*.example.com' --agree-tos --manual-auth-hook /root/dns-hook.sh

Note: You can also use this if your domain is not hosted by MyWebspace, as long as you have at least one MyWebspace hosted domain. Let's assume example.com is at MyWebspace but example.org isn't. You want to create a Certificate for *.example.org. The way you can do this, is that you first create a TXT record in example.com, for example _org-validation.example.com. Use its Autoupdate key in the steps above. Then you create a CNAME record on your other provider. Call it _acme-challenge.example.org and have it point to this new TXT record _org-validation.example.com at MyWebspace. Take into consideration that your external provider may take a while to publish the CNAME, so verify it has before continuing with Step 2.