Dataweaz

affirm.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
December 2, 1999
Expires on
December 2, 2027
Name servers
ns-1463.awsdns-54.org, ns-1890.awsdns-44.co.uk, ns-217.awsdns-27.com, ns-614.awsdns-12.net
Mail servers
mailstream-central.mxrecord.mx, mailstream-west.mxrecord.io, mailstream-east.mxrecord.io
SPF
Soft

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

DMARC tells mail servers what to do with an e-mail that claims to come from affirm.com but fails SPF and DKIM checks.

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=quarantine; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for affirm.com.

RuleValueResult
include%{i}._ip.%{h}._ehlo.%{d}._spf.vali.emailAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

E-mail signing (DKIM)

DKIM keys published by affirm.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
k1MailchimpRSA 1024 bits · shortActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 2048 bitsActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to affirm.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from affirm.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @affirm.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

affirm.com  MX  10 mx1.affirm.com.
affirm.com  MX  20 mx2.affirm.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.affirm.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

affirm.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.affirm.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.affirm.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.affirm.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.affirm.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of affirm.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns-1463.awsdns-54.org205.251.197.183
ns-1890.awsdns-44.co.uk205.251.199.98
ns-217.awsdns-27.com205.251.192.217
ns-614.awsdns-12.net205.251.194.102

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @affirm.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10mailstream-central.mxrecord.mx172.65.64.78
20mailstream-west.mxrecord.io172.65.220.210
20mailstream-east.mxrecord.io172.65.213.128

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.affirm.com.

NameContent
affirm.comdocusign=b06e9be3-7666-4868-9dcc-4170a01f13fa
affirm.comfacebook-domain-verification=mljae013pphr1v7s9qmjr1od0q4b37
affirm.comgoogle-site-verification=oPKjTfgSY7Gb_ICYHM4lsKIvTDIumzw51ULdQByWEpI
affirm.comgoogle-site-verification=pAkhUEXOAsw03YML584P4Mz6AGWKrI_rvVMIlMA4TMU
affirm.comgoogle-site-verification=s822qoydlNAOABuINWk0Znrj67HclLkvZ2VXCX6Nmhc
affirm.comjamf-site-verification=szXyQtQBT9BqzeGBWTKfSw
affirm.comjumio-up-idp-domain-verification=96ab6d36-87c5-4b60-b28f-52d4b142b4d5
affirm.commongodb-site-verification=fqxbrWhHRvG385BWYMqDU3TDjQLSGHpg
affirm.comnotion-domain-verification=GwCK7iKBVct6TTvYCzMWbPgFaKUtZqdSrc9ZTQEDZ42
affirm.comonetrust-domain-verification=c63ef161ba274c75aefba3883ca2fc05
affirm.comopenai-domain-verification=dv-g5d0T9rsUBFcnyS05B4NGInp
affirm.comparallels-domain-verification=ca3b420b7d2543a59ed0bbd750f850e30ff2363e91444abf87ec5ed6397d5f4b
affirm.compardot778433=e67349940141eb000ae0e650dc81b761d64a27f949669078aec081322b1cbb6c
affirm.compardot778433=fb24e220f454dd50a1a8eb4ce4fb9e03ce8a578f671906e6a66968e824c5e169
affirm.compardot963153=538c428c1d9495f89dc9645e5ab71a6a39ad535358c9ac950d1b513070c5eebe
affirm.comsending_domain778433=c2dbea95d44d98d2a63c7469add3164700dbec73184e3037fa85361f93ec7ff3
affirm.comsending_domain963153=538c428c1d9495f89dc9645e5ab71a6a39ad535358c9ac950d1b513070c5eebe
affirm.comslack-domain-verification=Zm7pKyRJuiFUsnxgltPQQC8Tp8Kxep2b29afZgy7
affirm.comsmartsheet-site-validation=tqVQ74cZA1pKsWlc_D5QlMPNb8vYtvNb
affirm.comstatus-page-domain-verification=987w3nfgs7sg
affirm.comstripe-verification=2759d29e60c0bae7d9e8212a26bc1ec10e7908af6f0522bf956e547af7208cad
affirm.comstripe-verification=2d0b5051e630a87b101bdb649af6aab1469d7dfb8e724193dff3c74e184a9047
affirm.comstripe-verification=3b73576e1b62f90177c431aed31f2c31a2db959eeae803df79170108c715258d
affirm.comstripe-verification=8894522d609849b1342f894c8055a03aa1ea7a88b8526f50aeb2d7721c4f8291
affirm.comstripe-verification=ee3426c0fb21c0e8a3f1f5368401b06dc9b9eeb94d04f3ea91bf9e8223ecb3ec
affirm.comv=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
affirm.comwhz0k8v6zgmqlf35g8mlgtpjjxvjwvlg
affirm.com4ljp7ydys3rtqbxq2yjdqrg9z321lq2b
affirm.comHZIXGSRIU
affirm.comZOOM_verify_Pcvm9macqAX0TOiB7I4IH8
affirm.com_globalsign-domain-verification=VPemhDee0EKRXi0IPzeSUrn849jHevrjIaTeDYOTZ4
affirm.com_qm6p025ab7k2h7kb2y0j0zp9cwscrk9
affirm.comanthropic-domain-verification-h8f8k6=PpUd4cztMwsLI1DtU02QAu6j8
affirm.comatlassian-domain-verification=DNaiSBS5ThZ8raU2CEfYYtOMwoTp18LXzmzqIAqebu9p01eO5kNlarSrfiBcHdv3
affirm.comatlassian-sending-domain-verification=d1e7e26c-2a5c-4306-9df8-0e600bc70f7e
affirm.comca3-4f17d21d484146598a0674fbbbe45ecd
affirm.comcanva-site-verification=tICckyw9TNkjWqLhWySfNQ
affirm.comcursor-domain-verification-8x01t1=NWLM4fVaIkaxy6uhunmiMP9vm
affirm.comdecagon-domain-verification-rx2vg4=xMQQmURySInNzb3Q753GcsV2n
affirm.comdocker-verification=7ac102e0-2b62-4b05-b134-775363b687a2
affirm.comdocusign=73b980e5-4728-47f9-92ed-d2319fef15e2
_dmarc.affirm.comv=DMARC1; p=quarantine; rua=mailto:[email protected]
google._domainkey.affirm.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCB8ZYQZkr2e1qwVvwqNAp441a78IeziNJzRDBnBzYGd0Q/0+HiwPd3uZ7R4Cz4ag+qp6qYQ2w5t+qFEaixQ0hZ5r+hTD6/zogiTlbbBhBZP+wpuiA9y7meQcNwH1aVNyai8QvDOqBC9bvzt5MQM1526kC1O5G0Zryi60wJsD3QswIDAQAB
k1._domainkey.affirm.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
k2._domainkey.affirm.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.affirm.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.affirm.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3myD6Me83+5GMtvj7IgQWIMmEI5+TpSCYzCCAMRve4MlZS/lngOUpPftbn/6/yKKckTUU+2Mq0yk6B6ZeB+ggFkTRc+0hJKQ0SJyatsqrR/YfgMJv2O5RiPiK3S4A3FF0wcHWccKtSck3MF3laPNUIzPRpZxPDdTx0pGvD2RJ65sLRNSmzOmWcVV3D7yXGWrY501nDbybaDhDWFFp1ihCZZEzsEplyhzUWnn29332HBiBLnbg5uvlp+LwhpTXD0Qq1VCuLA6n+KvbrB1MAyrXHCQNGX/KFFdnJqgriEtl0oahwNVtHJM8SIvEi29IrpTr7lChPpBtvdTHCa4xfu9PQIDAQAB
s2._domainkey.affirm.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDch6a85oaQKFVS9j47guTOEtDjBpaX29VOr47xNmnrwzVf8ZcSL587zzzRgdctpU0wVYhBNvR/7L1VNB/OsiuvK0pf5ppyl9FYWt4L82BH/Nyl4luv83zeXbP8qwtfstg2F03VhZbHQDjyPUOvbMDIzyJ4zPfKu3Dhy5KXTc3plwIDAQAB
zendesk1._domainkey.affirm.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.affirm.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

IPv4 addresses used by affirm.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
162.159.140.33Website162.159.140.0/24
172.66.0.33Website172.66.0.0/24
205.251.197.183Name server ns-1463.awsdns-54.org205.251.197.0/24
205.251.199.98Name server ns-1890.awsdns-44.co.uk205.251.199.0/24
205.251.192.217Name server ns-217.awsdns-27.com205.251.192.0/24
205.251.194.102Name server ns-614.awsdns-12.net205.251.194.0/24
172.65.64.78Mail server mailstream-central.mxrecord.mx172.65.64.0/24
172.65.220.210Mail server mailstream-west.mxrecord.io172.65.220.0/24
172.65.213.128Mail server mailstream-east.mxrecord.io172.65.213.0/24

WHOIS of the domain affirm.com

Domain Name: AFFIRM.COM
   Registry Domain ID: 14422559_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2025-11-02T04:16:06Z
   Creation Date: 1999-12-02T11:39:45Z
   Registry Expiry Date: 2027-12-02T11:39:44Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: NS-1463.AWSDNS-54.ORG
   Name Server: NS-1890.AWSDNS-44.CO.UK
   Name Server: NS-217.AWSDNS-27.COM
   Name Server: NS-614.AWSDNS-12.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T16:48:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.