Premium Services LTD

Overview

premium-services.net is the operational domain used by Premium Services LTD for outbound email infrastructure. Mail servers on this network transmit messages on behalf of authenticated business customers under the terms of our Acceptable Use Policy.

If you received a message from a host whose reverse DNS resolves to *.outbound.premium-services.net, or if this domain appears in the Received: headers of an email, the message was relayed through our infrastructure on behalf of a customer. Premium Services LTD does not author the content of relayed messages and does not operate recipient mailing lists.

Network Information

Reporting Abuse

Reports regarding messages that appear to violate our Acceptable Use Policy — including unsolicited bulk email, phishing, malware distribution, or harassment — should be directed to our abuse desk.

To enable investigation, reports must include:

• The complete original email headers of the reported message
• The date and time the message was received, including timezone
• The sending IP address as recorded in the Received: chain
• A concise description of the policy violation being reported

Postmaster Contact

Mailbox operators, deliverability teams, and network administrators with technical or operational questions may contact our postmaster directly.

Typical matters handled by postmaster include delivery diagnostics, authentication configuration inquiries, rate-limit negotiations, feedback loop coordination, and blocklist removal requests originating from mailbox providers.

Unsubscribe Requests

Premium Services LTD operates shared sending infrastructure on behalf of multiple independent customers. We do not maintain subscription databases and cannot directly remove recipients from a specific sender's distribution list.

To stop receiving messages from a particular sender:

• Use the one-click unsubscribe control shown by modern mail clients (Gmail, Outlook, Apple Mail) adjacent to the sender name — this invokes the RFC 8058 List-Unsubscribe-Post mechanism implemented across our platform
• Use the unsubscribe link provided in the message footer
• Contact the sender directly via the From: address

Failure by a sender to honor valid unsubscribe requests within two business days constitutes a policy violation and should be reported to our abuse desk.

Acceptable Use Policy

Customers transmitting mail through this infrastructure are contractually bound to comply with applicable anti-spam and data protection legislation, including CAN-SPAM (United States), GDPR and the ePrivacy Directive (European Union), UWG §7 (Germany), and equivalent regulations in recipient jurisdictions.

The following activities are expressly prohibited and result in immediate suspension:

• Transmission of unsolicited bulk email to recipients who have not provided verifiable opt-in consent
• Purchase, rental, scraping, or other acquisition of third-party recipient lists
• Falsification of sender identity, message headers, or routing information
• Distribution of phishing content, malware, or any content designed to deceive or defraud recipients
• Failure to honor unsubscribe requests within the period required by applicable law
• Circumvention of rate limits, authentication requirements, or mailbox provider restrictions

Authentication Standards

All mail transmitted through our infrastructure is authenticated in accordance with current industry standards:

• SPF (Sender Policy Framework) — RFC 7208
• DKIM (DomainKeys Identified Mail), 2048-bit RSA signatures — RFC 6376
• DMARC (Domain-based Message Authentication, Reporting and Conformance) with identifier alignment — RFC 7489
• RFC 8058 one-click unsubscribe for applicable message categories
• Opportunistic TLS 1.2+ on all outbound SMTP connections, with MTA-STS support where published by recipients
• Forward-Confirmed Reverse DNS on every sending IP address within our allocation

Customer sending domains publish their own SPF, DKIM, and DMARC records. Mailbox providers are encouraged to verify message authenticity using these mechanisms.

Security Disclosure

Security researchers may report vulnerabilities affecting our infrastructure in accordance with our security.txt policy (RFC 9116). Coordinated disclosure is appreciated.