Suped

How to set up DMARC/DKIM/SPF for Gigabyte Telecom

Published 21 Nov 2026
Updated 21 Nov 2026
10 min read
Summarize with
SPF, DKIM, and DMARC setup for Gigabyte Telecom email.
To authenticate Gigabyte Telecom email, authorize its confirmed outbound servers in your return-path domain's SPF record, enable DKIM signing for your domain, and publish a DMARC TXT record at _dmarc. DMARC passes when SPF or DKIM passes with a domain that matches your visible From domain under your alignment settings.
I start by requesting the account-specific DNS values from Gigabyte Telecom. I couldn't verify a public authentication setup guide, SPF include, or DKIM selector for its customer email service. The steps below use support-confirmed values and clearly marked examples.

Add your domain

Use a domain you control, such as example.com. If your mailbox uses a domain owned by Gigabyte Telecom, its administrators control that domain's authentication records; ask them to make the changes.
For a custom domain, request provisioning through Gigabyte Telecom. Its public website lists telephone support at 0800 062 2200. Confirm that your plan includes custom-domain email before changing DNS.
  1. Request provisioning: Give support your sending domain and mailbox addresses. Ask them to confirm that the domain is active for outbound email.
  2. Confirm DNS access: Identify the authoritative DNS provider. Save the existing SPF, DKIM, DMARC, and MX values before editing anything.
  3. Verify ownership: If support supplies a DNS verification token, publish its exact name, type, and value. Ask support to verify it and confirm activation; there is no verified universal Gigabyte Telecom token.
  4. Collect settings: Request the SMTP hostname and TLS settings, outbound IPv4/IPv6 addresses or SPF include, custom return-path configuration, and DKIM selector with its complete public DNS value.
The public support contact section is the starting point for these requests. It does not document a customer-facing email authentication control panel.
Illustrative reconstruction of Gigabyte Telecom's public support contacts.
Illustrative reconstruction of Gigabyte Telecom's public support contacts.
Ask for written confirmation of the DNS values and signing status. A working mailbox login alone does not establish that custom-domain DKIM is enabled.
I keep the current MX records unless Gigabyte Telecom explicitly requests a mail-hosting change. SPF, DKIM, and DMARC setup does not inherently require an MX change.

Set up SPF

Gigabyte Telecom supports return-path alignment. Ask support to configure the SMTP MAIL FROM domain as your sending domain or a suitable subdomain, then confirm the result in a delivered message's Return-Path header.
SPF is checked on that MAIL FROM domain, which is not necessarily your visible From domain. I publish only the outbound addresses or include mechanism confirmed for the account.
  1. Find the record: Look up TXT records on the confirmed MAIL FROM domain. Identify the single record beginning v=spf1.
  2. Authorize sending: Merge Gigabyte Telecom's confirmed mechanisms into that record before its final all mechanism. Preserve the other authorized senders; do not add a second SPF record.
  3. Check delegation: If support requires a CNAME for a return-path subdomain, follow that delegation instead of adding TXT data at the same name.
  4. Check limits: Keep SPF evaluation within 10 DNS-querying terms, including nested includes. Explicit ip4 and ip6 mechanisms do not consume that budget.
Example only: replace the address
192.0.2.25 is a documentation address, not a Gigabyte Telecom sending IP. This example assumes example.com is the MAIL FROM domain and has no other senders.
Illustrative SPF recordtext
Name: example.com Type: TXT Value: v=spf1 ip4:192.0.2.25 ~all
Do not copy Gigabyte Telecom's own corporate SPF record or invent include:gigabytetelecom.com.br. Its corporate mail configuration does not establish authorization for your account.
Enter the actual MAIL FROM domain in the SPF checker below. If it is a subdomain, checking only the parent domain will miss the relevant record.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
Confirm that one SPF record is returned and that its mechanisms cover the IP used by a fresh test message. DNS validation alone cannot prove which outbound server Gigabyte Telecom will use.
If a particular sending route retains a provider-owned return path, an SPF alignment failure is expected. Adding SPF to your visible From domain does not fix that route. DMARC still passes when DKIM passes with a matching signing domain; verify that result before enforcing DMARC.

Set up DKIM

Ask Gigabyte Telecom to enable outbound DKIM signing for your custom domain and supply the selector with its exact TXT value or CNAME target. Publishing a public key alone does not switch signing on.
I use the selector supplied for the account. A guessed selector such as default or selector1 is not a verified Gigabyte Telecom setting.
  1. Publish the key: Create the supplied DNS record at the exact selector._domainkey hostname. For TXT, copy the complete public key; for CNAME, copy the complete target.
  2. Preserve the key: Keep the public key unchanged. DNS providers that split long TXT values must preserve one logical record. Never publish the private key.
  3. Confirm signing: Ask support to confirm that outbound messages use your domain in the DKIM d= tag. Keep old selectors available during a key rotation until queued messages have cleared.
  4. Test the result: Send a fresh message through the configured SMTP service. Confirm dkim=pass and check that the signing domain satisfies your DMARC alignment setting.
Look up the selector found in a real messagebash
DKIM_DOMAIN=example.com DKIM_SELECTOR=selector-from-message dig +short CNAME "$DKIM_SELECTOR._domainkey.$DKIM_DOMAIN" dig +short TXT "$DKIM_SELECTOR._domainkey.$DKIM_DOMAIN"
Replace both shell values with the message's DKIM d= and s= values. Under relaxed alignment, a signing subdomain can share the organizational domain with the visible From domain. Strict alignment requires an exact domain match.
If DNS resolves but DKIM fails, send support the full message headers and the selector lookup. Ask them to check the active private key and whether a relay changed the signed message after signing.

Set up DMARC

For a domain without an enforced policy, I start with p=none and a working aggregate-report destination. If you already use p=quarantine or p=reject, keep that policy and fix the Gigabyte Telecom sending configuration.
Use the DMARC record generator to create the TXT value. DMARC is published on your visible From domain; it does not have to be enabled in the SMTP client.
  1. Inspect the policy: Check the existing _dmarc TXT record and preserve its reporting destinations and intentional settings.
  2. Set reporting: Replace dmarc@example.com in the example with a mailbox or reporting destination that you control and that processes aggregate XML reports.
  3. Publish one record: Create or update the TXT record at _dmarc on your sending domain. Enter the relative host or full hostname according to your DNS provider's format.
  4. Verify authorization: For an external rua destination, confirm that the destination operator has published the required external-reporting authorization.
Starting DMARC record for example.comtext
Name: _dmarc.example.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com
The example requests monitoring, without requesting quarantine or rejection for DMARC failures. The example reporting address must be replaced before publication.
Check the live policy with the DMARC checker. Confirm the hostname, a single valid policy, and the intended reporting address.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
A valid record proves that receivers can find a policy. It does not prove that Gigabyte Telecom messages pass DMARC or that every other legitimate sender is ready for enforcement.
Send real traffic and inspect aggregate reports after publication. Participating receivers send reports on their own schedules, commonly daily; a new setup often needs 24-48 hours before initial reports arrive.

Verify and troubleshoot

I test the actual sending route after every DNS or signing change. A webmail message and a website notification can use different servers, so test each route that sends with your domain.
The email tester is the quickest check of a delivered message. It supplies a test address and diagnoses the authentication results, sending IP, and related delivery configuration.
  1. Send directly: Copy the widget's current test address and send a non-sensitive message through Gigabyte Telecom. Keep the test page open; do not forward an existing message.
  2. Read authentication: Check SPF on the MAIL FROM domain, DKIM on the d= domain, and the final DMARC result for the visible From domain.
  3. Inspect the route: Record the outbound IP, Return-Path, DKIM selector, and receiver-generated Authentication-Results. Give these details to support when a result fails.
  4. Repeat coverage: Test each application and sending route, including IPv6 where used. A single successful message does not cover the entire outbound pool.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
If the test message never arrives, check the SMTP response, delivery queue, and bounce first. The tester needs a delivered message to inspect its authentication.
SPF pass and DKIM pass are authentication results. DMARC also checks the authenticated domain against the visible From domain, so two passing results on unrelated provider domains still fail DMARC.

Result

Check

Action

SPF fail
Outbound IP
Update SPF
SPF mismatch
MAIL FROM
Fix return path
DKIM missing
Signing status
Enable signing
DKIM fail
Selector and key
Ask support
DMARC fail
Domain match
Fix alignment
Use message results to choose the next repair.
For DNS changes, query the authoritative nameserver and allow existing cached records to expire according to their TTL. A change in a non-authoritative DNS zone has no effect on public lookups.
For delivery failures after authentication passes, ask Gigabyte Telecom to check PTR/rDNS and the outbound IP's blocklist (blacklist) status. The operator of the sending IP controls reverse DNS. Authentication success does not guarantee inbox placement.

Get alerted when it breaks

Suped is our DMARC platform for ongoing monitoring after the Gigabyte Telecom sending setup works. Its DMARC monitoring turns incoming aggregate reports into source-level authentication results and alerts.
I track legitimate sources separately so an authentication failure on customer mail is easy to distinguish from unauthorized use of the domain. Suped's issue diagnostics provide the affected source and steps to fix.
  1. Verify sources: Review the source table and mark only confirmed business senders as verified. Use actual message evidence and provider confirmation when identifying Gigabyte Telecom traffic.
  2. Enable issues: In Notifications, enable Issues detected and route alerts to the person responsible for DNS and email.
  3. Review new senders: Enable Sending sources need verification and DMARC summary emails. Investigate new IPs before authorizing them.
  4. Diagnose changes: Use record details to inspect SPF, DKIM, and rDNS results. Compare DNS history when failures follow a record edit.
Report timing affects alert timing
Aggregate DMARC monitoring depends on receiver reports arriving. Alerts based on those reports are not instant notifications for each failed message. Use Gigabyte Telecom's SMTP logs for immediate delivery errors.

Secure your domain with p=reject

Move to p=reject after every legitimate sending route has a reliable passing authentication path with the required domain match. I review the failures by source; a high overall pass rate can hide a broken low-volume application.
Suped's source verification and authentication diagnostics support this review. Hosted DMARC lets your team manage policy stages in the dashboard once configured, while reports show the effect of each change.
  1. Cover a full cycle: Observe normal operations and infrequent mail such as monthly invoices. Fix legitimate failures before tightening the policy.
  2. Test forwarding: Check important forwarded routes and mailing lists. Forwarding often breaks SPF; DKIM can preserve DMARC when the signed content remains intact.
  3. Stage enforcement: Move to p=quarantine, review reports and delivery failures, then use p=reject when legitimate traffic is ready. Keep an existing stronger policy in place.
  4. Check subdomains: Review explicit subdomain policies and inherited handling. Keep reporting active and record the prior policy for a controlled rollback if legitimate delivery breaks.
p=none
Collect reports and identify sending failures. This policy does not request DMARC-based quarantine or rejection.
p=reject
Request rejection of messages that fail DMARC. Receivers retain their local handling decisions; legitimate senders need a passing, matching authentication path.
Keep the established reporting destination when changing policy. This example changes only the policy for a domain that has completed the review.
DMARC protects the use of your domain in the visible From address. It does not prevent impersonation through a different lookalike domain or a misleading display name.
Example final policy after validationtext
Name: _dmarc.example.com Type: TXT Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Replace the example address with your existing reporting destination, then verify the published record and send fresh tests.
Keep Suped's alerts enabled after enforcement. Investigate new legitimate failures before authorizing additional servers or reducing the policy.

Frequency asked questions

Use the include mechanism or outbound IP addresses supplied for your account by Gigabyte Telecom support. I couldn't verify a public SPF include for customer accounts. Do not assume that the provider's root domain is an SPF include or copy its corporate SPF record.

Obtain the selector from support or the s= tag of a real DKIM-Signature header. Combine it with the signing domain in d= to look up selector._domainkey.signing-domain. The selector and public key must match the key used by the sending server.

Yes. A passing DKIM signature with a signing domain that satisfies DMARC alignment is sufficient. For a route with a provider-owned return path, adding SPF to your visible From domain does not change that return path. Confirm DKIM and the final DMARC result on a delivered message.

The suffix names Gigabyte Telecom's domain. It is a clue to the network operating an IP, not proof that a particular email is legitimate or sent through its hosted mailbox service. Check the connecting IP's current PTR record, forward DNS, message authentication, and provider confirmation before authorizing the source.

Keep the existing p=reject policy while configuring Gigabyte Telecom. Fix the affected sender's SPF or DKIM path and verify fresh messages. A monitoring-only starting policy is appropriate for a domain without established enforcement, not a routine prerequisite for adding a sender.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing