Dataweaz

bofa.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
May 15, 1992
Expires on
May 16, 2027
Name servers
f.ns-boa.us, e.ns-boa.biz, d.ns-bac.info, c.ns-bac.net, b.ns-bac.org, g.ns-bac.com, a.ns-bac.com
Mail servers
mxa-0000ec05.gslb.pphosted.com, mxb-0000ec05.gslb.pphosted.com
DMARC
Reject
SPF
Soft
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

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

Record

v=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=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 bofa.com.

RuleValueResult
includebankofamerica.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:bankofamerica.com ~all

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 bofa.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from bofa.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 @bofa.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

bofa.com  MX  10 mx1.bofa.com.
bofa.com  MX  20 mx2.bofa.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.bofa.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

bofa.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.bofa.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.bofa.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.bofa.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.bofa.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 bofa.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
f.ns-boa.us95.101.36.64
e.ns-boa.biz96.7.49.64
d.ns-bac.info23.61.199.64
c.ns-bac.net193.108.91.121
b.ns-bac.org184.26.160.64
g.ns-bac.com156.154.130.100
a.ns-bac.com2.16.40.64

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @bofa.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
10mxa-0000ec05.gslb.pphosted.com208.84.65.230
10mxb-0000ec05.gslb.pphosted.com208.84.65.230

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.bofa.com.

NameContent
bofa.comwebexdomainverification.7VRFC=e8872648-bc79-4b9c-8b43-94748fb4b3f0
bofa.com00Dd0000000fllf=1TBKh000000Kynh
bofa.com00DD50000009T2F=1TBD5000000CaTE
bofa.com00DDn0000014WMF=1TBDn0000000001
bofa.com"onetrust-domain-verification=01759ed35a874fd8a7e0c5ea18401910"
bofa.comccisso=e1100421-46df-4eb5-b9c1-d11fe147d3e7
bofa.com00D37000000J5Lh=1TBKb000000TN1j
bofa.com00D30000000nW2o=1TBKd0000000006
bofa.com00DDE0000044SVQ=1TBDE000000001T
bofa.comonetrust-domain-verification=0528ad208d144b188e657b0ffbfd6bc7
bofa.comanthropic-domain-verification-pqjv8n=oV84VxR5EDNPLjYtRy8i5Ke5a
bofa.comgoogle-site-verification=7KA2KW0wOWlHOiC6DBf6bNnexwl5LMpsnB-Vz7tDEH0
bofa.com00D2g0000000ZPI=1TBD1000000000M
bofa.com00DDY0000000Q63=1TBDY000000KyjB
bofa.com00DDc0000005CbI=1TBDc0000004CEi
bofa.comU4FLT20UPAQOM52YRBQH7T1K5PXBL1EG0LRZGS5FZ
bofa.comv=spf1 include:bankofamerica.com ~all
bofa.com00DHo000007ESQH=1TBHo000000sXtR
bofa.com00DDE0000045mMg=1TBDE000000CaR7
bofa.com00DDL00000D40CM=1TBDL000000001J
bofa.com00D750000000NEs=1TBDh0000004C94
bofa.com00D36000000rZom=1TBHq0000004C93
bofa.com"onetrust-domain-verification=19a6771827ec4c17909d00735a2e7518"
bofa.com00D30000001FXpf=1TBHt000000000L
bofa.comMS=ms20084233
bofa.comdocusign=2ac67c63-752d-4978-8909-52b35d4ed876
bofa.comwebexdomainverification.DPFR=a0591473-21be-41e1-b8d6-e7f3528d057b
bofa.com00D7g0000005BwN=1TBD70000004C9X
bofa.com00D30000001H88T=1TBKX000000Gmb8
bofa.comwebexdomainverification.8BOEU=1c0859c4-ed8c-4cda-b776-a2f7e686371c
bofa.comdell-technologies-domain-verification=bofa.com_af4da4c5-c58f-4f79-a291-a4b3307598b9_1730992560
bofa.comwebexdomainverification.7WJTK=80552637-d788-48d4-b755-7cf99668d990
bofa.com00D300000000K1b=1TBKZ0000004C9I
bofa.comopenai-domain-verification=dv-dUCHiq7whBr8a4mi2NCVm4Xr
bofa.comapple-domain-verification=bpvWW0rLipIyXGKN
bofa.com00D4C0000008x25=1TBD10000004C9c
bofa.comwebexdomainverification.AU51=a10f74e4-d5f4-4433-8fa4-b37c6cf04bbb
bofa.com00D400000007EoN=1TBKY000000fxU3
bofa.com00D3K0000008lCp=1TBDc0000008OK7
bofa.com_8x6pttojhdnovypbyv9rsaxz2cjtbak
bofa.com00D52000000JPHM=1TBDU000000000B
bofa.comwebexdomainverification.DMQQ=a4d1fc3a-0515-49fb-b2ea-cc80db2c01df
bofa.comwebexdomainverification.1TKU2=d9c8f391-62a5-4b34-b9db-8b54cdf9a292
bofa.comapple-domain-verification=Lnljorkg6pnKTtkc
bofa.comwebexdomainverification.=427157d3-d3c4-4207-b17e-df591a3f1d8a
bofa.comwebexdomainverification.EPKA=f85e09b7-9e6c-4fdd-ba48-8337397669d6
bofa.comapple-domain-verification=nG5Zd4g1UJM2hFj4
bofa.com00D300000005zGi=1TBKe000000oLkP
bofa.comwebexdomainverification.D04F=3be65cd4-e3a6-498c-8b33-b7bbcdc5f234
bofa.com00DDn0000014WHa=1TBDn000000XZAH
bofa.com00D30000001HRSt=1TBKe000000blJO
bofa.comwebexdomainverification.KK48=e778cf5c-3430-4f7f-be0c-c0a630b025d4
bofa.com00DE0000000ZaqE=1TBHt000000XZE9
bofa.comwebexdomainverification.BV9Q=af05801a-80b8-42c2-987a-498e51f82fd7
bofa.com00D700000009PLP=1TBKe0000004C93
bofa.comciscocidomainverification=207264518e598e8b0eba9e5b07566fca4186d60bc259e178af8220c6659c1406
bofa.comdocusign=4d49ce29-9e7c-4d23-8e1e-50768d283b95
bofa.com00D46000000aATr=1TBKk0000000001
bofa.com00D0b000000De84=1TBKW000000Gma9
bofa.com00DDk000000E4pS=1TBDk0000008ON0
bofa.com00D30000000nqfl=1TBHt000000CaR7
bofa.com00D8I0000016LkC=1TBDa000000000b
bofa.comwebexdomainverification.KK43=c0e7eb3c-f53b-4409-8904-9ec495be8ed8
bofa.com00D3000000071D4=1TBKX0000008OIy
bofa.com00DDY0000000PuC=1TBDY0000004C98
bofa.comDirectFedAuthUrl=https://fedsso-pp.bankofamerica.com/idp/SSO.saml2
bofa.com00D210000002QLf=1TBDl0000008OIP
bofa.comwebexdomainverification.1TKBV=84568d16-e1e9-4f77-948b-9902e56e0843
bofa.com00D1D000000jT9H=1TBDR0000008OI7
bofa.comwebexdomainverification.=efc58eb7-1637-47ac-9025-d3f06a9e9e2b
bofa.comDirectFedAuthUrl=https://fedsso.bankofamerica.com/idp/SSO.saml2
bofa.com00D300000000Lsb=1TBHp0000008OI5
bofa.comwebexdomainverification.D182=5754a906-4982-4593-99d9-a21ad9cecb74
bofa.com00D30000001H1Cv=1TBHt0000000001
bofa.com00DDG00000NAncy=1TBDG0000008OKW
bofa.com00D60000000KTAU=1TBKZ000000001U
bofa.com00DDn00000122RU=1TBDn0000004C9D
bofa.comapple-domain-verification=DFQFhqNOkD4F7JP7
_dmarc.bofa.comv=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]

Related IP addresses

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

IP addressUsed for/24 block
3.173.23.90Website3.173.23.0/24
3.173.22.90Website3.173.22.0/24
3.173.21.90Website3.173.21.0/24
95.101.36.64Name server f.ns-boa.us95.101.36.0/24
96.7.49.64Name server e.ns-boa.biz96.7.49.0/24
23.61.199.64Name server d.ns-bac.info23.61.199.0/24
193.108.91.121Name server c.ns-bac.net193.108.91.0/24
184.26.160.64Name server b.ns-bac.org184.26.160.0/24
156.154.130.100Name server g.ns-bac.com156.154.130.0/24
2.16.40.64Name server a.ns-bac.com2.16.40.0/24
208.84.65.230Mail server mxa-0000ec05.gslb.pphosted.com, Mail server mxb-0000ec05.gslb.pphosted.com208.84.65.0/24

WHOIS of the domain bofa.com

Domain Name: BOFA.COM
   Registry Domain ID: 860443_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-05-12T05:10:17Z
   Creation Date: 1992-05-15T04:00:00Z
   Registry Expiry Date: 2027-05-16T04:00:00Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: A.NS-BAC.COM
   Name Server: B.NS-BAC.ORG
   Name Server: C.NS-BAC.NET
   Name Server: D.NS-BAC.INFO
   Name Server: E.NS-BOA.BIZ
   Name Server: F.NS-BOA.US
   Name Server: G.NS-BAC.COM
   DNSSEC: signedDelegation
   DNSSEC DS Data: 19460 8 2 28442D4ED3CEF0EDD9470C5EE97E98F2BB7A67EA84360B23AF84675D2A725FEF
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T21:36:58Z <<<

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.