{"id":19761,"date":"2026-06-07T08:36:35","date_gmt":"2026-06-07T06:36:35","guid":{"rendered":"https:\/\/webhosting.de\/mailserver-header-analysis-spam-check\/"},"modified":"2026-06-07T08:36:35","modified_gmt":"2026-06-07T06:36:35","slug":"mailserver-header-analysis-spam-check","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/mailserver-header-analysis-spam-check\/","title":{"rendered":"Mailserver Header Analysis: Detect spam reliably"},"content":{"rendered":"<p>I reliably recognize spam when I see the <strong>Mail server header<\/strong> and evaluate the technical traces. The targeted header analysis shows the origin, transport route and authentication of a message and thus exposes deceptions and delivery errors quickly and reliably.<\/p>\n\n<h2>Key points<\/h2>\n\n<p>I rely on the complete <strong>Raw header<\/strong> and read the server chain backwards. I check the IP, host name and timestamp step by step. I evaluate the results for SPF, DKIM and DMARC in combination, not in isolation. I classify conspicuous received lines, inconsistent sender domains and manipulable fields in context. In the end, a clear picture emerges as to whether a message is legitimate or not. <strong>Spam<\/strong>.<\/p>\n<ul>\n  <li><strong>Received chain<\/strong> read backwards<\/li>\n  <li><strong>SPF\/DKIM\/DMARC<\/strong> Check in the network<\/li>\n  <li><strong>Sender IP<\/strong> and compare host names<\/li>\n  <li><strong>Return path<\/strong> match against header data<\/li>\n  <li><strong>Timestamp<\/strong> Check for plausibility<\/li>\n<\/ul>\n\n<h2>What does a mail server header really show?<\/h2>\n\n<p>A header contains technical <strong>Metadata<\/strong>, that mail programs often hide. I read the sender address, recipient, timestamp and each server station of the delivery. The Received, Return-Path and Authentication-Results fields are particularly important. They reveal the actual sender IP and the documented delivery route. It is precisely these signals that expose phishing and false <strong>Sender<\/strong> despite clean contents.<\/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\/06\/mailserver-analyse-4892.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Read the received chain securely<\/h2>\n\n<p>I start at the lower end of the <strong>Received<\/strong>-chain, because the starting point of the journey is there. Each line is written by the server that accepts the mail, making it easier to trace. If the host name, IP address and timestamp match, the route seems plausible. If entries do not match, I check possible forwarding or filter stations. For me, unknown hosts between known nodes are a strong <strong>warning signal<\/strong>.<\/p>\n\n<h2>Evaluate SPF, DKIM and DMARC in the header<\/h2>\n\n<p>In Authentication-Results I search for <strong>SPF<\/strong>, DKIM and DMARC with clear pass or fail information. An SPF pass alone is not enough, because the alignment and identity of the domain must match the visible address. DMARC gives me the hardest statement because it bundles the SPF and DKIM check at domain level. If signature stability is missing, I check for causes such as redirects or mailing lists. For policies and alignment, I take a look at <a href=\"https:\/\/webhosting.de\/en\/mailserver-spf-alignment-dmarc-policies-guide-security\/\">SPF alignment and DMARC<\/a>, to clearly explain outliers.<\/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\/06\/header_analysis_1234.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Quickly recognize warning signals in the header<\/h2>\n\n<p>I react immediately when the sender domain and <strong>Return path<\/strong> do not belong together. Conflicting time zones between received lines often indicate manipulation or unusual detours. A sender IP from a foreign network rarely matches a major brand. I expect missing or incorrect authentication, especially in the case of mass mails of questionable origin. If, on the other hand, the route, signature and domain are correct, my <strong>Risk<\/strong> clearly.<\/p>\n\n<h2>Improve deliverability with header data<\/h2>\n\n<p>I use headers to target delivery errors. <strong>diagnose<\/strong>. If mails appear in spam folders, I first look for DKIM errors or SPF abuse. Unexpected intermediate stations can indicate forwarding or filter rules. I often find blocklist clues in additional fields on individual servers. This is how I recognize which site is blocking the <strong>shipping<\/strong> really slows you down.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Header field<\/th>\n      <th>Note<\/th>\n      <th>Typical action<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Received<\/td>\n      <td><strong>Transport route<\/strong> implausible<\/td>\n      <td>Check DNS\/reverse, clarify redirects<\/td>\n    <\/tr>\n    <tr>\n      <td>Authentication results<\/td>\n      <td><strong>SPF\/DKIM<\/strong> Fail<\/td>\n      <td>Correct record, rotate key<\/td>\n    <\/tr>\n    <tr>\n      <td>Return path<\/td>\n      <td><strong>Envelope<\/strong> deviating<\/td>\n      <td>Comparison with shipping service\/address<\/td>\n    <\/tr>\n    <tr>\n      <td>Message ID<\/td>\n      <td><strong>Format<\/strong> suspicious<\/td>\n      <td>Check generation system<\/td>\n    <\/tr>\n    <tr>\n      <td>Date\/Received<\/td>\n      <td><strong>Times<\/strong> inconsistent<\/td>\n      <td>Synchronize time zones\/server time<\/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\/06\/mailserver-header-analysis-2948.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Practical procedure: from the copied header to the evaluation<\/h2>\n\n<p>I always copy the complete <strong>Header<\/strong> from the mail program, not just excerpts. I then read the received chain from bottom to top and highlight any anomalies. I match the sender IP with the claimed host name and domain. Only then do I evaluate SPF, DKIM and DMARC together. I summarize the final evaluation in short notes, <strong>Identity<\/strong> and signature together.<\/p>\n\n<h2>Weighing up tools against manual testing<\/h2>\n\n<p>Automatic evaluators save me <strong>Time<\/strong>, but do not replace an eye for detail. I use tools to quickly parse fields and detect format errors. I make the actual decision manually, especially for borderline cases or redirects. For content filters, I also use statistical methods. I get an overview of procedures such as <a href=\"https:\/\/webhosting.de\/en\/bayesian-heuristic-spam-filter-hosting-comparison-technology\/\">Compare Bayesian filters<\/a>, which I combine with header results.<\/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\/06\/mailserveranalyse_nacht_tech8001.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Determine a trustworthy first hop<\/h2>\n\n<p>I decide at the beginning which <strong>Received<\/strong>-line as the first trustworthy hop. Everything above the entry written by my own incoming server is potentially forgeable. That's why I compare the <em>by=<\/em>-attribute with my gateway hostname and ignore lines above it if they are not from systems that I control. This prevents falsified received lines from distorting my rating.<\/p>\n\n<h2>Envelope vs. visible sender<\/h2>\n\n<p>I make a strict distinction between <strong>Envelope sender<\/strong> (MAIL FROM\/Return-Path) and the visible From address. The field <em>Transmitter<\/em> shows me a technical shipping system if necessary, <em>Reply-To<\/em> defines the response address. If these fields differ greatly, I increase the caution. For redirects, I pay attention to <em>SRS<\/em> (Sender Rewriting Scheme): An altered return path with SRS marking often explains an SPF fail on the end system without fraud. Plus addressing (<em>user+tag@<\/em>) in the envelope to recognize bulk mailing and tracking.<\/p>\n\n<h2>ARC, forwarding and mailing lists<\/h2>\n\n<p>For legitimate redirects, I check the <strong>ARC<\/strong>-chain (Authenticated Received Chain). Standing <em>ARC-Seal<\/em> and <em>ARC message signature<\/em> at <em>pass<\/em>, I tend to trust the originally documented SPF\/DKIM results, even if DMARC fails at the last hop. Mailing lists often change mails (subject prefixes, footers), which breaks DKIM. <em>List-Id<\/em>, <em>List-Unsubscribe<\/em> and a bulk<em>Precedence<\/em> then explain the deviations and prevent misjudgments.<\/p>\n\n<h2>Transport details: TLS, HELO\/EHLO and DNS<\/h2>\n\n<p>I read in <strong>Received<\/strong> the transportation details: <em>with ESMTPS<\/em> indicates TLS, often including cipher and protocol version. The <em>HELO\/EHLO<\/em>-name of the sending system should match the reverse DNS (<em>PTR<\/em>) and ideally match back to the same IP via Forward-Confirm (A\/AAAA). For me, a generic rDNS or a HELO as a mere IP are indicators of poorly configured systems. Large senders use consistent hostname schemes; deviations are quickly noticed.<\/p>\n\n<h2>Additional headers with added value<\/h2>\n\n<p>In addition to the standards <strong>X header<\/strong> specifically: <em>X-Spam status<\/em> and <em>X-Spam flag<\/em> show heuristics of upstream filters, <em>X-Originating-IP<\/em> reveals the real client IP for some systems. Hints like <em>X-PHP script<\/em> point to self-hosted form mailers. The following speak for serious mass mailing <em>Feedback ID<\/em>, <em>List-Id<\/em> and <em>List-Unsubscribe<\/em>. If all this is missing from an alleged \u201enewsletter\u201c e-mail, I evaluate it more strictly. <em>Message ID<\/em> I check the format and domain extension; atypical or empty domains are conspicuous.<\/p>\n\n<h2>MIME level: content type, attachments and encoding<\/h2>\n\n<p>I take a look at the <strong>MIME structure<\/strong> to: <em>multipart\/alternative<\/em> with a clean plain text part speaks for legitimate systems, pure HTML without text part is often mass mailing of lower quality. <em>Content type<\/em>, <em>boundary<\/em> and <em>charset<\/em> help me to differentiate between mailbox emails and manual messages. I recognize suspicious attachments by <em>Content disposition<\/em>, duplicate file extensions and unusual <em>Content transfer encodings<\/em>. TNEF\/\u201ewinmail.dat\u201c or incorrectly set MIME types often break DKIM - I explain this as a technical error rather than intentional.<\/p>\n\n<h2>International domains and characters<\/h2>\n\n<p>I check <strong>IDN\/Punycode<\/strong> Exactly: A from-domain can visually look like \u201eexample.com\u201c, but actually contain a similar-looking Unicode character. The punycode-encoded form then often appears in the header. I also pay attention to <em>SMTPUTF8<\/em> in received or capability notices. If the font encoding does not match the claimed language or brand, this is a further indication.<\/p>\n\n<h2>Understanding the time profile per hop<\/h2>\n\n<p>From each <strong>Received<\/strong>-line: The distance between timestamps shows me delays per hop. Large gaps with known greylisting hops can be explained, but abrupt time zone changes without a plausible reason cannot. If a <em>Date<\/em>-If the signal is in the future or far in the past, many filters evaluate it negatively - but I keep it if the other signals are consistent.<\/p>\n\n<h2>Read bounces and DSN precisely<\/h2>\n\n<p>For unclear returns I evaluate <strong>Delivery Status Notifications<\/strong> from. <em>Final Recipient<\/em>, <em>Action<\/em>, <em>Status<\/em> (e.g. 5.7.1 Policy) and <em>Diagnostic code<\/em> tell me whether authentication, reputation, size or content was blocked. Sometimes the actual reason is only in the <em>Diagnostic code<\/em> of the recipient MTA; I then rely less on generic status information.<\/p>\n\n<h2>Comparison with MTA logs<\/h2>\n\n<p>If I have access, I correct headers with <strong>Mail server logs<\/strong>. Many MTAs write a queue ID in <em>Received<\/em> (<em>id<\/em>=...). I find these again in Postfix, Exim or Exchange logs. This allows me to clearly document delivery times, TLS parameters, filter actions or redirections and separate header artifacts from real transport problems.<\/p>\n\n<h2>Special cases of legitimate senders<\/h2>\n\n<p>Brands often ship via <strong>Third-party platforms<\/strong>. I then expect subdomains, dedicated return paths and consistent DKIM signatures of the sending domain, while the visible from-domain is relaxed-aligned via DMARC. Shared IP ranges with other customers are normal as long as rDNS, HELO and signatures are clean. If any of this is missing, it may be due to IP warmup, new keys or routing changes - then I speak of an \u201einconsistent, but not malicious\u201c situation.<\/p>\n\n<h2>Short test checklist<\/h2>\n\n<ul>\n  <li>Set first trusted hop, ignore received above it<\/li>\n  <li>Match envelope (return path) against From\/Sender\/Reply-To<\/li>\n  <li>Evaluate SPF\/DKIM\/DMARC together with alignment, observe ARC for redirects<\/li>\n  <li>Check HELO, rDNS and IP consistency per hop<\/li>\n  <li>Classify X header, list information and message ID format<\/li>\n  <li>Check MIME structure, coding and attachments for anomalies<\/li>\n  <li>Check time stamp per hop and total latency for plausibility<\/li>\n  <li>Prioritize DSN fields and diagnostic code for bounces<\/li>\n  <li>Optionally correlate with MTA logs to resolve doubts<\/li>\n<\/ul>\n\n<h2>Header analysis for your own mail server<\/h2>\n\n<p>Do I operate my own <strong>Mail server<\/strong>, I use headers on a daily basis for quality assurance. I check whether outgoing emails have the expected signatures and whether recipient servers see them correctly. I quickly uncover errors in signature stability via authentication results. For consistent signatures, I pay attention to canonicalization rules and format details. I get practical background information on topics such as <a href=\"https:\/\/webhosting.de\/en\/dkim-canonicalization-signature-stability-mail-server-security\/\">DKIM-Canonicalization<\/a>, to eliminate deviations conclusively.<\/p>\n\n<h2>Practical example: suspicious invoice email<\/h2>\n\n<p>In one case, an invoice email looked like this <strong>genuine<\/strong> but the received chain stood out. The sender IP was in a network that did not match the brand. SPF checked positive, but the sending domain did not match the From. DKIM was completely missing, although the brand was otherwise signed. The header thus showed clear <strong>Phishing<\/strong>-suspicion despite perfect layout.<\/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\/06\/spam_analyse_5829.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Avoid common errors during evaluation<\/h2>\n\n<p>I never rely on just one <strong>Value<\/strong>, because individual fields can be misleading. Paying attention only to the visible sender address is often misleading. I also don't ignore time zones, as incorrect times hide suspicious routes. I evaluate missing DKIM signatures in the context of redirects. Only the overall picture provides a conclusive <strong>Decision<\/strong>, whether spam is present.<\/p>\n\n<h2>When the analysis is particularly worthwhile<\/h2>\n\n<p>I resort to header analysis when filters unexpectedly <strong>fail<\/strong> or block legitimate emails. Unclear bounces, sudden floods of spam or conspicuous campaigns benefit the most. Patterns across several messages show recurring servers, IP ranges or incorrect signatures. These indications significantly sharpen guidelines and server settings. Every clean evaluation reduces effort, saves money and strengthens the <strong>Delivery<\/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\/2026\/06\/mailserver-analyse-bild-4132.png\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Brief summary: What sticks<\/h2>\n\n<p>I recognize deceptions quickly when I <strong>Header<\/strong> completely, check the path backwards and evaluate authentication in the composite. Received lines, sender IP, return path and authentication results provide reliable clues. This is how I separate genuine customer emails from fraud and repair delivery routes without guesswork. The method is suitable for both beginners and professionals as it offers clear steps. Those who work in this way reduce spam, secure brand identity and increase the <strong>Reliability<\/strong> in mail traffic.<\/p>","protected":false},"excerpt":{"rendered":"<p>Mailserver Header Analysis helps with spam detection, phishing checks and delivery problems. How to correctly read headers, authentication and dispatch routes.<\/p>","protected":false},"author":1,"featured_media":19754,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[821],"tags":[],"class_list":["post-19761","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-spambekaempfung-web_hosting"],"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":"97","_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":"Mailserver Header","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":"19754","footnotes":null,"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/19761","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=19761"}],"version-history":[{"count":0,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/19761\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/19754"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=19761"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=19761"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=19761"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}