LDNS LDNS

// dns · txt

force.com TXT Record Lookup

Use this TXT record lookup tool to view all text-based DNS records for force.com. TXT records are commonly used for email authentication (SPF, DKIM, DMARC), domain ownership verification, and other purposes.

//01

What Are force.com's TXT Records?

TXT (Text) records for force.com contain text strings published in DNS. While originally designed for human-readable notes, TXT records are now primarily used for machine-readable data like email authentication policies and domain verification tokens.

force.com's TXT records reveal important information about the domain's email security configuration, which services have verified ownership of force.com, and any other text-based DNS data the domain administrators have published.

Each TXT record can hold up to 255 characters per string, though a single record can contain multiple strings concatenated together. Large records like DKIM keys often use this multi-string format.

//02

Common TXT Record Types

SPF (Sender Policy Framework) records start with "v=spf1" and specify which servers are authorized to send email on behalf of force.com. These are critical for preventing email spoofing and improving deliverability.

DKIM (DomainKeys Identified Mail) public keys are stored as TXT records under selector subdomains (e.g., selector._domainkey.force.com). DMARC policies are published at _dmarc.force.com and control how receiving servers handle unauthenticated email.

Domain verification records are used by services like Google ("google-site-verification=..."), Microsoft ("MS=..."), Facebook ("facebook-domain-verification=..."), and Apple ("apple-domain-verification=...") to confirm that force.com's owner has authorized the service.

//03

Understanding force.com's TXT Records

TXT records may appear cryptic at first, but most follow standard formats. Look for known prefixes to identify the type: "v=spf1" for SPF, "v=DMARC1" for DMARC, "v=DKIM1" for DKIM keys, and service-specific verification strings.

If force.com has an SPF record, it defines which IP addresses and services are allowed to send email as force.com. The presence of DMARC and DKIM records indicates stronger email authentication. Verification records confirm that force.com is linked to specific third-party services.

//04

TXT Record Lookup for force.com

This TXT record lookup tool automatically queries DNS for all TXT records published at force.com. You can also use command-line tools: "dig force.com TXT" on Linux/macOS or "nslookup -type=txt force.com" on Windows.

Note that some TXT records exist on subdomains rather than the root domain. DKIM keys, for example, are at selector._domainkey.force.com. DMARC policies are at _dmarc.force.com. Use the dedicated SPF and DMARC pages for deeper analysis of those specific records.

//05

Frequently Asked Questions

Does force.com have SPF? — Look for a TXT record starting with "v=spf1" among force.com's TXT records. If present, force.com has SPF configured to control which servers can send email on its behalf.

What TXT records does force.com have? — force.com's TXT records are categorized by type (SPF, DMARC, DKIM, verification, or generic TXT).

What are TXT records used for? — TXT records serve multiple purposes: email authentication (SPF, DKIM, DMARC), domain ownership verification for services like Google and Microsoft, and storing arbitrary configuration data.

How do I add a TXT record to my domain? — TXT records are added through your DNS provider's control panel. Log into your DNS hosting dashboard, add a new TXT record with the required value, and save. Changes typically propagate within minutes to hours.