{"id":19441,"date":"2026-05-17T15:04:36","date_gmt":"2026-05-17T13:04:36","guid":{"rendered":"https:\/\/webhosting.de\/mailserver-spf-alignment-dmarc-policies-guide-sicherheit\/"},"modified":"2026-05-17T15:04:36","modified_gmt":"2026-05-17T13:04:36","slug":"mailserver-spf-alignment-dmarc-policies-guide-security","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/mailserver-spf-alignment-dmarc-policies-guide-sicherheit\/","title":{"rendered":"Understanding mail server SPF alignment and DMARC policies"},"content":{"rendered":"<p><strong>SPF DMARC<\/strong> decides today whether mail servers accept, quarantine or completely reject your messages. I explain how mail server SPF alignment and DMARC policies work together, where errors occur and how you can increase delivery, authenticity and brand trust step by step.<\/p>\n\n<h2>Key points<\/h2>\n\n<p>I will summarize the most important findings so that you can make the right adjustments straight away. <strong>SPF<\/strong> determines which servers are allowed to send, but only the alignment links this technology with the visible sender domain. <strong>DMARC<\/strong> controls the recipient's reaction and provides reports that I use for optimization. Without proper alignment, you will lose delivery, even if individual checks pass. I therefore plan sender paths, return paths and DKIM domains consistently with the main domain. In this way, I gradually build up protection without jeopardizing legitimate emails.<\/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\/2026\/05\/mailserver-sicherheit-2984.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<ul>\n  <li><strong>Alignment<\/strong> decides: From, return path and DKIM domain must match the main domain.<\/li>\n  <li><strong>DMARC Policy<\/strong> controls: none, quarantine, reject - tighten step by step.<\/li>\n  <li><strong>SPF<\/strong> clean up: one record, clear includes, no duplicates.<\/li>\n  <li><strong>DKIM<\/strong> signed: unique keys, rotation, valid selector.<\/li>\n  <li><strong>Reporting<\/strong> use: Read reports, consolidate dispatch paths.<\/li>\n<\/ul>\n\n<h2>SPF briefly explained: the sender list in the DNS<\/h2>\n\n<p>I define in the DNS which systems are allowed to send e-mails for my domain and thus secure the <strong>Shipping route<\/strong>. A single SPF record bundles all IPs and includes so that providers can clearly evaluate the check. I keep the record lean, limit DNS lookups and remove old entries that are not relevant. <strong>Purpose<\/strong> have more. A hard qualifier (-all) marks everything unknown as unauthorized as soon as all legitimate paths are correct. If you want to delve deeper, you will find practical steps in this compact <a href=\"https:\/\/webhosting.de\/en\/spf-dkim-dmarc-hosting-email-security-serverauth-server\/\">Guide to e-mail authentication<\/a>which I use as a checklist.<\/p>\n\n<h2>SPF alignment in practice: visible from meets return path<\/h2>\n\n<p>I first check whether the domain in the visible From matches the domain of the return path, because that's where the <strong>Alignment<\/strong>. DMARC accepts relaxed alignment if both are under the same main organizational domain; strictly means: exact match. I set up external delivery services so that the bounce handler uses a subdomain of my main domain. In this way, I clearly link the technical check and the visible sender and set a <strong>Standard<\/strong>, of the delivery. Incorrect return paths often break the alignment unnoticed - I check this consistently with every new integration.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/05\/Mailserver_DMARC_Meeting_4532.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Understanding DMARC: Policy, Alignment and Reports<\/h2>\n\n<p>DMARC evaluates each message based on SPF and DKIM and checks with a <strong>Policy<\/strong>, what happens in case of errors. I start with p=none, read reports and identify all legitimate sources before going to quarantine or reject. I use aspf and adkim to determine whether I require relaxed or strict alignment for SPF and DKIM. I set rua for aggregate reports and usually do without ruf in the beginning to keep the volume manageable. This is how I build a <strong>Image<\/strong> of all shipping routes and quickly detect misuse.<\/p>\n\n<h2>DMARC policies in comparison: impact and use<\/h2>\n\n<p>The choice of level influences delivery and protection, which is why I make it based on data after evaluating the <strong>Reports<\/strong>. First I secure SPF and DKIM for each path, then I tighten the policy. I often combine stricter alignment with DKIM because redirects occasionally break SPF. In this table you can see the main differences that I take into account when planning. So the <strong>Control<\/strong> with you at any time.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Policy<\/th>\n      <th>Effect on fail<\/th>\n      <th>Recommended for<\/th>\n      <th>Note<\/th>\n      <th>Example record<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td><strong>none<\/strong><\/td>\n      <td>No enforcement<\/td>\n      <td>Start-up phase, stocktaking<\/td>\n      <td>Collect reports, close gaps<\/td>\n      <td>v=DMARC1; p=none; rua=mailto:reports@domain.de; aspf=r; adkim=r<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>quarantine<\/strong><\/td>\n      <td>Spam\/junk folder<\/td>\n      <td>Transition after adjustment<\/td>\n      <td>Visible effect, moderate risk<\/td>\n      <td>v=DMARC1; p=quarantine; rua=mailto:reports@domain.de; aspf=r; adkim=r<\/td>\n    <\/tr>\n    <tr>\n      <td><strong>reject<\/strong><\/td>\n      <td>Rejection<\/td>\n      <td>Final enforcement<\/td>\n      <td>Only according to stable test paths<\/td>\n      <td>v=DMARC1; p=reject; rua=mailto:reports@domain.de; aspf=s; adkim=s<\/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\/2026\/05\/mailserver-spf-dmarc-policies-2047.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Typical mistakes and how I fix them<\/h2>\n\n<p>I often see several SPF records per domain, which simplifies the evaluation at the recipient's end. <strong>confused<\/strong>. I therefore consolidate everything into one entry and remove contradictory texts. Another classic case: external tools send with your From domain, but are not in the SPF or do not sign with your DKIM domain. I correct the return path to a separate subdomain and activate DKIM with a selector from your domain. Only when all paths match properly do I set a stricter <strong>Policy<\/strong>, so that legitimate mails are not lost.<\/p>\n\n<h2>Hosting and infrastructure: what I look out for<\/h2>\n\n<p>I choose a provider that offers DNS management, DKIM signature on the server and clear wizards for <strong>Entries<\/strong> offers. A mail infrastructure with a good reputation helps because large providers use strict filtering. I prefer environments in which I can quickly set subdomains, selectors and reporting addresses. For admin setups with Plesk, this <a href=\"https:\/\/webhosting.de\/en\/spf-dkim-dmarc-plesk-guide-safety-tuning-professional\/\">Plesk-Guide<\/a> helpful steps that I often use in projects. This is how I keep changes clear and ensure the <strong>Delivery<\/strong> sustainably.<\/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\/2026\/05\/techoffice_mailserver_spf_dmarc_4352.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Step-by-step introduction: from monitoring to enforcement<\/h2>\n\n<p>I start every project with a complete inventory of all shipping paths so that I don't have to make any <strong>Source<\/strong> forget. Then I clean up the SPF record and enable DKIM on every system that sends mail. I set DMARC to p=none, collect reports and compare them with my inventory. As soon as everything is properly authenticated and aligned, I change the policy to quarantine. With sufficiently stable numbers, I gradually go to reject and thus create clear <strong>Boundaries<\/strong> for abuse.<\/p>\n\n<h2>Evaluating reporting: from data to decisions<\/h2>\n\n<p>Aggregate reports show me which IPs, from-domains and result values appear so that I can <strong>Anomalies<\/strong> recognize. I group by source, see fail rates and check whether alignment or signature is missing. If new IPs appear, I decide whether to include them in SPF or block them. For the evaluation, I use tools that prepare the XML data in an understandable way and make trends visible. A good starting point is this compact introduction to <a href=\"https:\/\/webhosting.de\/en\/dmarc-reports-spoofing-analyze-securenet\/\">Analyze DMARC reports<\/a>, which I like to call <strong>Reference<\/strong> use.<\/p>\n\n<h2>Redirects, DKIM and the right order<\/h2>\n\n<p>Classic redirects can break SPF because the redirecting IP is not in the SPF of the original domain. <strong>stands<\/strong>. I therefore additionally secure consignments with DKIM, because the signature survives clean forwarding. I pay attention to a clear sequence: first fix all sender paths, then monitoring, then step-by-step enforcement. This reduces risk and saves time when troubleshooting if individual paths are not yet running properly. If you proceed in this way, you keep the <strong>Error rate<\/strong> permanently low.<\/p>\n\n<p>In more complex chains, I also use standards that make forwarding more robust. With SRS (Sender Rewriting Scheme), the envelope from the redirector can be rewritten so that SPF can be correct again. This is not part of DMARC, but is useful if you cannot do without domain forwarding. For mailing lists and gateways that change content, I take into account that DKIM signatures can break; here I support recipient chains with ARC (Authenticated Received Chain) so that previous checks remain traceable. I consciously plan for these special cases and test them with realistic scenarios before tightening the policy.<\/p>\n\n<h2>SPF in detail: mechanisms, limits and clean structure<\/h2>\n\n<p>I keep SPF technically stable and maintainable. The 10-lookup principle is non-negotiable: include, a, mx, exists and redirect all count. I consolidate includes, remove cascades and avoid \u201eflat\u201c copy-paste of entire IP lists without a lifecycle because they quickly become obsolete. I use redirect specifically when a subdomain is to inherit the exact SPF of the main domain - include remains my tool for connecting other legitimate sources. I do not use ptr; it is unreliable and is not recommended. I define clear networks via ip4\/ip6 with appropriate CIDR masks and deliberately set the qualifiers: + (implicit), ~softfail for transitions and -fail once the inventory is complete.<\/p>\n\n<p>I structure the SPF record in such a way that the most frequent hits appear early (short evaluation path) and define a practical TTL so that I can roll out changes in a controlled manner. I check separate SPF identities for HELO\/EHLO if systems support this, as some recipients also evaluate the HELO identity. I bind the envelope-from (return path) to a separate subdomain that matches my monitoring and ensure that a suitable SPF record is also located there. In this way, I keep both the technical check and the operational view together.<\/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\/2026\/05\/entwickler_schreibtisch_code_3821.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Roll out DKIM correctly: Key, header and rotation<\/h2>\n\n<p>I use 2048-bit RSA keys as standard and plan a regular rotation with clear selector names (e.g. based on year or quarter). The selector is uniquely assigned to each sending system so that I can exchange keys with minimal compromise. I sign the relevant headers (From is mandatory, usually Date, Subject, To, Message-ID) and oversign From to prevent manipulation. For canonicalization, I choose c=relaxed\/relaxed because in practice it is robust against trivial format changes. I do not set the l= tag (body length) as it can open up scope for misuse and makes verification more fragile.<\/p>\n\n<p>I make sure that the DKIM domain (d=) matches the main organizational domain and contributes to DMARC alignment. For external senders, I configure a separate subdomain if possible and have it signed with my selector. I do not set test flags permanently: t=y is only intended for short test phases, t=s (strict) restricts subdomain matches and does not fit into every alignment concept. I plan DNS TTLs for the DKIM keys in such a way that rotation within a maintenance window is possible without long waiting times - first publish, then change over production systems, then remove old keys in an orderly fashion.<\/p>\n\n<h2>Subdomain strategy and staging: sp=, pct= and clean sender paths<\/h2>\n\n<p>I separate roles via subdomains: transactional, marketing, support and system messages run on clearly named paths with their own bounce handling. In DMARC, I use sp= to enforce subdomains separately if the main domain is still in monitoring. For risk-free rollouts, I use pct= to scale in stages until all legitimate sources are stable. I use ri to regulate the report cycle if the volume becomes too high and store several recipients in rua to separate operational and security-relevant evaluations. This allows me to have granular control without unnecessarily jeopardizing productive traffic.<\/p>\n\n<h2>BIMI: Visibility as a bonus on a DMARC basis<\/h2>\n\n<p>I see BIMI as a visible trust accelerator that is based on clean DMARC. The prerequisite is an enforced policy (quarantine or reject) and consistent alignment. I ensure a clean, consistent brand logo and clear sender conventions so that the display does not appear random. A Verified Mark Certificate can also increase acceptance; however, I only plan to use it once SPF, DKIM and DMARC are running reliably. This way, BIMI becomes the reward effect of an already robust email authentication and not a risky shortcut.<\/p>\n\n<h2>Operating routine and troubleshooting: control changes, find errors quickly<\/h2>\n\n<p>I keep a lean change log for DNS, SPF, DKIM and DMARC changes, set appropriate TTLs and roll out adjustments in maintenance windows. We define alerts based on data: rising DMARC fail rates, new unknown IPs or falling DKIM pass rates trigger notifications. I also monitor operational KPIs such as bounce and complaint rates, delivery times and spam folder percentages. This combination of technical and delivery metrics prevents us from only collecting \u201egreen ticks\u201c but overlooking real problems in the inbox.<\/p>\n\n<p>In the analysis, I start with the headers: Received-SPF shows me the identity and result (pass\/softfail\/fail) and which domain was checked (HELO vs. MailFrom). Authentication-Results lists dkim=pass\/fail with d= and s= as well as dmarc=pass\/fail plus applied policy. If SPF=pass, but DMARC fails, I look at the alignment: Does the From domain match the return path or the DKIM domain in organizational terms? If mailing list signatures break through footer\/subject prefixes, I choose more robust signatures and rely more heavily on DKIM alignment. In this way, the actual cause can be pinpointed and rectified in just a few steps.<\/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\/2026\/05\/mailserver-buero-9023.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Requirements of large providers: what I also consider<\/h2>\n\n<p>Large mailboxes have tightened their rules: an enforced DMARC policy, clean list hygiene and low complaint rates are basic requirements today. I set the list unsubscribe headers consistently (including the one-click variant), keep reverse DNS and EHLO hostnames stable and enforce TLS in transport where possible. I ramp up high volumes in a controlled manner to build reputation and isolate marketing traffic to my own subdomains. In this way, I meet the expectations of modern providers and translate authentication directly into delivery quality.<\/p>\n\n<h2>Data protection for forensic reports: making a conscious decision<\/h2>\n\n<p>I only activate ruf selectively because forensic reports can contain personal content and the volume is difficult to calculate. When I set ruf, I store and process the data restrictively, minimize retention times and check the legal basis. I use fo to control the scope, and aggregate reports are usually all I need to make decisions. In this way, I maintain data protection and still receive the information I need for optimization.<\/p>\n\n<h2>Brief summary: what is important now<\/h2>\n\n<p>I rely on consistent <strong>Alignment<\/strong> between From, Return-Path and DKIM-Domain, because this is where delivery is decided. I clean up SPF, activate DKIM on all sources and start DMARC with p=none for meaningful reports. With a clear data basis, I tighten the policy to quarantine and later to reject. I continuously monitor reports and adjust includes, selectors and sender paths when systems change. In this way, I ensure authenticity, reduce misuse and increase the <strong>Trustworthiness<\/strong> every mail that bears your name.<\/p>","protected":false},"excerpt":{"rendered":"<p>Comprehensive guide to mail server SPF alignment and DMARC policies: How to optimize email security and deliverability with the focus keyword SPF alignment DMARC.<\/p>","protected":false},"author":1,"featured_media":19434,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_crdt_document":"","inline_featured_image":false,"footnotes":""},"categories":[708],"tags":[],"class_list":["post-19441","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email"],"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":"73","_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":"1","_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 DMARC","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":"19434","footnotes":null,"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/19441","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=19441"}],"version-history":[{"count":0,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/19441\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/19434"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=19441"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=19441"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=19441"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}