Dataweaz

crypto.com

Summary

Registrar
Network Solutions, LLC
Status
clientDeleteProhibited
Created on
May 6, 1993
Expires on
May 7, 2034
Name servers
sima.ns.cloudflare.com, chad.ns.cloudflare.com
Mail servers
mxb-00543801.gslb.pphosted.com, mxa-00543801.gslb.pphosted.com, aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx3.googlemail.com, aspmx2.googlemail.com
DMARC
Reject

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 crypto.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Strict
SPF alignment
Relaxed
Failure reports
—

Record

v=DMARC1; p=reject; sp=reject; adkim=s; rua=mailto:[email protected],mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
mx—Allowed
ip413.228.3.214/32Allowed
ip4166.78.71.191/32Allowed
includesendgrid.netAllowed
include_spf.google.comAllowed
include_spf.atlassian.netAllowed
includespf-00543801.pphosted.comAllowed
includeamazonses.comAllowed
a—Allowed
include_spf.salesforce.comAllowed
all—Rejected

Top-level DNS lookups: 8 of 10 allowed

Record

v=spf1 mx ip4:13.228.3.214/32 ip4:166.78.71.191/32 include:sendgrid.net include:_spf.google.com include:_spf.atlassian.net include:spf-00543801.pphosted.com include:amazonses.com a include:_spf.salesforce.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
k1MailchimpRSA 1024 bits · shortActive
mandrillMandrillRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive

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

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

crypto.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.crypto.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.crypto.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.crypto.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.crypto.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 crypto.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.

TypeIP address
A104.19.223.17
A104.19.222.17
AAAA2606:4700::6813:df11
AAAA2606:4700::6813:de11

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
sima.ns.cloudflare.com173.245.58.222
chad.ns.cloudflare.com173.245.59.82

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @crypto.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
5mxb-00543801.gslb.pphosted.com205.220.160.186
5mxa-00543801.gslb.pphosted.com205.220.160.186
10aspmx.l.google.com108.177.15.27
50alt2.aspmx.l.google.com142.251.127.27
50alt1.aspmx.l.google.com192.178.213.26
100aspmx3.googlemail.com142.251.127.27
100aspmx2.googlemail.com192.178.213.27

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

NameContent
crypto.comstripe-verification=4C074D42C2767E2A9C88645EF9A435F8A6B32AF96C2C0AA8E459842ABBF1C015
crypto.comteamviewer-sso-verification=3c92f68977df46f8a836faf3dee19b1c
crypto.comtverrblc66rfaf718t8nkv3ska
crypto.comtwilio-domain-verification=8cef33ec97d09c8ffd8ca03b2a7ef585
crypto.comv=spf1 mx ip4:13.228.3.214/32 ip4:166.78.71.191/32 include:sendgrid.net include:_spf.google.com include:_spf.atlassian.net include:spf-00543801.pphosted.com include:amazonses.com a include:_spf.salesforce.com -all
crypto.com7baha1sqkqhek96j30iigj5jhj
crypto.com886cc7c2-4930-4e6c-82f7-b749a331f6bf
crypto.comCKO=cli_mbaj5wmc4fpu7gy6arlev3ipsy
crypto.comFoxit-domain-verification=27119cac84f28274d0e9435f684b9933
crypto.comMS=ms89782890
crypto.com_r7ph0jpxjinr0eiyfj2rnxb54691eyc
crypto.com_rj7cydrznqqclu1nvwivn7ci3u67pup
crypto.com_v12xhxzb2z7btr29qg4jzs6fjtfaeyi
crypto.com_x4vbsuduc7he5rma9yk4jq187rqtpqo
crypto.comadobe-idp-site-verification=d1d24ca7de8f48eabcb6db556f51aeb77f354775e863452fee8f6d0dc4e9ba50
crypto.comapple-domain-verification=gkrEgGUVeHhuHMMruqzgVlhai0KyQuU8fFjhDCxRBZg
crypto.comapple-domain-verification=k42cyDihDFgZyDji
crypto.comatlassian-domain-verification=mPIKsb4ANOnJdLnDcm5/XNWhVwAf77WKi84paGU6D1gpB2lKTIanMUpNHQfgQn/A
crypto.comatlassian-sending-domain-verification=5519512d-035a-454e-a3c2-105757a7a8df
crypto.combox-domain-verification=bd7e193ce1d8807fc0c92872c1d8ebab1fc8207e9cddd5e256
crypto.combox-domain-verification=bd7e193ce1d8807fc0c92872c1d8ebab1fc8207e9cddd5e2562279f68fc6a0d4
crypto.comcursor-domain-verification-axv2zp=mYKLERga3bfWGVc9QKs4zFEH1
crypto.comdocker-verification=91d288c2-871b-4e61-ad9b-17dc7a66dded
crypto.comdocusign=44e85aef-c293-4280-a57e-c6805015f751
crypto.comfacebook-domain-verification=598suasmwyal84kh3gglgawu4kp26h
crypto.comfacebook-domain-verification=8y8dsk7b387u8fdzhwd38r7918jd61
crypto.comgoogle-site-verification=0BkiWmFJ3j6n9dB155uT7bjYG2W-SvIjaW43B2nVlic
crypto.comgoogle-site-verification=I7WDPOWEyGgthDtKQo87fedNKpc0HBvj63qimMVfvQU
crypto.comgoogle-site-verification=PCetuilY5Boe-estav7CPomAMy-r1Itp_pkS_w7zlb8
crypto.comgoogle-site-verification=QBNOiaBV-QoDHr_zovE1c1GTZnj4LS0dvSp0LktqXjY
crypto.comgoogle-site-verification=UmBlyd162v42XnvTlkcyJCcsFVFzbZP1xlqeAF1QrYY
crypto.comgoogle-site-verification=ZsldpD3RCgz2ntLBhPvWKAsL5uFtgUcxNuP5U0HDNe8
crypto.comjamf-site-verification=XIIIvRTCj711MkK70OauJA
crypto.commiro-verification=57041690cd985a8c994e4fc960e73460e844a257
crypto.commixpanel-domain-verify=c76c83bd-b6f1-42d9-a0fc-b9046f981edb
crypto.commongodb-site-verification=3dYblW5pflsGhK9sIKXE02aRNButG7TG
crypto.comnotion-domain-verification=FDuhhiLdG51uQQ069lihmtNg7812kZsCNV3zrF8Trap
crypto.compaloaltonetworks-site-verification=341cd8a6c026568fbf2f1d688bd2ab3a93300ac792771e4ac940019dbc73fdd2
crypto.comprofound-domain-verification-bjq5yx=NTKxYHpu01zqfoukonnGJqYbU
crypto.comsdzzsstffjsvrm1tl6w3vzjhnwnk7w6x
crypto.comsegment-site-verification=ymbSTvWR2lTKLIR4Cxtyv1bEQz5ShY9J
crypto.comshopify-verification-code=3qnHrrZ3HBGVPKTMpMgTOja8jUB3oj
crypto.comslack-domain-verification=3t9FUgZ4ZU1fSFKsi6RSvcHMatYSJsZ5n6zIQYPT
crypto.comstatus-page-domain-verification=71jf0xbkm9dv
_dmarc.crypto.comv=DMARC1; p=reject; sp=reject; adkim=s; rua=mailto:[email protected],mailto:[email protected]
google._domainkey.crypto.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxSzoxlDp2VvgzVrC6zkOC2cLAKpV0VRJZ/GNkHUI1M8Xp2ErAw3levyJYSXRqy0enNVcYGE3ITM+TaRiFit2XqksKCFCjYIp66AxBWdBCB3QxNypJbTuR7+wXKr99JcfK8r9Cc+bVJWh4qNm1c95Y7d/z7ZaV64oDKQQeRJ6ArD/jx4WeDiNKT4BM68ZWrxGkFweZR9pKp1uBPN/rOfgQypZJS1ds8cGaUtiQpoXOizBwVCm3qcQPPFFNbhCfdejEudGx9Q9r9SC8s5hCVQM/5cNswHnomJgE8Dj7rz867i2VAwpMX/nHnSLiAYUyl2KVfDGr1vnsDNhmiuhGIXRTQIDAQAB
k1._domainkey.crypto.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
mandrill._domainkey.crypto.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey.crypto.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt7ztqVI7GEwKY5JX7wMr5WG7uQvkc1YiA7YZWBbirZvZPFnsaw6e+rvcCLy4t5wsdDdIGdn9BuWudcSUJzQl4aVgttTrNQxO516LfJRw/qLo/1R1CoktU9jbLf2ZNY/dpLFlobkhzfw/4npj/worNobdsuUNLiR/CBfTDmU9JkXJYN6E2DlmO1ImLUJXH1joLsAGE6OPK+IiO5lydhfiV1Wxb7eAuaMiRTk1PhLFTMHIypUajXaF0FgozOeLZO37HAlaPBCutltq3nQbJVjAJB3GxeAaZBHFcE23UD8shE4g2Xr4U+8d9rAngb7Evz5sVhXQ6a/7LsXWuqRu5h//rQIDAQAB
s2._domainkey.crypto.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCb4VmbUf3MQdr3KFmbIInxNwHIgT1ORbSafvQgtOzeLaOauLAFtFTr+bE/HNE/Uf3a8FRXCOS05uLJ7Qn14Jew8r7H7nqL7PBxC7F4U2x2nJefewUbj/2IrityI9EPG8+uphNEWpnYn6h38B8vgAVu4pgiltRw/p0xzTfBb9pOwwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
104.19.223.17Website104.19.223.0/24
104.19.222.17Website104.19.222.0/24
173.245.58.222Name server sima.ns.cloudflare.com173.245.58.0/24
173.245.59.82Name server chad.ns.cloudflare.com173.245.59.0/24
205.220.160.186Mail server mxb-00543801.gslb.pphosted.com, Mail server mxa-00543801.gslb.pphosted.com205.220.160.0/24
108.177.15.27Mail server aspmx.l.google.com108.177.15.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com, Mail server aspmx3.googlemail.com142.251.127.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
192.178.213.27Mail server aspmx2.googlemail.com192.178.213.0/24
13.228.3.214Authorized by SPF13.228.3.0/24
166.78.71.191Authorized by SPF166.78.71.0/24

WHOIS of the domain crypto.com

Domain Name: CRYPTO.COM
   Registry Domain ID: 317197_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.networksolutions.com
   Registrar URL: http://networksolutions.com
   Updated Date: 2024-05-09T04:08:54Z
   Creation Date: 1993-05-06T04:00:00Z
   Registry Expiry Date: 2034-05-07T04:00:00Z
   Registrar: Network Solutions, LLC
   Registrar IANA ID: 2
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.8777228662
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   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: CHAD.NS.CLOUDFLARE.COM
   Name Server: SIMA.NS.CLOUDFLARE.COM
   DNSSEC: signedDelegation
   DNSSEC DS Data: 2371 13 2 118E5F9739C723FCAA4D916D272E15A8B3BFB86EF1A41CD9740CC3C83A1EE286
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T04:32:13Z <<<

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.