Primary route for US West transactional flows and Pacific-adjacent portfolios.
Private Relay Infrastructure
feikap
Private relay for critical email.
Reviewed SMTP access, sender authentication, regional routing and abuse-resistant transactional delivery operations.
Transactional traffic only
Sender review required
SPF / DKIM / DMARC expected
No open relay access
Request private relay access
No cold outreach. No purchased lists.
Routing Atlas
Ten regional positions. One reviewed-access policy.
Los AngelesLAX / US West
VirginiaIAD / US East
LondonLHR / UK
FrankfurtFRA / EU
DubaiDXB / MEA
SingaporeSIN / SEA
Hong KongHKG / APAC
TokyoNRT / Japan
SeoulICN / Korea
SydneySYD / Oceania
587
STARTTLS
465
SSL relay
Token
Bearer auth
Policy
Reviewed access
Private access
Credentials are issued only after sender and domain review.
Regional routing
Node assignment is based on use case, region and operational posture.
Authenticated senders
SPF, DKIM and DMARC alignment are expected before production.
Abuse resistant
Policy enforcement protects recipients and relay reputation.
Mesh
Regional relay positions.
feikap presents routing as a controlled infrastructure layer. Regional positions support
account, security, billing and operational mail without exposing anonymous open-relay capacity.
East Coast continuity route for US-oriented applications and failover posture.
UK relay position for regulated communication and regional delivery discipline.
European routing position for compliance-aware delivery and sender review.
Middle East bridge for regional expansion and private delivery continuity.
Southeast Asia relay position for low-latency regional routing.
Asia-Pacific gateway for portfolio routing and regional policy control.
Japan-facing route for account, billing and product-critical notification flows.
North Asia relay position for regional continuity and product messaging.
Oceania continuity route for southern Pacific transactional delivery.
Architecture
From sender to handoff.
The workflow is deliberately narrow: authenticated SMTP submission, policy review,
regional route selection and reputation monitoring for transactional delivery.
SMTP submission over STARTTLS or SSL from approved credentials.
Traffic type, sender identity and access boundaries are evaluated.
SPF, DKIM, DMARC and domain posture signals are expected.
Regional affinity and continuity rules determine relay position.
Transactional traffic is handed off through the assigned route.
Bounce, complaint and abuse signals protect the relay reputation.
Delivery Classes
Designed for expected mail.
feikap is for messages recipients expect to receive. Each delivery class is tied
to account state, product activity or service operation.
Class A
Authentication.
Verification codes, password resets, login alerts and account confirmation messages.
Class B
Account operations.
Billing notices, invoices, subscription updates and account lifecycle notifications.
Class C
Product events.
Order updates, workspace invitations, service events and workflow notifications.
Class D
Security notices.
Risk alerts, device-change messages and security-sensitive operational communication.
Sender Requirements
Trust starts at the domain.
Access is not based on volume alone. Sender posture, DNS alignment, traffic hygiene
and abuse response readiness determine whether a workload belongs on the relay layer.
SPF alignment
Sender domains should authorize the infrastructure used to submit mail and avoid conflicting sender sources.
v=spf1 include:...
DKIM signing
Messages should be signed with domain-aligned keys to establish sender identity and message integrity.
selector._domainkey
DMARC monitoring
DMARC policy helps detect unauthorized use, protect brand identity and improve trust signals over time.
_dmarc.yourdomain.com
Bounce discipline
Invalid recipients, repeated failures and complaint patterns should be handled before reputation is affected.
suppression required
Traffic boundaries
Transactional mail only. No cold outreach, purchased lists, deceptive routing or campaign blasting.
reviewed use only
Routing
Policy-led delivery.
More nodes should not mean less control. Routing is based on region, sender identity,
traffic class and risk signals rather than anonymous self-serve capacity.
Routing
Regional affinity.
Traffic can be assigned to a preferred routing region after domain and use-case review.
Reputation
Sender lanes.
Sender domains are separated by posture, message type and operational risk profile.
Continuity
Failover review.
Continuity routes can be reviewed for high-sensitivity transactional workloads.
Risk
Adaptive throttling.
Suspicious traffic patterns may trigger throttling, credential rotation or suspension.
Not For
Clear boundaries.
A private relay brand becomes more credible when it says what it will not carry.
feikap is not a growth-hacking or bulk campaign platform.
Unrequested sales sequences and scraped-contact campaigns are outside scope.
List buying, list renting and inherited recipient databases are not supported.
Political, lobbying or ideological campaign traffic is not accepted.
Gambling, adult content, phishing, malware, impersonation and deceptive financial schemes are prohibited.
Access Models
Reviewed before volume.
feikap can support different operational shapes without becoming public self-serve infrastructure.
Each path begins with a sender and traffic review.
For early-stage transactional workloads that need controlled SMTP access.
- Single-domain review
- Basic sender posture check
- Gradual traffic ramp
For operators managing multiple domains, brands or product environments.
- Multi-domain evaluation
- Reputation lane separation
- Regional routing review
For sensitive transactional flows where continuity and route planning matter.
- Preferred region planning
- Continuity posture review
- Abuse-response expectations
Status
Operational surface.
Public status is intentionally concise. Detailed routing health, continuity posture and
assigned nodes are confirmed during onboarding.
Position
Role
Status
Access
United States
US West / US East relay positions
Operational
Reviewed
Europe
UK and EU routing positions
Operational
Reviewed
Asia-Pacific
Hong Kong, Singapore, Tokyo and Seoul
Operational
Reviewed
Oceania
Sydney continuity position
Operational
Reviewed
Public status reporting is updated manually during infrastructure events. The status surface is not
a promise of anonymous node capacity; routing is assigned only after access review.
Docs
Technical protocol.
Integration is deliberately narrow. SMTP access requires approved credentials,
encrypted transport and sender authentication before production traffic.
Host
relay-la.feikap.com
Port
587 / STARTTLS
Port
465 / SSL
Auth
Bearer Token Required
Access
Selective Node Vetting
Protocol access is issued after sender review. Credentials are not self-serve. Customers should configure SPF, DKIM and DMARC before production sending.
// feikap SMTP logistics
Host: relay-la.feikap.com
Port: 587 STARTTLS
Port: 465 SSL
Auth: Bearer Token
// access note
Selective node vetting is mandatory before access.
// recommended sender posture
SPF: aligned
DKIM: aligned
DMARC: monitored
Traffic: transactional only
Policy
Integrity standards.
feikap is not an open relay for any traffic. Access depends on lawful use,
recipient trust, sender authentication and infrastructure hygiene.
Zero Tolerance
Illicit activity prohibited.
feikap does not support gambling, wagering, adult content, political campaigns, lobbying, ideological propaganda, phishing, malware distribution, fraud, impersonation or unsolicited abuse.
Enforcement
Immediate access termination.
Violations may result in suspension, throttling, credential rotation, node removal or complete termination where infrastructure, legal or reputation risk is detected.
Privacy
Minimal retention orientation.
Communication content is not intended for long-term storage. Processing is limited to delivery, diagnostics, abuse review, security control and legal requirements.
Security
Encrypted relay operations.
Delivery operations are structured around authenticated access, encrypted transport and disciplined node control.
Terms of Service
By accessing feikap infrastructure, SMTP relay endpoints, documentation, credentials or related services, you agree to the service terms, acceptable use policy, privacy policy and compliance rules.
feikap is intended for legitimate organizations, developers and operators with verified transactional delivery needs. Access may require identity, domain and sender review.
Customers are responsible for sender domains, DNS authentication, recipient consent, content, list hygiene, bounce handling, complaint handling and all activity through issued credentials.
Email delivery depends on recipient systems, sender reputation, domain configuration, network conditions and third-party filtering. Universal inbox placement cannot be guaranteed.
Privacy Policy
feikap may process sender addresses, recipient addresses, routing data, authentication records, timestamps, delivery states, bounce responses and security signals.
Message content may be processed transiently for delivery, troubleshooting, abuse review, compliance obligations or technical security functions.
feikap is oriented toward minimal retention. Operational metadata may be retained where needed for diagnostics, fraud prevention, abuse investigation or legal obligations.
Data may be disclosed to infrastructure providers, security vendors, legal authorities or abuse response parties when necessary for operations, compliance or harmful activity investigation.
Acceptable Use
Permitted use includes verification codes, password resets, billing notices, security alerts, account updates, service notices, order updates and legitimate transactional communication.
Prohibited use includes spam, phishing, malware, credential theft, fraud, impersonation, deceptive routing, harassment, unsolicited bulk messaging and bypass attempts.
Gambling, wagering, adult content, political campaigns, ideological propaganda, deceptive financial schemes, illegal pharmaceuticals and high-risk sectors may be disallowed or require review.
feikap may monitor metadata, traffic patterns, abuse reports, bounce rates, complaint rates and security signals to detect abuse and preserve infrastructure integrity.
FAQ
Operational clarity.
Short answers for teams evaluating whether feikap is the right layer for
transactional infrastructure and reviewed SMTP access.
Is feikap an open SMTP relay?
No. feikap is reviewed-access relay infrastructure. Credentials are issued only after sender, domain and use-case review.
Is feikap for marketing campaigns?
No. feikap is positioned for transactional, account-related and product-critical messages, not unsolicited bulk campaigns or cold outreach.
Which DNS records should be prepared?
Customers should prepare SPF, DKIM and DMARC alignment before production sending. Additional DNS or sender requirements may be confirmed during onboarding.
Can access be terminated?
Yes. Access may be suspended, throttled, rotated or terminated when traffic creates infrastructure, reputation, compliance or recipient-safety risk.
How are routing positions assigned?
Node assignment depends on use case, sending region, sender posture, traffic profile and operational review. The mesh is not exposed as anonymous self-serve capacity.
Abuse
Reputation is operational capital.
The abuse desk protects recipients, customers, infrastructure and the
sender reputation layer behind every relay position.
Report unsolicited or harmful traffic.
To report phishing, malware, impersonation, fraud, unsolicited traffic, policy violations or suspicious relay activity, send message headers, timestamps, sender address, recipient address and relevant evidence to the abuse desk.
Inquiry
Request private relay access.
For private relay access, onboarding, compliance review or portfolio-scale transactional delivery, contact feikap with your use case, sending domain, expected volume and preferred routing region.
Expected response time: less than 12 hours.
Access Brief
Request access
Sending domain
Include the domain or domains you expect to authenticate for relay access.
Traffic profile
Describe whether traffic is verification, account, billing, order or operational messaging.
Expected volume
Share approximate daily or monthly message volume and any planned ramp-up requirements.
Preferred routing region
US, Europe, Middle East, Southeast Asia, APAC, Japan, Korea, Oceania or undecided.
Direct contact: [email protected]. Include headers or technical context when reporting abuse.