Outlook Modify Signature Techniques For Professional Use

Published

outlook modify signature
Table of Contents

Email signatures serve as a digital business card, reflecting professionalism and brand identity in every communication. OutlookModifySignatureTechniquesForProfessionalUse explores how to leverage Outlook’s signature editor to create polished, functional, and compliant email closures. From foundational customization methods to advanced troubleshooting, this guide covers the technical and practical aspects of optimizing signatures across desktop, web, and enterprise environments.

Outlook’s signature system integrates text, visuals, and interactive elements, yet its capabilities vary between platforms and configurations. Understanding these nuances—such as HTML rendering inconsistencies, Exchange policy restrictions, and cross-client compatibility—ensures signatures remain both visually cohesive and operationally reliable. Whether adjusting fonts in the drag-and-drop editor or scripting batch updates via PowerShell, precision in implementation determines the effectiveness of this often-overlooked communication tool.

outlook modify signature

Core Components of an Outlook Email Signature and Placement Rules

Outlook email signatures serve as a digital business card, combining visual and textual elements to reinforce professional identity. The core components—text, images, hyperlinks, and logos—are structured hierarchically, with placement rules dictated by Outlook’s rendering engine and email client compatibility. Proper organization ensures consistency across platforms while adhering to email standards (e.g., RFC 2822 for plain text, MIME for HTML). Below are the foundational elements and their functional roles in signature design.

Text Elements and Hierarchy

Outlook signatures support structured text via HTML or plain text formats, with the following hierarchy governing display:

  • Primary Name/Title: Typically rendered in the largest font (e.g., 12pt–14pt) for visibility.
  • Secondary Details: Positioned below the primary line, often in smaller font (e.g., 10pt–11pt), including job role, department, or company tagline.
  • Contact Information: Aligned to the right or left, formatted as clickable links (e.g., phone, email) or static text.
  • Legal Disclaimers: Placed at the bottom, often in a smaller, less prominent font (e.g., 8pt–9pt) to comply with corporate or regulatory requirements.

    • Best Practice: Use semantic HTML tags (`

    `, `

    `, ``) for text styling to ensure consistency across email clients. Avoid excessive line breaks or nested tables, as these can trigger spam filters or break rendering in clients like Gmail or Apple Mail.

    Images, Logos, and Visual Assets

    Visual components must adhere to Outlook’s attachment limits (typically 10MB per email) and MIME compliance. Key considerations include:
  • File Formats: Supported formats are JPEG, PNG, and GIF (avoid SVG or animated GIFs, as these may not render in all clients).
  • Dimensions: Logos should not exceed 600px in width to prevent truncation in mobile views. Height should scale proportionally (e.g., 1:2 or 1:3 aspect ratio).
  • Alt Text: Required for accessibility and fallback rendering. Example:
    • ```html
    Acme Corporation Official Logo ```
  • Hosting: Embedded images (data URLs) are less reliable than web-hosted assets due to Outlook’s caching behavior. Use absolute URLs (e.g., `https://cdn.example.com/logo.png`) for consistency.

    • Warning: Outlook Web App (OWA) may strip embedded images if the email is marked as "external" or if security policies block image loading.

    Links in signatures must comply with email client restrictions and spam filters. Key rules:
  • Anchor Text: Use descriptive text (e.g., "Visit Our Website" instead of "Click Here") to improve click-through rates and accessibility.
  • URL Structure: Avoid shortened URLs (e.g., Bit.ly) or dynamic parameters (e.g., `?utm_source=email`), as these may trigger spam filters.
  • Tracking: Outlook does not support JavaScript or web beacons in signatures. For analytics, use UTM parameters in static links or redirect via a landing page.
  • Button Styles: CSS-styled buttons (e.g., `
    • ```html ```

    Note: Outlook for Mac and OWA may render links in blue regardless of inline CSS. Test signatures using tools like Litmus or Email on Acid.

    Placement Rules and Email Client Compatibility

    Signature placement is governed by Outlook’s default settings and email client policies:
  • Desktop Outlook (Windows/Mac):
  • Signatures appear below the email body by default, but can be configured to show above (via `File > Options > Mail > Signatures`).
  • Multiple signatures (e.g., work/personal) are stored in the `Signatures` folder within the Outlook data file (`.ost` or `.pst`).
  • Outlook Web App (OWA):
  • Signatures are appended automatically and cannot be placed above the body. Customization is limited to text/images via the OWA signature editor.
  • Mobile Clients (iOS/Android):
  • Signatures may truncate if the email body exceeds the screen width. Use responsive designs (e.g., media queries in HTML) to mitigate this.

    • Conflict Resolution: If a signature appears misplaced, check the account settings in Outlook (`File > Account Settings > Account Settings`) for conflicting profiles or corrupted template files.

    Methods to Modify Signatures in Outlook Desktop (Windows/Mac)

    Outlook Desktop for Windows and Mac provides multiple methods to create and modify email signatures, ranging from built-in editors to automated tools. Each approach varies in complexity, flexibility, and compatibility with organizational policies. Below, a structured comparison outlines the key methods, their implementation steps, advantages, and limitations. Additionally, dynamic field embedding, batch updates via scripting, and advanced CSS/HTML customization are addressed to ensure signatures align with professional standards and compliance requirements.

    Comparison of Manual vs. Automated Signature Editing Methods

    The choice between manual and automated methods depends on user expertise, organizational policies, and the need for scalability. Below is a comparative table summarizing the most common approaches:
    Method Steps Pros Cons
    Manual Editor (Outlook Built-in) 1. Open Outlook and navigate to File > Options > Mail > Signatures.
    2. Select an existing signature or create a new one.
    3. Use the toolbar to insert text, images, hyperlinks, and basic formatting (bold, italics, font size).
    4. Preview and set as default for new messages or replies/forwards.
    • No third-party dependencies or coding required.
    • Direct integration with Outlook’s interface.
    • Supports basic HTML elements (tables, lists) via the editor.
    • Limited to Outlook’s native formatting options (e.g., no custom CSS).
    • Manual updates required for multiple profiles or users.
    • No support for dynamic fields beyond Outlook’s placeholders (e.g., no real-time data pulls).
    Drag-and-Drop Editor (HTML/Code Injection) 1. Compose the signature in an external HTML editor (e.g., Notepad++, VS Code) or use Outlook’s "Edit HTML" mode.
    2. Insert custom HTML/CSS for advanced layouts (e.g., responsive grids, custom fonts).
    3. Paste the code into Outlook’s signature editor via the "HTML" tab.
    4. Test rendering across devices and Outlook versions.
    • Full control over design (e.g., CSS3 animations, custom typography).
    • Supports responsive layouts for mobile/desktop.
    • Faster updates when signatures are centrally managed via code.
    • Requires HTML/CSS knowledge; risk of breaking signatures if syntax errors occur.
    • May not render consistently across Outlook versions (e.g., older clients strip unsupported tags).
    • No built-in version control for collaborative edits.
    Third-Party Tools (e.g., HubSpot, WiseStamp, Exclaimer) 1. Install the tool’s add-in or plugin for Outlook.
    2. Design signatures using the vendor’s cloud-based editor (often with drag-and-drop interfaces).
    3. Sync signatures to Outlook via API or manual export/import.
    4. Schedule automatic updates or enforce compliance templates.
    • Advanced features like dynamic content (e.g., weather, stock tickers), analytics, and A/B testing.
    • Centralized management for enterprise deployments.
    • Often includes compliance templates (e.g., GDPR disclaimers).
    • Subscription costs and potential vendor lock-in.
    • Dependency on third-party servers (privacy concerns for sensitive data).
    • Some tools may not support all Outlook features (e.g., Mac-specific quirks).
    PowerShell Scripting (Batch Updates) 1. Use Outlook’s COM object model to automate signature creation/modification.
    2. Write a script to loop through Outlook profiles or users (e.g., via Exchange Server).
    3. Deploy scripts via scheduled tasks or Group Policy for enterprise-wide updates.
    4. Log errors for troubleshooting.
    • Ideal for large-scale deployments (e.g., 1,000+ users).
    • Supports conditional logic (e.g., role-based signatures).
    • Can integrate with Active Directory for dynamic user data.
    • Requires PowerShell expertise and administrative rights.
    • Script failures may silently corrupt signatures.
    • Limited to Outlook Desktop; web versions (Outlook on the Web) require EWS or Graph API.
    Exchange Server Policies (Disclaimer Rules) 1. Configure Exchange Admin Center or PowerShell to apply transport rules.
    2. Define disclaimers with static or dynamic content (e.g., legal notices).
    3. Set scope (e.g., all external emails, specific domains).
    4. Test compliance with sample emails.
    • Enforces signatures universally across all clients (Outlook, mobile, web).
    • Centralized management reduces user errors.
    • Supports legal/compliance requirements (e.g., HIPAA, SOX).
    • Limited customization compared to manual methods.
    • May conflict with user-created signatures.
    • Requires Exchange Server licensing and permissions.

    Embedding Dynamic Fields in Outlook Signatures

    Outlook supports placeholders to insert dynamic data into signatures, such as the sender’s name, company, or date. These fields update automatically based on the user’s profile or system settings. Below are the most commonly used placeholders and their syntax:
    Outlook’s dynamic field syntax for signatures:
    • User Information:
      • %FirstName% – Displays the user’s first name (e.g., "John").
      • %LastName% – Displays the user’s last name (e.g., "Doe").
      • %DisplayName% – Combines first and last name (e.g., "John Doe").
      • %Email% – Inserts the sender’s email address.
      • %Title% – Pulls the user’s job title from Outlook’s profile.
    • Company and Contact Details:
      • %Company% – Displays the company name from the profile.
      • %Phone% – Inserts the primary phone number.
      • %Mobile% – Inserts the mobile number (if available).
      • %Address% – Shows the full address (requires manual entry in Outlook).
    • Date and Time:
      • %Date% – Inserts the current date (format: MM/DD/YYYY).
      • %Time% – Inserts the current time (format: HH:MM AM/PM).
      • %FullDateTime% – Combines date and time.
    • Custom Fields:
      • Use Outlook’s User Properties (File > Options > Mail > User Information) to add custom fields (e.g., %Department%, %Location%

        outlook modify signature - Ilustrasi 2

        Advanced Signature Customization Techniques in Outlook

        Outlook’s signature editor extends beyond basic formatting to include dynamic, interactive, and platform-specific customizations. These techniques enhance professionalism, improve engagement, and ensure cross-platform consistency. Below are lesser-known features, reusable components, and cross-platform comparisons to optimize email signatures for diverse use cases.

        Lesser-Known Outlook Signature Features and Implementation

        Outlook supports advanced signature elements that adapt to context, improve accessibility, and integrate modern digital tools. These features are often overlooked but provide significant functionality for businesses and individuals.

        Conditional Signatures
        Conditional signatures allow automatic switching between signatures based on predefined rules (e.g., sender email domain, recipient list, or time of day). This is useful for separating work and personal emails or applying seasonal disclaimers.

      • Implementation Steps:
        • 1. Navigate to File > Options > Mail > Signatures.
        2. Click Signatures Settings > New to create a secondary signature.
        3. Under When replying or forwarding, select Show this signature and define conditions (e.g., "If my email address is @company.com").
        4. Assign the signature to specific accounts or rules via Rules > Manage Rules & Alerts.

        Social Media Icons with Hyperlinks
        Embedding clickable social media icons (LinkedIn, Twitter, etc.) in signatures increases professional networking visibility.

      • Implementation Steps:
        • 1. Insert an image (e.g., SVG or PNG) via the Insert > Pictures tab.
        2. Right-click the image > Link > Insert Hyperlink and enter the URL (e.g., `https://linkedin.com/in/username`).
        3. For consistency, use the same icon style and color scheme across all signatures.

        Clickable QR Codes for Contact Information
        QR codes streamline contact sharing by encoding email, phone, or LinkedIn profiles into a scannable format.

      • Implementation Steps:
        • 1. Generate a QR code using a tool like QR Code Generator (encode text as `mailto:email@example.com` or `tel:+1234567890`).
        2. Insert the QR code as an image in the signature.
        3. Add a tooltip (via HTML alt text) explaining its purpose (e.g., "Scan to save contact").

        Dynamic Date/Time Stamps
        Auto-updating timestamps (e.g., "Sent on [Date]") add credibility and reduce manual updates.

      • Implementation Steps:
        • 1. Insert a Quick Part (see next section) with the field code `{MERGEFIELD Date}`.
        2. Alternatively, use a Word document embedded in the signature with a `DATE` field (requires Outlook 2016+).

        Accessibility Features
        Ensure signatures comply with WCAG standards by adding:

      • Alt text for images: Right-click image > Edit Alt Text.
      • Logical tab order: Use Insert > Object > ActiveX Control (if supported) to define focus sequences.
      • High-contrast colors: Test with tools like WebAIM Contrast Checker.
        • The Quick Parts gallery stores frequently used signature elements (e.g., legal disclaimers, contact blocks) for rapid insertion and consistency. This reduces redundancy and ensures compliance across emails.

        Creating and Storing Quick Parts

      • Legal Disclaimers:
        • 1. Type the disclaimer in a new email draft.
        2. Select the text > Insert > Quick Parts > Save Selection to Quick Parts Gallery.
        3. Name it (e.g., "Confidentiality Notice") and assign a keyboard shortcut (e.g., `Ctrl+Alt+D`).
      • Contact Blocks:
        • 1. Format a contact block (name, title, phone, email) in a draft.
        2. Save as a Quick Part with a descriptive name (e.g., "Executive Contact").
        3. Insert via Insert > Quick Parts > AutoText or the shortcut.

        Editing and Updating Quick Parts

      • To modify a saved Quick Part:
        • 1. Open the Quick Parts gallery.
        2. Right-click the item > Edit or Delete.
      • For dynamic updates (e.g., changing a phone number), use fields like `{MERGEFIELD Phone}` and update via Mail Merge (advanced).

        • Limitations and Workarounds

      • HTML/CSS Limitations: Quick Parts do not support complex styling. For advanced formatting, use HTML signatures (see next section).
      • Cross-Account Sync: Quick Parts are profile-specific. To share across accounts, export the Normal.dotm template (located in `%AppData%\Microsoft\Templates`) and import it into other Outlook profiles.

        • Overriding Default Signature Settings for Multiple Email Accounts

        Outlook allows distinct signatures for each email account without merging profiles, ensuring personal and work emails maintain separate branding. This is critical for users managing multiple identities (e.g., work, freelance, personal).

        Assigning Signatures to Specific Accounts
        1. Open File > Options > Mail > Signatures.
        2. Select an account from the E-mail account dropdown.
        3. Choose a signature for New messages and Replies/Forwards.
        4. Repeat for each account (Outlook Desktop supports up to 10 accounts per profile).

        Conditional Signatures for Mixed Accounts
        To auto-select signatures based on the sender’s email:
        1. Create separate signatures (e.g., "Work Signature" and "Personal Signature").
        2. Use Rules to apply them dynamically:

      • File > Manage Rules & Alerts > New Rule.
      • Select Apply this rule after sending > Sent to people or distribution list.
      • Define conditions (e.g., "where my address is @workdomain.com").
      • Set the action to Insert signature "Work Signature".

        • Avoiding Profile Merging

      • Windows: Signatures are stored in the Outlook Data File (.ost/.pst). To prevent merging:
      • Use separate profiles (Control Panel > Mail > Show Profiles).
      • Export/import signatures via File > Open & Export > Import/Export.
      • Mac: Signatures are tied to the Outlook preferences file (`~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook Preferences`). Backup and restore this file to transfer signatures without merging accounts.

        • Troubleshooting Account-Specific Issues

      • Missing Signatures: Ensure the account is added to Outlook (Account Settings > Account Settings).
      • Formatting Errors: Test signatures in a new draft before sending. Corrupted templates may require re-creation.

        • Adding Interactive Elements to Signatures

        Outlook’s Insert tab and third-party add-ins enable signatures with buttons, forms, and embedded content, though functionality varies by version. Below are methods for desktop (Windows/Mac) and cloud-based solutions.

        Native Outlook Interactive Elements
        1. Buttons (Hyperlinks):

      • Insert a shape (Insert > Shapes) or text box with a call-to-action (e.g., "Schedule a Meeting").
      • Right-click > Hyperlink > Enter URL (e.g., `https://calendly.com/username`).
      • Style with borders/colors via Shape Format.

        • 2. Forms and Surveys:

      • Use Microsoft Forms to create a survey, then embed it via a hyperlink:
      • Insert a text box with text like "Take our survey".
      • Link to the Forms URL (e.g., `https://forms.office.com/r/...`).

        • 3. Embedded Videos:

      • Insert a YouTube video via hyperlink or HTML (for Outlook 2016+):

        • - Paste into the signature HTML editor (Insert > HTML).

        Third-Party Add-Ins for Advanced Functionality

      • HubSpot Sales Email Templates: Integrates with Outlook to add trackable CTAs and CRM data.
      • Steps: Install via Home > Get Add-ins > HubSpot.
      • Supports dynamic fields (e.g., contact name from CRM).
      • Boomerang for Outlook: Adds "Read Receipts" and "Follow-Up" buttons.
      • Steps: Install via Add-ins > Get Add-ins > Boomerang.
      • DocuSign: Embeds e-signature requests directly in emails.
      • Steps: Insert via Home > New Email > DocuSign > Sign Request.

        • Limitations and Cross-Platform Notes

      • Mac Restrictions: Interactive elements (e.g., buttons) may not render consistently. Test in Outlook for Mac (2016+) or use webmail.

        • Troubleshooting Signature Issues in Outlook

        Email signatures in Outlook are critical for maintaining professionalism, but technical disruptions—such as corrupted files, formatting errors, or compatibility issues—can disrupt their functionality. Signature malfunctions often stem from XML/HTML structure flaws, conflicting add-ins, or profile corruption, which may manifest as missing images, broken hyperlinks, or misaligned text. Proactive diagnostics, automated validation scripts, and systematic reset procedures are essential to restore signatures without compromising email data integrity. This section provides structured troubleshooting methodologies, including diagnostic checklists, script-based repairs, and migration protocols to ensure seamless signature management across Outlook versions.

        Checklist of Common Signature Errors and Diagnostic Commands

        Signature failures in Outlook typically arise from structural or environmental issues. Below is a categorized checklist of frequent errors, accompanied by diagnostic commands to identify root causes. Use these steps to systematically isolate problems before applying fixes.
        Key Diagnostic Commands for Outlook (Windows):
      • Check for XML/HTML syntax errors:
        • `Outlook.exe /safe` (opens Outlook in Safe Mode, bypassing add-ins)
        `Ctrl+Shift+Esc` → Task Manager → End Task for Outlook processes → Restart Outlook.
      • Validate signature file integrity:
        • Open the signature file (`.htm` or `.xml`) in a text editor and search for:
      • Unclosed tags (``, `` without ``, ``).
      • Broken paths (e.g., `href="C:\invalid\path\image.jpg"`).
      • Unsupported CSS or JavaScript.
      • Test link functionality:
        • Copy the signature HTML into a browser to verify hyperlink accessibility.
        1. Missing or Broken Images
          • Symptoms: Placeholder icons, red "X" markers, or blank spaces where images should appear.
          • Diagnostic Steps:
            • Verify image file paths in the signature HTML/XML are absolute (e.g., `http://domain.com/images/logo.png`) or relative to the Outlook data file location.
            • Check file permissions for the image directory (e.g., `C:\Users\Username\AppData\Roaming\Microsoft\Signatures`).
            • Run Outlook in Safe Mode to rule out add-in interference.
          • Common Fixes:
            • Re-embed images using Outlook’s "Insert Picture" tool (File → Options → Mail → Signatures → Edit Signature).
            • Replace relative paths with absolute URLs or UNC paths (e.g., `\\server\share\images\logo.png`).
        2. Formatting Glitches (Text Alignment, Font Issues, Spacing)
          • Symptoms: Misaligned text, missing fonts, or collapsed spacing in sent emails.
          • Diagnostic Steps:
            • Compare the signature’s rendered appearance in Outlook’s "Preview" pane with the sent email (check for discrepancies in font stacks or CSS overrides).
            • Test with a minimal signature (e.g., plain text + one image) to isolate formatting conflicts.
            • Use Outlook’s "Inspect Message" tool (right-click email → Message Options → Inspect) to check for stripped formatting.
          • Common Fixes:
            • Replace custom fonts with web-safe alternatives (e.g., Arial, Calibri) or embed fonts using `@font-face` in the HTML.
            • Use inline CSS instead of external stylesheets to avoid dependency issues.
            • Reset signature formatting via:
              Registry Edit (Advanced):
              Navigate to `HKEY_CURRENT_USER\Software\Microsoft\Office\\Outlook\Options\Mail` and delete the `Signature` subkey. Restart Outlook to regenerate defaults.
        3. Broken Hyperlinks or Redirect Loops
          • Symptoms: Links displaying as plain text, 404 errors, or infinite redirects.
          • Diagnostic Steps:
            • Validate URLs in the signature HTML using tools like W3C Link Checker.
            • Check for relative paths (e.g., `href="../contact"` vs. `href="https://domain.com/contact"`).
            • Test links in a browser after copying the signature HTML to rule out Outlook-specific issues.
          • Common Fixes:
            • Replace relative URLs with absolute paths or use Outlook’s "Insert Hyperlink" tool to ensure proper encoding.
            • Disable "Track Changes" in signature files if they were edited in Word (File → Info → Protect Document → Track Changes → Off).
        4. Signature Not Appearing in Sent Emails
          • Symptoms: Signature absent in outgoing emails despite being set in Outlook.
          • Diagnostic Steps:
            • Confirm the signature is assigned to the correct account (File → Account Settings → Select account → Change → More Settings → Signature tab).
            • Check Outlook’s "Rules" (File → Manage Rules & Alerts) for policies overriding signatures.
            • Verify the signature file extension is `.htm` or `.html` (not `.txt` or `.docx`).
          • Common Fixes:
            • Recreate the signature file and reassign it via the Signatures dialog.
            • Reset Outlook’s mail profile:
              Steps:
              1. Close Outlook.
              2. Press `Win + R`, type `control panel`, and navigate to Mail (Microsoft Outlook).
              3. Select Show Profiles → Add → Create a new profile with the same account.
              4. Test the signature in the new profile.

        Automated Script for Signature File Corruption Validation

        Signature files stored as HTML or XML may degrade over time due to manual edits, add-in interference, or Outlook updates. Below is a PowerShell script to validate and repair structural integrity by checking for common corruption patterns (e.g., unclosed tags, invalid attributes, or broken references). Save the script as `Validate-OutlookSignature.ps1` and run it in PowerShell (admin rights required).
        Script Logic:
        1. Parses the signature file for XML/HTML compliance.
        2. Flags malformed tags, deprecated attributes, or missing DOCTYPE declarations.
        3. Generates a corrected version with warnings for manual review.

        <#
        .SYNOPSIS
        Validates and repairs Outlook signature files for XML/HTML corruption.
        .DESCRIPTION
        Checks for common issues: unclosed tags, invalid attributes, broken links, and deprecated elements.
        Outputs a corrected file with warnings.
        .NOTES
        Requires PowerShell 5.1+ and .NET Framework 4.5+.
        Tested on Outlook 2016/365 signature files (.htm, .html, .xml).
        #>

        param (
        [Parameter(Mandatory=$true)]
        [string]$SignaturePath,

        [string]$OutputPath = "$env:TEMP\FixedSignature_$(Get-Date -Format 'yyyyMMdd').html"
        )

        # Load required assemblies
        Add-Type -AssemblyName System.Xml
        Add-Type -AssemblyName System.Xml.Linq

        function Test-SignatureIntegrity {
        param (
        [string]$FilePath
        )

        $errors = @()
        $dom = New-Object System.Xml.XmlDocument
        $html = [System.IO.File]::ReadAllText($FilePath)

        try {

        Attempt to load as XML (strict mode)

        $dom.LoadXml($html) | Out-Null
        $isValidXml = $true
        }
        catch {
        $isValidXml = $false
        $errors += "XML Parsing Error: $($_.Exception.Message)"
        }

        # Check for common HTML issues
        if ($html -match ']src\s=\s*["\']([^"\']+)["\']') {
        $imagePaths = $matches[1] -split '[;"\']'
        foreach ($path in $imagePaths) {
        if (-not (Test-Path $path -Path

        Mastering Outlook signature customization transforms a routine email footer into a strategic asset, reinforcing brand consistency and operational efficiency. By combining manual adjustments with automated workflows, users can maintain professional standards while adapting to evolving technical requirements. From resolving corrupted templates to integrating dynamic fields, the techniques outlined here empower organizations to standardize signatures across teams and platforms. Ultimately, a well-optimized signature enhances credibility, streamlines compliance, and aligns digital communication with corporate identity.

        Leave a Comment

        Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of www.linuxunplugged.com.