{"id":12648,"date":"2025-09-20T14:59:57","date_gmt":"2025-09-20T12:59:57","guid":{"rendered":"https:\/\/webhosting.de\/spf-dkim-dmarc-plesk-guide-sicherheit-tuning-professional\/"},"modified":"2025-09-20T14:59:57","modified_gmt":"2025-09-20T12:59:57","slug":"spf-dkim-dmarc-plesk-guide-safety-tuning-professional","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/spf-dkim-dmarc-plesk-guide-sicherheit-tuning-professional\/","title":{"rendered":"How to configure SPF, DKIM and DMARC correctly in Plesk"},"content":{"rendered":"<p>In this guide, I will show you step by step how to <strong>SPF DKIM<\/strong> and DMARC in Plesk so that your emails are reliably authenticated. You will learn clear procedures for DNS records, Plesk switches and test methods to increase deliverability and block abusive senders.<\/p>\n\n<h2>Key points<\/h2>\n\n<ul>\n  <li><strong>SPF<\/strong> determines which systems are allowed to send mails for your domain.<\/li>\n  <li><strong>DKIM<\/strong> signs outgoing messages and protects against manipulation.<\/li>\n  <li><strong>DMARC<\/strong> links SPF\/DKIM with guidelines and reports.<\/li>\n  <li><strong>Plesk<\/strong> provides wizards and DNS templates for a quick start.<\/li>\n  <li><strong>Monitoring<\/strong> of DMARC reports sharpens your policy in operation.<\/li>\n<\/ul>\n\n<h2>Check prerequisites in Plesk<\/h2>\n\n<p>Before I make any settings, I check the mail server used in <strong>Plesk<\/strong> and DNS management. On Linux I usually work with Postfix, on Windows with SmarterMail, as these services provide SPF, DKIM and DMARC functions. I also check whether the domain has its DNS zones in the Plesk DNS or with an external provider, because I can then manage the entries outside of <strong>Plesk<\/strong> must be added. For smooth operation, I keep the host name, reverse DNS and valid TLS certificates clean, as delivery servers check these points. A clean starting point saves a lot of time later on and strengthens the <strong>Reputation<\/strong>.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk-mailkonfiguration-8192.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Setting up SPF in Plesk - step by step<\/h2>\n\n<p>To get started, I open \"Tools &amp; Settings\" \u2192 \"DNS Settings\" and search for a TXT record that starts with <strong>v=spf1<\/strong> begins. If it is missing, I put it on, for example: <code>v=spf1 a mx include:yourmailprovider.de -all<\/code>so that authorized systems are allowed to send and all others are blocked. If the domain uses additional senders such as Microsoft 365, Google Workspace or newsletter services, I add the appropriate <strong>include<\/strong>-mechanisms from their documentation. After saving, I allow up to 48 hours for the change to take effect globally and test the record with an SPF checker via a test email to a selected mailbox. You can find a compact classification of the interaction of the mechanisms in the <a href=\"https:\/\/webhosting.de\/en\/email-authentication-spf-dkim-dmarc-guide\/\">compact guide<\/a>which explains the most important scenarios.<\/p>\n\n<h2>Activate DKIM in Plesk - this is how you proceed<\/h2>\n\n<p>For <strong>DKIM<\/strong> I go to \"Tools &amp; Settings\" \u2192 \"Mail server settings\" and activate the option to sign outgoing emails. I then open \"Websites &amp; Domains\" at domain level \u2192 Domain \u2192 \"Mail\" \u2192 \"Settings\" and check whether signing is activated for each domain. If I manage DNS externally, I export the data from <strong>Plesk<\/strong> generated DKIM public keys and enter these as TXT records with the DNS provider (note the selector name). After a maximum of 24-48 hours, recipients should validate the DKIM signatures, which I confirm by sending a test mail to a DKIM check mailbox or a header check. A valid signature strengthens the <strong>Deliverability<\/strong> noticeable.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk_spf_dkim_dmarc_9321.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Define DMARC policy and use reports<\/h2>\n\n<p>Now I set <strong>DMARC<\/strong> as TXT record on <code>_dmarc.yourdomain.tld<\/code> with the value <code>v=DMARC1; p=quarantine; rua=mailto:reports@deinedomain.tld; ruf=mailto:forensics@deinedomain.tld; adkim=s; aspf=s<\/code>. The tags <strong>p<\/strong>, <strong>rua<\/strong> and <strong>call<\/strong> control policy and reporting, while <code>adkim<\/code>\/<code>aspf<\/code> define the strict alignment (strict). In practice, I often start with <code>p=none<\/code>evaluate reports for two to four weeks and then move on to <code>quarantine<\/code> or <code>reject<\/code> on. The reports show which systems are sending mails on your behalf and where SPF or DKIM fail, allowing direct corrections to be made. A more detailed sequence of steps describes the <a href=\"https:\/\/webhosting.de\/en\/dmarc-implementation-email-security\/\">DMARC implementation<\/a> with concrete examples.<\/p>\n\n<h2>DNS propagation, tests and best practices<\/h2>\n\n<p>Every DNS change takes time, so I plan up to 48 hours for global DNS changes. <strong>Propagation<\/strong> on. In this phase, I send test mails to external mailboxes and check the authentication results in the header for <strong>spf=pass<\/strong>, <strong>dkim=pass<\/strong> and <strong>dmarc=pass<\/strong>. If a mail receives a <em>softfail<\/em> or <em>Neutral<\/em>I check the SPF mechanisms, the DKIM selectors and the envelope-from (return path) for alignment with From:. When using redirects, I monitor DMARC results, as SPF often breaks there; DKIM usually compensates for this. I avoid <code>~all<\/code> permanently and consistently rely on <strong>-all<\/strong>.<\/p>\n\n<h2>DMARC tags and values - compact table<\/h2>\n\n<p>I use the following overview to <strong>DMARC<\/strong> quickly and reliably and to avoid misinterpretations. I keep the values consistent across main and subdomains and document changes in a traceable manner. For productive domains, I set strict alignment and always activate aggregate reports. Forensic reports (<code>call<\/code>) I plan in compliance with data protection regulations. Setting clear guidelines stabilizes the <strong>Reputation<\/strong> of the domain sustainably.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Day<\/th>\n      <th>Meaning<\/th>\n      <th>Possible values<\/th>\n      <th>Recommendation<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td><strong>p<\/strong><\/td>\n      <td>Policy for main domain<\/td>\n      <td>none, quarantine, reject<\/td>\n      <td>Start with none, then increase to reject<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>sp<\/strong><\/td>\n      <td>Policy for subdomains<\/td>\n      <td>none, quarantine, reject<\/td>\n      <td>sp=reject for productive setups<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>rua<\/strong><\/td>\n      <td>Aggregate reports<\/td>\n      <td>mailto:adresse<\/td>\n      <td>Use your own reporting address<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>call<\/strong><\/td>\n      <td>Forensic reports<\/td>\n      <td>mailto:adresse<\/td>\n      <td>Activate only if necessary<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>adkim<\/strong><\/td>\n      <td>DKIM alignment<\/td>\n      <td>r (relaxed), s (strict)<\/td>\n      <td>adkim=s for clear assignment<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>aspf<\/strong><\/td>\n      <td>SPF alignment<\/td>\n      <td>r (relaxed), s (strict)<\/td>\n      <td>aspf=s for fewer false alarms<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>pct<\/strong><\/td>\n      <td>Percentage of application<\/td>\n      <td>0-100<\/td>\n      <td>Step-by-step tightening with pct<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk-email-sicherheit-einrichten-6283.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Integrate external senders: Microsoft 365, Google, newsletter services<\/h2>\n\n<p>If a domain uses additional shipping paths, I add the SPF includes for <strong>Microsoft<\/strong> 365, Google Workspace, Mailgun, SendGrid or newsletter tools exactly as documented. For each service, I check whether a separate DKIM key is active and whether the from domain is really signed. I avoid duplicate or too many <strong>include<\/strong>-cascades, as SPF is limited to ten DNS lookups. If the budget for lookups is not sufficient, I consolidate senders or move individual streams to subdomains with their own DMARC policy. This is how I keep SPF lean and secure the <strong>Signatures<\/strong> from.<\/p>\n\n<h2>In-depth checks and server selection<\/h2>\n\n<p>For incoming mails I activate in <strong>Plesk<\/strong> checking SPF, DKIM and DMARC so that the server filters spam at an early stage. On Linux, these checks are available by default, while on Windows they are implemented with SmarterMail. I make sure that the mail server is updated properly so that signature routines and parsers remain up to date. If there are problems with false positives, I adjust the scoring thresholds, but never the <strong>Policy<\/strong> of your own domain. This way I keep protection high and ensure that legitimate senders are delivered.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk-konfiguration-office-9284.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Common errors and quick solutions<\/h2>\n\n<p>Meets \"<strong>SPF<\/strong> permerror\", there is usually a syntax error or the lookup limit has been exceeded. If DKIM fails, I check the selector, public key record and the termination of the TXT value with correct quotation marks. If DMARC fails <code>fail<\/code>I first check the alignment: From-Domain, Return-Path and DKIM-d= must match perfectly. If SPF breaks with redirects, I rely on <strong>DKIM<\/strong> and keep the signature status stable. I use this sequence to solve most delivery problems without a long search.<\/p>\n\n<h2>DNS templates and automation in Plesk<\/h2>\n\n<p>If I manage many domains, I set the <strong>DNS template<\/strong> in Plesk and store standard records for SPF, DKIM and DMARC there. New domains immediately receive solid defaults that I only need to fine-tune. I also implement planned changes such as stricter DMARC domain-wide using templates and scripts. For rotations of the DKIM keys, I work with two selectors so that I can make gradual changes. This keeps the operation consistent across dozens of domains and <strong>maintainable<\/strong>.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk_spf_dkim_dmarc_setup_8947.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Evaluate DMARC reports and tighten policy<\/h2>\n\n<p>After the go-live, I evaluate aggregate reports on a daily basis and identify <strong>Sources<\/strong>that send on behalf of the domain without authorization. I block unexpected IPs and clean up outdated tools before I tighten the policy. The change from <code>p=none<\/code> at <code>quarantine<\/code> and later on <code>reject<\/code> I carry out with <code>pct<\/code> in stages so that I can measure effects in a controlled manner. If legitimate senders appear in the failed report, I correct SPF includes or activate my own DKIM key. This routine strengthens the <strong>Reputation<\/strong> visible and reduces spoofing.<\/p>\n\n<h2>Understanding alignment correctly<\/h2>\n\n<p>So that <strong>DMARC<\/strong> I consistently ensure correct alignment. With <strong>SPF<\/strong> is the domain in the envelope from (return path) or the HELO\/EHLO identity, which must match the visible from domain (strict: identical, relaxed: same organizational domain). With <strong>DKIM<\/strong> I check the <code>d=<\/code>-attribute of the signature: It must point to the same domain (strict) or to the same organizational domain (relaxed). In practice, I make sure that:<\/p>\n<ul>\n  <li>the bounce path used (return path) uses a domain that matches the from domain or is deliberately outsourced to a subdomain with its own DMARC policy,<\/li>\n  <li>all third-party providers the From domain <em>sign<\/em> (DKIM), not just their own shipping domain,<\/li>\n  <li>the DKIM signature remains intact during forwarding to compensate for SPF breaks.<\/li>\n<\/ul>\n<p>If alignment is missing, DMARC receivers report an error despite valid SPF\/DKIM <code>dmarc=fail<\/code>. That's why I check the fields in the e-mail headers <code>Authentication results<\/code>, <code>Return path<\/code> and the DKIM parameters. This allows me to quickly recognize whether SPF or DKIM is providing the alignment and where I need to make improvements.<\/p>\n\n<h2>Key management and DNS parameters<\/h2>\n\n<p>For robust <strong>DKIM<\/strong>-setups, I used 2048-bit keys. In <strong>Plesk<\/strong> I can set the key length per domain; I turn up older 1024-bit keys promptly. If necessary, I split long DKIM TXT records into several quotation mark segments so that the DNS server delivers them correctly. I also define meaningful <strong>TTL<\/strong>-values: In rollout phases I go to 300-900 seconds, productively I use 1-4 hours. This allows me to react flexibly to changes without overloading the caches.<\/p>\n<p>The <strong>Rotation<\/strong> I do this without failure with two selectors:<\/p>\n<ol>\n  <li>Create a new selector in Plesk and publish the public key as TXT in the DNS.<\/li>\n  <li>Change the sender to the new selector and observe the monitoring (show headers) <code>s=new selector<\/code>).<\/li>\n  <li>Once all flows have been converted, remove the old selector in the DNS and deactivate it in Plesk.<\/li>\n<\/ol>\n<p>I use third-party providers where possible, <em>delegated<\/em> DKIM records (e.g. CNAME to the provider selector). This allows me to maintain control in my zone and rotate keys without risking operational breaks.<\/p>\n\n<h2>Special cases: Forwarding, mailing lists and gateways<\/h2>\n\n<p>In real environments, I regularly see redirects, mailing lists or security gateways that rewrite emails. I pay particular attention to the effects here:<\/p>\n<ul>\n  <li><strong>Forwarding<\/strong>SPF often breaks because the forwarding IP is not in the SPF of the sender domain. I rely here on <strong>DKIM<\/strong>which provides the content protection. If the signature remains unchanged, DMARC exists via DKIM alignment.<\/li>\n  <li><strong>Mailing lists<\/strong>Many lists change subjects or footers and thus break the DKIM signature. In such cases, I plan relaxed alignment and check whether the list uses SRS\/ARC or its own signatures. If possible, I use a subdomain with its own DMARC policy for lists.<\/li>\n  <li><strong>Security gateways<\/strong>Gateways that re-sign messages or rewrite the envelope-from must be correctly aligned with the sender domain. I document their role and anchor them in the SPF (ip4\/ip6) or via include so that the alignment is maintained.<\/li>\n<\/ul>\n<p>Meet mails with <code>spf=fail<\/code> through a forwarding, this is not automatically critical as long as <code>dkim=pass<\/code> is present and the DKIM alignment is correct. I evaluate the entirety of the authentication results instead of individual signals in isolation.<\/p>\n\n<h2>Shared IPs, HELO\/EHLO and rDNS<\/h2>\n\n<p>If several domains share the same outgoing IP, I rely on clean <strong>rDNS<\/strong> and consistent HELO\/EHLO names. The reverse pointer points to an FQDN (e.g. <em>mail.hosting-example.tld<\/em>), whose A-record points back to the same IP. The MTA responds with exactly this name. I make sure that the <strong>SMTP TLS certificate<\/strong> matches the HELO name (SNI if multiple names are served). For each sender domain, I also ensure that SPF\/DKIM\/DMARC are fully and correctly aligned - the shared IP alone does not affect DMARC as long as authentication is effective.<\/p>\n<p>For dedicated senders (e.g. transactional mail vs. marketing), I like to separate them via subdomains and optionally their own IPs. This helps with <strong>Reputation management<\/strong>simplifies the evaluation of DMARC reports and minimizes mutual interference.<\/p>\n\n<h2>Monitoring and rollout in practice<\/h2>\n\n<p>To ensure smooth operation, I combine continuous <strong>DMARC analysis<\/strong> with clear rollout steps:<\/p>\n<ul>\n  <li><strong>Baseline<\/strong>: 2-4 weeks <code>p=none<\/code>collect all aggregate reports (rua), identify sources of error.<\/li>\n  <li><strong>Cleanup<\/strong>Remove unauthorized senders, clean up SPF includes, activate DKIM on all legitimate systems.<\/li>\n  <li><strong>Dressing<\/strong>With <code>pct<\/code> gradually to <code>quarantine<\/code>, later on <code>reject<\/code> increase, measure effects as a percentage.<\/li>\n  <li><strong>Alerting<\/strong>Define threshold values (new IPs, fail rate per provider, new from domains) and set up notifications.<\/li>\n  <li><strong>Documentation<\/strong>Keep selectors, TTL, key runtimes, SPF budget and responsibilities under version control.<\/li>\n<\/ul>\n<p>I check the <strong>SPF lookup budget<\/strong> (max. 10 mechanisms with DNS queries) and consolidate includes. Critical mechanisms such as <code>ptr<\/code> or <code>+all<\/code> I generally do not use them; <code>ip4<\/code>\/<code>ip6<\/code>, <code>a<\/code>, <code>mx<\/code> and targeted <code>include<\/code> remain the means of choice. This is how I keep the setup stable and auditable.<\/p>\n\n<h2>Quick check for each domain<\/h2>\n\n<p>At the end of each installation, I run a fixed <strong>Check<\/strong> through: SPF record available, lookup budget under ten, mechanisms correctly sorted, <code>-all<\/code> Active. DKIM signature valid, selector documented, key length sufficient, rotation planned. DMARC with valid TXT record, strict alignment, reporting mailboxes accessible and archived. Show test mails <code>spf=pass<\/code>, <code>dkim=pass<\/code> and <code>dmarc=pass<\/code> in the header. I use this sequence to keep setups reproducible and <strong>low error<\/strong>.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/plesk-spf-dkim-dmarc-3197.png\" alt=\"\" width=\"1536\" height=\"1024\" \/>\n<\/figure>\n\n\n<h2>Practical summary for quick success<\/h2>\n\n<p>I start every project with clear <strong>Standards<\/strong>Keep SPF lean, activate DKIM for each sender and roll out DMARC with reporting. This is followed by two to four weeks of monitoring to close blind spots and tighten guidelines. I integrate external services in a controlled manner, document includes and keep the lookup budget under control. I use DNS templates for several domains and plan rotations of DKIM keys to keep the signatures fresh. I summarize useful practical ideas and troubleshooting tips in my <a href=\"https:\/\/webhosting.de\/en\/email-security-plesk-tips-2025-protection\/\">Plesk tips 2025<\/a> together so that you can maintain a strong <strong>Deliverability<\/strong> reach.<\/p>","protected":false},"excerpt":{"rendered":"<p>Learn how to set up SPF, DKIM and DMARC correctly in Plesk. Protect your email communication with our step-by-step guide! Focus: spf dkim dmarc plesk.<\/p>","protected":false},"author":1,"featured_media":12641,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_crdt_document":"","inline_featured_image":false,"footnotes":""},"categories":[791],"tags":[],"class_list":["post-12648","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-emailserver-administration-anleitungen"],"acf":[],"_wp_attached_file":null,"_wp_attachment_metadata":null,"litespeed-optimize-size":null,"litespeed-optimize-set":null,"_elementor_source_image_hash":null,"_wp_attachment_image_alt":null,"stockpack_author_name":null,"stockpack_author_url":null,"stockpack_provider":null,"stockpack_image_url":null,"stockpack_license":null,"stockpack_license_url":null,"stockpack_modification":null,"color":null,"original_id":null,"original_url":null,"original_link":null,"unsplash_location":null,"unsplash_sponsor":null,"unsplash_exif":null,"unsplash_attachment_metadata":null,"_elementor_is_screenshot":null,"surfer_file_name":null,"surfer_file_original_url":null,"envato_tk_source_kit":null,"envato_tk_source_index":null,"envato_tk_manifest":null,"envato_tk_folder_name":null,"envato_tk_builder":null,"envato_elements_download_event":null,"_menu_item_type":null,"_menu_item_menu_item_parent":null,"_menu_item_object_id":null,"_menu_item_object":null,"_menu_item_target":null,"_menu_item_classes":null,"_menu_item_xfn":null,"_menu_item_url":null,"_trp_menu_languages":null,"rank_math_primary_category":null,"rank_math_title":null,"inline_featured_image":null,"_yoast_wpseo_primary_category":null,"rank_math_schema_blogposting":null,"rank_math_schema_videoobject":null,"_oembed_049c719bc4a9f89deaead66a7da9fddc":null,"_oembed_time_049c719bc4a9f89deaead66a7da9fddc":null,"_yoast_wpseo_focuskw":null,"_yoast_wpseo_linkdex":null,"_oembed_27e3473bf8bec795fbeb3a9d38489348":null,"_oembed_c3b0f6959478faf92a1f343d8f96b19e":null,"_trp_translated_slug_en_us":null,"_wp_desired_post_slug":null,"_yoast_wpseo_title":null,"tldname":null,"tldpreis":null,"tldrubrik":null,"tldpolicylink":null,"tldsize":null,"tldregistrierungsdauer":null,"tldtransfer":null,"tldwhoisprivacy":null,"tldregistrarchange":null,"tldregistrantchange":null,"tldwhoisupdate":null,"tldnameserverupdate":null,"tlddeletesofort":null,"tlddeleteexpire":null,"tldumlaute":null,"tldrestore":null,"tldsubcategory":null,"tldbildname":null,"tldbildurl":null,"tldclean":null,"tldcategory":null,"tldpolicy":null,"tldbesonderheiten":null,"tld_bedeutung":null,"_oembed_d167040d816d8f94c072940c8009f5f8":null,"_oembed_b0a0fa59ef14f8870da2c63f2027d064":null,"_oembed_4792fa4dfb2a8f09ab950a73b7f313ba":null,"_oembed_33ceb1fe54a8ab775d9410abf699878d":null,"_oembed_fd7014d14d919b45ec004937c0db9335":null,"_oembed_21a029d076783ec3e8042698c351bd7e":null,"_oembed_be5ea8a0c7b18e658f08cc571a909452":null,"_oembed_a9ca7a298b19f9b48ec5914e010294d2":null,"_oembed_f8db6b27d08a2bb1f920e7647808899a":null,"_oembed_168ebde5096e77d8a89326519af9e022":null,"_oembed_cdb76f1b345b42743edfe25481b6f98f":null,"_oembed_87b0613611ae54e86e8864265404b0a1":null,"_oembed_27aa0e5cf3f1bb4bc416a4641a5ac273":null,"_oembed_time_27aa0e5cf3f1bb4bc416a4641a5ac273":null,"_tldname":null,"_tldclean":null,"_tldpreis":null,"_tldcategory":null,"_tldsubcategory":null,"_tldpolicy":null,"_tldpolicylink":null,"_tldsize":null,"_tldregistrierungsdauer":null,"_tldtransfer":null,"_tldwhoisprivacy":null,"_tldregistrarchange":null,"_tldregistrantchange":null,"_tldwhoisupdate":null,"_tldnameserverupdate":null,"_tlddeletesofort":null,"_tlddeleteexpire":null,"_tldumlaute":null,"_tldrestore":null,"_tldbildname":null,"_tldbildurl":null,"_tld_bedeutung":null,"_tldbesonderheiten":null,"_oembed_ad96e4112edb9f8ffa35731d4098bc6b":null,"_oembed_8357e2b8a2575c74ed5978f262a10126":null,"_oembed_3d5fea5103dd0d22ec5d6a33eff7f863":null,"_eael_widget_elements":null,"_oembed_0d8a206f09633e3d62b95a15a4dd0487":null,"_oembed_time_0d8a206f09633e3d62b95a15a4dd0487":null,"_aioseo_description":null,"_eb_attr":null,"_eb_data_table":null,"_oembed_819a879e7da16dd629cfd15a97334c8a":null,"_oembed_time_819a879e7da16dd629cfd15a97334c8a":null,"_acf_changed":null,"_wpcode_auto_insert":null,"_edit_last":null,"_edit_lock":null,"_oembed_e7b913c6c84084ed9702cb4feb012ddd":null,"_oembed_bfde9e10f59a17b85fc8917fa7edf782":null,"_oembed_time_bfde9e10f59a17b85fc8917fa7edf782":null,"_oembed_03514b67990db061d7c4672de26dc514":null,"_oembed_time_03514b67990db061d7c4672de26dc514":null,"rank_math_news_sitemap_robots":null,"rank_math_robots":null,"_eael_post_view_count":"2587","_trp_automatically_translated_slug_ru_ru":null,"_trp_automatically_translated_slug_et":null,"_trp_automatically_translated_slug_lv":null,"_trp_automatically_translated_slug_fr_fr":null,"_trp_automatically_translated_slug_en_us":null,"_wp_old_slug":null,"_trp_automatically_translated_slug_da_dk":null,"_trp_automatically_translated_slug_pl_pl":null,"_trp_automatically_translated_slug_es_es":null,"_trp_automatically_translated_slug_hu_hu":null,"_trp_automatically_translated_slug_fi":null,"_trp_automatically_translated_slug_ja":null,"_trp_automatically_translated_slug_lt_lt":null,"_elementor_edit_mode":null,"_elementor_template_type":null,"_elementor_version":null,"_elementor_pro_version":null,"_wp_page_template":null,"_elementor_page_settings":null,"_elementor_data":null,"_elementor_css":null,"_elementor_conditions":null,"_happyaddons_elements_cache":null,"_oembed_75446120c39305f0da0ccd147f6de9cb":null,"_oembed_time_75446120c39305f0da0ccd147f6de9cb":null,"_oembed_3efb2c3e76a18143e7207993a2a6939a":null,"_oembed_time_3efb2c3e76a18143e7207993a2a6939a":null,"_oembed_59808117857ddf57e478a31d79f76e4d":null,"_oembed_time_59808117857ddf57e478a31d79f76e4d":null,"_oembed_965c5b49aa8d22ce37dfb3bde0268600":null,"_oembed_time_965c5b49aa8d22ce37dfb3bde0268600":null,"_oembed_81002f7ee3604f645db4ebcfd1912acf":null,"_oembed_time_81002f7ee3604f645db4ebcfd1912acf":null,"_elementor_screenshot":null,"_oembed_7ea3429961cf98fa85da9747683af827":null,"_oembed_time_7ea3429961cf98fa85da9747683af827":null,"_elementor_controls_usage":null,"_elementor_page_assets":[],"_elementor_screenshot_failed":null,"theplus_transient_widgets":null,"_eael_custom_js":null,"_wp_old_date":null,"_trp_automatically_translated_slug_it_it":null,"_trp_automatically_translated_slug_pt_pt":null,"_trp_automatically_translated_slug_zh_cn":null,"_trp_automatically_translated_slug_nl_nl":null,"_trp_automatically_translated_slug_pt_br":null,"_trp_automatically_translated_slug_sv_se":null,"rank_math_analytic_object_id":null,"rank_math_internal_links_processed":null,"_trp_automatically_translated_slug_ro_ro":null,"_trp_automatically_translated_slug_sk_sk":null,"_trp_automatically_translated_slug_bg_bg":null,"_trp_automatically_translated_slug_sl_si":null,"litespeed_vpi_list":null,"litespeed_vpi_list_mobile":null,"rank_math_seo_score":null,"rank_math_contentai_score":null,"ilj_limitincominglinks":null,"ilj_maxincominglinks":null,"ilj_limitoutgoinglinks":null,"ilj_maxoutgoinglinks":null,"ilj_limitlinksperparagraph":null,"ilj_linksperparagraph":null,"ilj_blacklistdefinition":null,"ilj_linkdefinition":null,"_eb_reusable_block_ids":null,"rank_math_focus_keyword":"SPF DKIM","rank_math_og_content_image":null,"_yoast_wpseo_metadesc":null,"_yoast_wpseo_content_score":null,"_yoast_wpseo_focuskeywords":null,"_yoast_wpseo_keywordsynonyms":null,"_yoast_wpseo_estimated-reading-time-minutes":null,"rank_math_description":null,"surfer_last_post_update":null,"surfer_last_post_update_direction":null,"surfer_keywords":null,"surfer_location":null,"surfer_draft_id":null,"surfer_permalink_hash":null,"surfer_scrape_ready":null,"_thumbnail_id":"12641","footnotes":null,"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=12648"}],"version-history":[{"count":0,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12648\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/12641"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=12648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=12648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=12648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}