Dataweaz

squarespace.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
March 25, 2003
Expires on
March 25, 2027
Name servers
ns04.squarespacedns.com, ns03.squarespacedns.com, ns02.squarespacedns.com, dns4.p06.nsone.net, dns3.p06.nsone.net, dns2.p06.nsone.net, ns01.squarespacedns.com, dns1.p06.nsone.net
Mail servers
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx4.googlemail.com, aspmx3.googlemail.com, aspmx5.googlemail.com, aspmx2.googlemail.com
DMARC
Reject
SPF
Soft
DKIM
5 keys found
Website
See the website

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 squarespace.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; aspf=r; fo=1; pct=100; 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 squarespace.com.

RuleValueResult
includesquarespace-mail.comAllowed
includemail.zendesk.comAllowed
include_spf.google.comAllowed
includesendgrid-spf.email.squarespace.comAllowed
includeregistrarmail.netAllowed
include_spf.mailrelay.rrpproxy.netAllowed
ip48.41.221.0/24Allowed
ip48.36.86.0/24Allowed
ip434.174.163.32/27Allowed
ip4162.216.148.0/27Allowed
all—Suspicious

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 include:squarespace-mail.com include:mail.zendesk.com include:_spf.google.com include:sendgrid-spf.email.squarespace.com include:registrarmail.net include:_spf.mailrelay.rrpproxy.net ip4:8.41.221.0/24 ip4:8.36.86.0/24 ip4:34.174.163.32/27 ip4:162.216.148.0/27 ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
mandrillMandrillRSA 1024 bits · shortActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 2048 bitsActive
key1—RSA 2048 bitsActive
key2—RSA 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 squarespace.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from squarespace.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 @squarespace.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

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

squarespace.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.squarespace.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.squarespace.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.squarespace.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.squarespace.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 squarespace.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
A198.49.23.180
A198.49.23.181
A198.185.159.180
A198.185.159.181

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
ns04.squarespacedns.com45.54.22.193
ns03.squarespacedns.com45.54.22.129
ns02.squarespacedns.com45.54.22.65
dns4.p06.nsone.net198.51.45.70
dns3.p06.nsone.net198.51.44.70
dns2.p06.nsone.net198.51.45.6
ns01.squarespacedns.com45.54.22.1
dns1.p06.nsone.net198.51.44.6

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @squarespace.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
10aspmx.l.google.com142.251.5.26
20alt1.aspmx.l.google.com192.178.213.26
20alt2.aspmx.l.google.com172.253.148.27
30aspmx4.googlemail.com142.250.147.26
30aspmx3.googlemail.com172.253.148.27
30aspmx5.googlemail.com172.253.152.26
30aspmx2.googlemail.com192.178.213.26

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

NameContent
squarespace.comyahoo-verification-key=M9bvd644/VMh6U00Krwt5kvZNMB/w54Q4ynBedHIqOg=
squarespace.com_g93o5msuzwgbqxf7aet2vp472xkcdni
squarespace.comautodesk-domain-verification=OIiVxJrWZxwtj8O9cTGf
squarespace.comairtable-verification=6f64da2fbf9a20671f629a7bce16bfe5
squarespace.comanthropic-domain-verification-6c445d=wNcntYC79lpQKOmhb9h3uVUp4
squarespace.comopenai-domain-verification=dv-62K73GBFx0ak0DeimlySthXn
squarespace.comcursor-domain-verification-5atzdh=G88XLIW0HoSrXYpz90Icz9sa0
squarespace.comdropbox-domain-verification=9l7rf4p0wc9j
squarespace.comjamf-site-verification=Rtc-BZaPHnuqZmWggwyRew
squarespace.comtwilio-domain-verification=c9cdda756fb6f761678e330875455bc4
squarespace.comgoogle-site-verification=VenKbbgMTiaa1wJ_ySMZKFA3nfhnUEAZckAUOp0dytg
squarespace.comgoogle-site-verification=hBfLDRLm_7xc28TI8H5zd-CmBwB6DtkHHAXMoa5mBe0
squarespace.comdocusign=54d34e8a-b4bb-4975-a977-1024bbf1cb1c
squarespace.comdocusign=40e06657-1a9a-4e6b-b55d-548e0b9c0a97
squarespace.comgoogle-site-verification=OOBNwn_eiZcawRwjSDl1hVwGkl9mynl6tTON6qIUSQc
squarespace.comfacebook-domain-verification=02pcb9aata32foeofjc5l5d96vcgfp
squarespace.comv=spf1 include:squarespace-mail.com include:mail.zendesk.com include:_spf.google.com include:sendgrid-spf.email.squarespace.com include:registrarmail.net include:_spf.mailrelay.rrpproxy.net ip4:8.41.221.0/24 ip4:8.36.86.0/24 ip4:34.174.163.32/27 ip4:162.216.148.0/27 ~all
squarespace.comMS=80BAE8129C17E5AE8C975C3916FE0762E854B4C9
squarespace.comMS=ms91395519
squarespace.comatlassian-domain-verification=XmsOb8xGdHRMqn/qh91SBVqL1LQctNaopAew1Li0fB9OMaFfDqI9c/ZIZPI5I8kY
squarespace.commgverify=ebea2f3c85bdc4dd207e7d7c91c73946bf1fe749ec2f244a23427f106b8a7437
squarespace.comh1-domain-verification=uN8V8ofDaAiiY7kewHURuigi4FnYePsATWHG7fKu9GF7St84
squarespace.comslack-domain-verification=JQ7RgZvTvv5y8A2wT3mRt8GFwxubOEo57beNQAwW
squarespace.comt8whs493nvslv3v2pfzl7pcv86k5fqnj
squarespace.comgoogle-site-verification=HeURgznwlLL8xdGii24CTN6S_q5FXDbLX7jyUP6N8XY
squarespace.comgoogle-site-verification=47px85SXlRbteJV96eHmkPZY58kJcf7oLCC8TFsajWA
squarespace.comgoogle-site-verification=U_jN2U77WWPeulVQ4h6rr7OtRztcHY7jwoUGv3CfPBQ
squarespace.comelastic-cloud-verification=7c5a67715a62aed52d2e41b5a3d84908256c761e2421c4aa52c8b861e05ae8f1
squarespace.comwrike-verification=NjkxMTg1Njo3MTBjMDIzNWVlM2NhNjU2MDc3YzM0MTE3YTZmYmM4YTEzNWQ1ZmIwZjVlNmE2MjRmNWI3ODY0OGFiMGU5YWFk
squarespace.comTAILSCALE-YZOBN6TpzuwAfh22pvBT
squarespace.comgoogle-site-verification=aQgKIlHqg5Ehd7tP0Usr7IlNC8xi_wQDd-U0Epda9oo
squarespace.comgoogle-site-verification=RdFDT0L7o6DB9H3YCzIv17-nz_Ia_JMsh_KNV2L_gjc
squarespace.comgoogle-site-verification=KsaabOANH6kdIsCwO41RGFXaEt15E10bL5nd0TJZAcQ
_dmarc.squarespace.comv=DMARC1; p=reject; aspf=r; fo=1; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]
mandrill._domainkey.squarespace.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
zendesk1._domainkey.squarespace.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.squarespace.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB
key1._domainkey.squarespace.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqhI5rKs4eQK/bINDlFI1hevswCX3wmqxknR85s3UgLHZQt61plsrrDgPxmxdV7oYOgvGY4QGVUmDxo30v8Tv2g2TXrbKtdfDhqjBasrXGuYq+u83g6nkfvGz9C4B9bXyWr8fjegJPr6OQDEde4m8dZbJaKI3iNbx3LqXtPmGg4HXWJsWXWpk0ll7oeM5c+d1dPH5iYsAkTnc/eUTIyAlfeJ7zs2d1x2s+8hS2/okzjjjnqR1/j5oTBr4gciRvtmHAZiNKdGsSAPNWYQe9llOB71JUGn+0w1AW9z3Nro+00pYl2rOzgdhGZTyDrxbJJbhao9eL61ENHaaweQhDsA9UQIDAQAB
key2._domainkey.squarespace.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnnouhe2ZR3zdd6lxjBH18CeYTYl46iA7g4N0v4k9UNFaP99NlCQj2NzNAzcRTNKHf9bnxewI7y3d3+Y6Y5IsLQFbt8YAqcgmhTAqVBUr3UC9uc/cNb7j8xxA7bB/eIeRQ7DXSJYqWAAhp/rOAYY0lmfioM7hDyPc8cIh/jUlH42c7fcbZpEvVVn9Pu0SVjr19ptZDS+Pp5W1PJIhDG07ovTFdlJ3uUtpEcnOIuynseegGGwIR7Js9eEv1Lh+bBGhQluXOkU+G0htzM9HFlC02hRVsNmm5uJa+y2fnNXyn1p/nVX0Ybc3v4lsTmevnaEd/NTv6U/dTkj5lvIbL2ZOXwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
198.49.23.180Website198.49.23.0/24
198.49.23.181Website198.49.23.0/24
198.185.159.180Website198.185.159.0/24
198.185.159.181Website198.185.159.0/24
45.54.22.193Name server ns04.squarespacedns.com45.54.22.0/24
45.54.22.129Name server ns03.squarespacedns.com45.54.22.0/24
45.54.22.65Name server ns02.squarespacedns.com45.54.22.0/24
198.51.45.70Name server dns4.p06.nsone.net198.51.45.0/24
198.51.44.70Name server dns3.p06.nsone.net198.51.44.0/24
198.51.45.6Name server dns2.p06.nsone.net198.51.45.0/24
45.54.22.1Name server ns01.squarespacedns.com45.54.22.0/24
198.51.44.6Name server dns1.p06.nsone.net198.51.44.0/24
142.251.5.26Mail server aspmx.l.google.com142.251.5.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com, Mail server aspmx2.googlemail.com192.178.213.0/24
172.253.148.27Mail server alt2.aspmx.l.google.com, Mail server aspmx3.googlemail.com172.253.148.0/24
142.250.147.26Mail server aspmx4.googlemail.com142.250.147.0/24
172.253.152.26Mail server aspmx5.googlemail.com172.253.152.0/24

WHOIS of the domain squarespace.com

Domain Name: SQUARESPACE.COM
   Registry Domain ID: 96151137_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2025-02-21T09:18:43Z
   Creation Date: 2003-03-25T21:26:58Z
   Registry Expiry Date: 2027-03-25T20:26:58Z
   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
   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: DNS1.P03.NSONE.NET
   Name Server: DNS2.P03.NSONE.NET
   Name Server: DNS3.P03.NSONE.NET
   Name Server: DNS4.P03.NSONE.NET
   Name Server: NS01.SQUARESPACEDNS.COM
   Name Server: NS02.SQUARESPACEDNS.COM
   Name Server: NS03.SQUARESPACEDNS.COM
   Name Server: NS04.SQUARESPACEDNS.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T13:09: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.