Dataweaz

theguardian.com

Summary

Registrar
GoDaddy.com, LLC
Status
clientDeleteProhibited
Created on
July 6, 1994
Expires on
July 5, 2027
Name servers
dns2.p04.nsone.net, dns3.p04.nsone.net, dns4.p04.nsone.net, ns01.theguardiandns.com, ns02.theguardiandns.com, ns03.theguardiandns.com, ns04.theguardiandns.com, dns1.p04.nsone.net
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.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 theguardian.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
—

Record

v=DMARC1;p=reject;rua=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 theguardian.com.

RuleValueResult
include_spf.google.comAllowed
includespf_c.oraclecloud.comAllowed
include_spf.salesforce.comAllowed
include_spf1.theguardian.comAllowed
ip4199.255.192.0/22Allowed
ip4199.127.232.0/22Allowed
ip454.240.0.0/18Allowed
ip469.169.224.0/20Allowed
ip423.249.208.0/20Allowed
ip423.251.224.0/19Allowed
ip476.223.176.0/20Allowed
ip454.240.64.0/18Allowed
ip476.223.128.0/19Allowed
ip4216.221.160.0/19Allowed
ip4206.55.144.0/20Allowed
ip424.110.64.0/18Allowed
all—Rejected

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 include:_spf.google.com include:spf_c.oraclecloud.com include:_spf.salesforce.com include:_spf1.theguardian.com ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 ip4:24.110.64.0/18 -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive

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

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

theguardian.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.theguardian.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.theguardian.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.theguardian.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.theguardian.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 theguardian.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
A151.101.1.111
A151.101.65.111
A151.101.129.111
A151.101.193.111
AAAA2a04:4e42:600::367
AAAA2a04:4e42::367
AAAA2a04:4e42:200::367
AAAA2a04:4e42:400::367

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
dns2.p04.nsone.net198.51.45.4
dns3.p04.nsone.net198.51.44.68
dns4.p04.nsone.net198.51.45.68
ns01.theguardiandns.com45.54.51.1
ns02.theguardiandns.com45.54.51.65
ns03.theguardiandns.com45.54.51.129
ns04.theguardiandns.com45.54.51.193
dns1.p04.nsone.net198.51.44.4

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @theguardian.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.com74.125.71.26
20alt2.aspmx.l.google.com142.251.127.26
20alt1.aspmx.l.google.com192.178.213.27
30alt3.aspmx.l.google.com172.253.148.27
30alt4.aspmx.l.google.com142.250.147.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.theguardian.com.

NameContent
theguardian.commiro-verification=9bbe1ce0f13ab2efbbda64d44bd0db3c1f17fd60
theguardian.comcisco-ci-domain-verification=394bd3979592402fa40244fcf11f48e5e5014697e1f7e8587eba08075cdd79e3
theguardian.com_hfmu2x1szay737kpys7nmqjko311kxu
theguardian.commultiverse-domain-verification=3e7e7acf-12cc-4934-a23a-b8c0127fb091
theguardian.comslack-domain-verification=K3gfZj51sHXR6hxk5BVVfunkmGnHxc4NvwNtqo77
theguardian.comgoogle-site-verification=6-wiFtmcPHY78jVuZUE3io1c6c9SrSyjPVmUr7XRW2I
theguardian.comgoogle-site-verification=9SMJbNVsYm0GCVZbGVOMSzXajrK_pqVtjW3P007kaQo
theguardian.comgoogle-site-verification=I3xSjID5V7E9UDa3WSvvvpCqiqw1_34kG1Y_rz5dlV4
theguardian.comfacebook-domain-verification=9qqmd2kl745hph02i64iyoxvdphmi9
theguardian.combrave-ledger-verification=7e309ab3cd9203b886205458254a13f930f79821ea05031742f7dfc9285370c8
theguardian.comadobe-idp-site-verification=af3ef20fdc1d370aee02414a73ce0db9f1b465c21d53a369080184cd8e4b60f1
theguardian.comgoogle-site-verification=ujq5XlF5Ty7dwXv7S3AV99WRr8IwetZIjNqqloPpKmA
theguardian.comgoogle-site-verification=M9Q_QcvQQCoQEca1--d55J0QKwKZt0XgAAj9DJrJ0jQ
theguardian.compardot709753=1cfbb8fa5dabcb6befc9faa15661f500a64a6f22eb83bb146848633dbe7633cf
theguardian.comamazonses:2s68hEXFIHnDWOVNuEbZ06pSFJhN0qCtTx8lztmngls=
theguardian.comgoogle-site-verification=IU-vqTBscxkgU3J_f5i10_i624mvE3IjvYpeVPB2A98
theguardian.comapple-domain-verification=sVI2atim1Brh4UUx
theguardian.comgoogle-site-verification=4l7NequdA4a20U0D9YSw7ENlF69-hDeHXx21aU2UUC0
theguardian.comapple-domain-verification=4qbvNZKyKKZyBtdU
theguardian.comMS=ms94953828
theguardian.comMS=B95E020056873FBC8A077EEE2104192B3DBC1D61
theguardian.comdocusign=1f00efb3-0975-459c-b221-e46452a0f92a
theguardian.comintersight=123333260936a76db6d9dedc01d0ab4d61a9aae47515abbf0087e02a395747f9
theguardian.comRDOAB9Z9GAJESXAA11TST3LEI0RN5LQ4TES408NS
theguardian.comgoogle-site-verification=iLS6vcS8qLmM07nG-W_M3TAmaSEAAwoLBKovJCGOrOs
theguardian.comgoogle-site-verification=LCHObeC_7NyDBnXVNSqm5VJAve2qxx04PmUFc697Rf0
theguardian.com73t2Qr1jv9^4RG3CsYKp#F&^5S1fxpHtq9X5bLBQtc4q2PhMvMBmUrIh%LLGPb3V!XpnW9tvQd$tg^rLv!8ALDOQhhss%c9K%Xt
theguardian.comdocker-verification=42d9d88d-f950-4407-a675-3d843c16a983
theguardian.comonetrust-domain-verification=ce4031d6f7b94fdb9ed409ab9cf643d3
theguardian.comstripe-verification=85178DB4E6F4EC41721B7F20BD9F04B21E2B630ADA8156BDFE421272EBC2056F
theguardian.comopenai-domain-verification=dv-m8f1SR7Sj1HI4BIM0XsZAOxx
theguardian.comformstack-domain-verification=0cc5b58e5ea4088ab9333fcd9721a72f
theguardian.comv=spf1 include:_spf.google.com include:spf_c.oraclecloud.com include:_spf.salesforce.com include:_spf1.theguardian.com ip4:199.255.192.0/22 ip4:199.127.232.0/22 ip4:54.240.0.0/18 ip4:69.169.224.0/20 ip4:23.249.208.0/20 ip4:23.251.224.0/19 ip4:76.223.176.0/20 ip4:54.240.64.0/18 ip4:76.223.128.0/19 ip4:216.221.160.0/19 ip4:206.55.144.0/20 ip4:24.110.64.0/18 -all
theguardian.comasv=d971bc0397a95b5da450b9bfbad1212a
theguardian.comlucidlink-verification=4K96N0ZDHCHPKDZ538AFRVH54G
_dmarc.theguardian.comv=DMARC1;p=reject;rua=mailto:[email protected]
google._domainkey.theguardian.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnuDl3k22cx1FKi+XBTLdQOynnQwIko7h0eAszuUQ6cFFUZC5aJzKtfW26UZ/o8npeppiSZjmO02RoftFv7L0PjRY9991dtdfoId2W4T8wGQRFNMiK2HOa5E2U7toANOss4atZuNSL/Wz431qiUhSAJke8w/2L4mO1cniK1eq6k6JHzQ21329B6rUXj4JG4F9NgpAZhMpkD7zIK7CQGuuZFzfGvIE4UZw7/f9Sa8nbFZJT37l3BsmlhU582YwzoELZ0ezC0NHflQKzfdaW6AkPZr6hAlT7cODjKSNTl6dwSIHFZMZOoo3KQxg3UHYIQ+asKsf9zjUgXi1KiAEWjHSbQIDAQAB
k2._domainkey.theguardian.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.theguardian.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;

Related IP addresses

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

IP addressUsed for/24 block
151.101.1.111Website151.101.1.0/24
151.101.65.111Website151.101.65.0/24
151.101.129.111Website151.101.129.0/24
151.101.193.111Website151.101.193.0/24
198.51.45.4Name server dns2.p04.nsone.net198.51.45.0/24
198.51.44.68Name server dns3.p04.nsone.net198.51.44.0/24
198.51.45.68Name server dns4.p04.nsone.net198.51.45.0/24
45.54.51.1Name server ns01.theguardiandns.com45.54.51.0/24
45.54.51.65Name server ns02.theguardiandns.com45.54.51.0/24
45.54.51.129Name server ns03.theguardiandns.com45.54.51.0/24
45.54.51.193Name server ns04.theguardiandns.com45.54.51.0/24
198.51.44.4Name server dns1.p04.nsone.net198.51.44.0/24
74.125.71.26Mail server aspmx.l.google.com74.125.71.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.27Mail server alt3.aspmx.l.google.com172.253.148.0/24
142.250.147.26Mail server alt4.aspmx.l.google.com142.250.147.0/24

WHOIS of the domain theguardian.com

Domain Name: THEGUARDIAN.COM
   Registry Domain ID: 79632_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.godaddy.com
   Registrar URL: http://www.godaddy.com
   Updated Date: 2026-07-05T10:47:49Z
   Creation Date: 1994-07-06T04:00:00Z
   Registry Expiry Date: 2027-07-05T04:00:00Z
   Registrar: GoDaddy.com, LLC
   Registrar IANA ID: 146
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 480-624-2505
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: DNS1.P04.NSONE.NET
   Name Server: DNS2.P04.NSONE.NET
   Name Server: DNS3.P04.NSONE.NET
   Name Server: DNS4.P04.NSONE.NET
   Name Server: NS01.THEGUARDIANDNS.COM
   Name Server: NS02.THEGUARDIANDNS.COM
   Name Server: NS03.THEGUARDIANDNS.COM
   Name Server: NS04.THEGUARDIANDNS.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-03T09:33:14Z <<<

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.