Dataweaz

cox.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
March 23, 1995
Expires on
February 7, 2027
Name servers
ns.cox.net, ns.west.cox.net, ns.east.cox.net
Mail servers
cox-com.mail.protection.outlook.com
DMARC
Reject
SPF
Soft

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

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

Record

v=DMARC1; p=reject; sp=none; fo=1; ri=3600; 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 cox.com.

RuleValueResult
include%{d}.7b.spf-protect.agari.comAllowed
exists%{i}._i.%{d}._d.espf.agari.comAllowed
all—Suspicious

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 include:%{d}.7b.spf-protect.agari.com exists:%{i}._i.%{d}._d.espf.agari.com ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector2Microsoft 365RSA 1024 bits · shortActive
mandrillMandrillRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 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 cox.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from cox.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 @cox.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

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

cox.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.cox.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.cox.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.cox.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.cox.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 cox.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
A45.60.45.167
A45.60.49.167

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.cox.net98.163.68.36
ns.west.cox.net98.163.68.52
ns.east.cox.net98.163.68.37

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @cox.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
10cox-com.mail.protection.outlook.com52.101.42.16

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

NameContent
cox.comsn1@$q*^o0R0h@$TXx1ZE3^Jv1Y9$WUgF8IdqXR%NNVOBGy3nHSun4#HyfOPuObUMBTr0#rvt7BbjeaM9pDpOMusi0ZIZUZA!oX
cox.comstatus-page-domain-verification=gjp2gy2hmb41
cox.comapple-domain-verification=OytMjh_mSWLvqtsJzsiLgWSMtDIMM3TznlExRBpzTmE
cox.comIVrw78Pf1B9FFT5JcVyq6pMD1IY1R7Gwlauv3BxlUIMa2Bawn/J3ejSLA45mQFtvWIzlPVpmpdFUgsU1RcdJ/A==
cox.com_wbnkadgee1ro94r65wvx28m8qskuoh5
cox.comteamviewer-sso-verification=65482d5ad2ec42f3822cb0e44d7f60e2
cox.comwindsurf-verification=OOuMrkqxYFeQ6KjmWydUsthITm3kcQP8tWC0H7CfeBI=
cox.comamazonses:ScMmLdre1Y87fgi8PmLDFi7Fjnt89iIxpESwD3mUZdg=
cox.com0ed1fe018a20f5a232b86a4719be0942708fe2a23a
cox.comapple-domain-verification=KVUrEPeDn5D5oc13
cox.comDirectFedPassiveSignInUri=https://login.microsoftonline.com/9feebc97-ff04-42c9-a152-767073872118/saml2
cox.comintersight=2db29f213d260fdf444ed19de8a2a221facf0189f963d7e6faeae9da63961571
cox.compexip-ms-tenant-domain-verification=e09712b4-39a7-44ce-a036-a242f0e3f332
cox.comduo_sso_verification=xJKhKYGsPbCRksvTuogilXjFT3DKitQb6CWlRrCsdGN68uwruSsOkCQ91EPu19ab
cox.comSFMC-Wjt3vsR3dn1578QBUa-kejsVuDjbI3Gt45tK3z-O
cox.comsending_domain1011211=97e7f27e22688729ca1dc98758c3957012ac4a7a565b409746c8d4d473cdd556
cox.commiro-verification=dc28193af38475e7748c947cbe82fc1f8e603ebb
cox.comtwilio-domain-verification=6d61acd0c5f6ead0960811ebc3bcaf4b
cox.comlogmein-verification-code=b0ef02fe-6ba9-46a0-8a52-dcadde31c141
cox.com00DEk00000Uwy4A=1TBEk0000000azZ
cox.com9sfSyodIux70u+5qmDM75JSHzvp+/I1u/Yj1XyhPEvQLMiZVtPdc6AYoddzcvbVUQq0Crn7JO+H6JHVN2X88lA==
cox.comcmc-verification=a8149969-d9dc-407b-9240-d62a54c3c0f0
cox.com_njda7hlygcyp925jjehs4mc3l3xrrv1
cox.comcisco-ci-domain-verification=384365baf08fe6911a21433a71a8ddf2b11bdc43cbead60d18507d28b519a70
cox.comsmartsheet-site-validation=vczhKnCV6lmaMN6NmXE5yzNfjpx8f3L4
cox.comdocusign=fa5ca50b-8bd2-4173-bc49-098f89138b03
cox.comcmc-verification=f93c9f06-95d4-4e22-b9c9-ba5943f0010a
cox.com00D8c000007V7b7=1TBQo0000000DDN
cox.comasv=f6afe7c38daa36fbe173011604de1023
cox.com1password-site-verification=Q5HRB2HRUVEKPKLPUYSHPY7TVU
cox.comadobe-idp-site-verification=3a34ac7a8c31e19289e987c5291978339f484d0ab15bb1e04246f349166500dd
cox.com1password-site-verification=IEGMFFQW3VAMXJ6NZWYJWVNVPI
cox.comv=msv1 t=1A155616-9012-4BF3-AEA1-31E76F79E812
cox.compardot_340601_*=b0719eab62510bff552b688ea671dbde0515aeb67d525344fa1d34e2cfc56c51
cox.comamazonses:PWgG2G3N32fHgHnJ5gScHORODG7ECdUIKTE7mj+13nc=
cox.compardot340601=c53160c663795dd500364ee21052811899b9ebdd8cb9f63f30f3d146c3538ee6
cox.comwebexdomainverification.FJM6=be5f625b-a357-41f1-8fd7-fe497011980e
cox.comwebexdomainverification.=c03bc5ff-3e9c-4b50-915b-382f9d07133b
cox.comjamf-site-verification=joOosvPwwEmZ_JV6HhcC3g
cox.com_8l2qjhah03uhsgsusqcn3fxwnthj15x
cox.comonetrust-domain-verification=61c560f3c5034683b16c83fbb22138b7
cox.combold-verification: BUoe7mlIUji6SQU
cox.comjamf-site-verification=mqrYF23_YSCrqqLxzWNZKA
cox.comgoogle-site-verification=5avliMKxh_MUyAteLmFW9gV9wgytyi1LHUnzTkAJVX8
cox.comanthropic-domain-verification-p23c76=Vj4gpCwGgYTWf73a5NWYnava4
cox.comv=spf1 include:%{d}.7b.spf-protect.agari.com exists:%{i}._i.%{d}._d.espf.agari.com ~all
cox.compaloaltonetworks-site-verification=09b162682bf108246522568a5160b4617771dd906103cbf8ed622bb9a3b50504
cox.comgoogle-site-verification=yd_9m1USTBo5RNlsPA2JXBqdw5QsbT5thDhNryh5Zns
cox.com_2yzgjbniu8g8z6xsyl23zrjnxjp8cau
_dmarc.cox.comv=DMARC1; p=reject; sp=none; fo=1; ri=3600; rua=mailto:[email protected]; ruf=mailto:[email protected]
selector2._domainkey.cox.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQChwN7pcFxRrkKlVWzf0kQHF+BnKS2Wj9ohCWJUb44Ra9I/h0yj8iQWQlJWvfZjWv3KAYNkjyuw0m3rqeOKE9MZ3wtqsflOOOnSoA+PvO4y3GqTwygkJ1DDiojkBijsSNa/qsbwyIDB5D3pNse5k7NdNV62E9JvQFWL7dZp7cYT0wIDAQAB;
mandrill._domainkey.cox.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey.cox.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr3az7ru/VhwU+rTMal5AG0jfOCpaEVHfiVTkO2U/l0fE16U/tyL4obOv8o/n/HwsKwEpwkIt5UtG25MKX26/lUd5TMo7ltRzk/OU4kI+CR9rK00EW3JbD9ZxDj+lvycgJUyNfsB8QeAhZB9GG9zHu4jLSOgqVFihqY9dPUx+BskgwPsc9lH6u0vBXv1DNG2XYLhaaSRZwnajbXNOSwN43EkbGWoVfgsG7g8QQxgv3zfFm6oEv+dQDiNkC6gOyPzKQHPEZ4ioJ18lqauyyW55kpq2Gd/E1ZBTNNTDfdxa6JHS7keU136974MG9Ol/QOoDHDNH6CFCJgKwUbPGyhgWrwIDAQAB
s2._domainkey.cox.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7O5ek89keLm7nVdY+Xk3f8593nCasxMaXWiLn04QzYFJE2kJdn4hTduiJJpDxyF0tjENrVeIJMKGssf73Rs3NA2zBivl7riPzA6C0DUYe7hQA2A51kXpofAhHiqwrgFkbf3qtA3fgXnO3v+w/RsgybF0g8fdkSJChoI+MaV3lv6Om5xBcWiiXl1isDE1hX6nBJf8LBEQzjpcVuIBUVvxtkStmOjZ0G8stgcauj/KFEeFCVYRwkQaqZ35sWlei9E+jEW7YQ+Q+50R9b1hbF/BqMtYBRnDQMnGyItsy8TnhRWen1enAli3yXK8EyEeQ0VK40dh62rqSxJMaf6oBvodAwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
45.60.45.167Website45.60.45.0/24
45.60.49.167Website45.60.49.0/24
98.163.68.36Name server ns.cox.net98.163.68.0/24
98.163.68.52Name server ns.west.cox.net98.163.68.0/24
98.163.68.37Name server ns.east.cox.net98.163.68.0/24
52.101.42.16Mail server cox-com.mail.protection.outlook.com52.101.42.0/24

WHOIS of the domain cox.com

Domain Name: COX.COM
   Registry Domain ID: 2096_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-02-03T06:09:44Z
   Creation Date: 1995-03-23T05:00:00Z
   Registry Expiry Date: 2027-02-07T14:42:01Z
   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: NS.COX.NET
   Name Server: NS.EAST.COX.NET
   Name Server: NS.WEST.COX.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T16:19: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.