Dataweaz

rws.com

Summary

Registrar
Nom-iq Ltd. dba COM LAUDE
Status
clientDeleteProhibited
Created on
November 12, 1997
Expires on
November 11, 2031
Name servers
cruz.ns.cloudflare.com, david.ns.cloudflare.com
Mail servers
mxb-003f9603.gslb.pphosted.com, mxa-003f9603.gslb.pphosted.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 rws.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 rws.com.

RuleValueResult
include%{ir}.%{v}.%{d}.spf.has.pphosted.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all

E-mail signing (DKIM)

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

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

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

rws.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.rws.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.rws.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.rws.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.rws.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 rws.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
A172.67.74.40
A104.26.14.182
A104.26.15.182
AAAA2606:4700:20::681a:fb6
AAAA2606:4700:20::681a:eb6
AAAA2606:4700:20::ac43:4a28

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
cruz.ns.cloudflare.com172.64.32.88
david.ns.cloudflare.com173.245.59.152

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @rws.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
10mxb-003f9603.gslb.pphosted.com66.159.246.22
10mxa-003f9603.gslb.pphosted.com66.159.235.148

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

NameContent
rws.comOSSRH-79744
rws.comatlassian-domain-verification=CU05b01LwQ8dwEuC5YbuyYjP6FcrbcnbafXIjwlJIWSqPL6Oa2dwMBc8agWAYi8r
rws.compardot27822=6736d859f5cf3b9f50c74e3ffa4af558dbd4ba5ff9a2e7a2052f85b772d5b92a
rws.comatlassian-sending-domain-verification=32e71104-69a0-4263-9a09-3be3b47532d8
rws.comgoogle-site-verification=i0Kg8Dhl23iKYdlmnQEoZc5jvft4x5HVDlxTnVe72iE
rws.comadobe-idp-site-verification=1434f114bdfe5de16f6950bdb184457e23610ae15c4ac6c9c695de033dc81f41
rws.comapple-domain-verification=JpAM6sQfEuFP71J1
rws.comgoogle-site-verification=XSvO0uTsAJZtKCu2tziK9xoyppPpkEkod2ivRCZkqIQ
rws.comSv0s2hss1a61mN4P5IgQUdVJxGB2RqkWQ37RCloJX65kYK5hNf5VFzn6Y4EgkWrj7+YxeMHvSorDhlFvp3IFbA==
rws.comv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
rws.comMS=ms15315374
rws.comDynatrace-site-verification=2731af7e-187d-47a9-8c04-e3e99a7e147d__8lo7r51qnlfdoa569i8j9qls1a
rws.comcanva-site-verification=gq7hDoAIF0AcqT0wuxFO8A
rws.com_cx2tr5swvcts52zyvghqwjqs2ig1q89
rws.combrevo-code:e8fcf6f26590121a2371f48c9290ac52
rws.comgvUg+klL+C4SKMfLdt1dq9eDp8zSmuoenokeIABJ8kw=
rws.comMS=ms66981383
rws.comcursor-domain-verification-yt4zjt=KuNpuIhl5RKwZwyYBHOMeyDX2
rws.commiro-verification=5c89b6997eaa6bd21d3ac18cda0ff0c0eaa79716
rws.comanthropic-domain-verification-nbm5bz=womL45EnR7ldXYlcw5zxAe1nF
rws.comamazonses:PFC66pP+RI26XAZ5sJ0VG4G53R+c9di83nzvIMrO2as=
rws.comK1wKg3M8zmSV6Th6xLk4
rws.comms-domain-verification=2a0aec95-3ec3-4845-9947-99386fcaf2f0
rws.com9Y6DWN4S1PU1IRXXHU3GYQ8KF0ZPFGZ6GEZL4NGP
rws.com_g7dj57wxjwnnz4a3my3axg3tqfqsdaw
rws.comteamviewer-sso-verification=b5b8b33414af4b9393a2c90db5f438fb
_dmarc.rws.comv=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]
selector1._domainkey.rws.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnSRnJTmB5UNuBr/MLYQXiLPaW0vHRt2RqCAFcIsy3kG0TQCKRgDUdzFQNz002Cib4zR87//DOMFfHlzcGUc37Sbi1YgH8gfBug3CJ5I88b4rTTFwWb7tab+300f29orOkX3Vo2+kk6g52kmtP5bhkAGMYiNZ1s6K2vxWND4NMuNs+sDo4Mjym6JLn9+rayPGLzfiohKu3eHAXmc3tmy8SUB45LBdCtyIJYjfcqzWC+H6pCdBPLz/ucssgrjL/Ec+oEshvBWHw3jEcFGQfBuks0NS/ybMEacQ5SeQkmIlOB14ZxoytDle2N++S2C4O+MIPj5+/+cYHMZvAZoi7D+6/QIDAQAB;
k2._domainkey.rws.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.rws.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.rws.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3s0lZcGFpVS6+RxmXL39GabObDSFVm1TXSmovLE4WR+SdyRVqqxAjGarZ/bWbTMc81xP8Mgr6IsB7YI1uoB5H9kN+EqLTmxwc8UtBHMa72/7oreed1Nb5qcPQcDtMSPbQ8khHoBWyI+hs/AYjIkKmApfPuJCcdBCRPHxDtWIo0RhovRqIUJyxAByqrwX8BPmkmgJqdrsMHYPOGaxru7M55JnADDLU9B2D7SFJIs6ZEMywz/owqRsvCYP4nhMHhBvkVW9MpvWa7bP1WhxDr9FxYSLmviJ6mm7zymmGb0H+pS/bwqehTOy0/JFWyX+K4MDSGG2MkHyfWCtqNJ5c2Rg7wIDAQAB
s2._domainkey.rws.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDfP8eNlPBM2GTtMBbcObkdfuDuEySTJmAdGIXfHYk7r2q3n4GCJv2i/4WaSrdm0v+QI+bWaiHX+LykXWay1+9W1UWhykoApEkB2wfnm8EzwF6vMNb+qzJW62U66ybu3wzCkRwK6vzh45n5eTZlv0vnWVsRmS/RdGPfL3jkXvi8IwIDAQAB
zendesk1._domainkey.rws.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.rws.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
172.67.74.40Website172.67.74.0/24
104.26.14.182Website104.26.14.0/24
104.26.15.182Website104.26.15.0/24
172.64.32.88Name server cruz.ns.cloudflare.com172.64.32.0/24
173.245.59.152Name server david.ns.cloudflare.com173.245.59.0/24
66.159.246.22Mail server mxb-003f9603.gslb.pphosted.com66.159.246.0/24
66.159.235.148Mail server mxa-003f9603.gslb.pphosted.com66.159.235.0/24

WHOIS of the domain rws.com

Domain Name: RWS.COM
   Registry Domain ID: 2127934_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.comlaude.com
   Registrar URL: http://www.comlaude.com
   Updated Date: 2025-04-18T16:46:35Z
   Creation Date: 1997-11-12T05:00:00Z
   Registry Expiry Date: 2031-11-11T05:00:00Z
   Registrar: Nom-iq Ltd. dba COM LAUDE
   Registrar IANA ID: 470
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +442074218250
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: CRUZ.NS.CLOUDFLARE.COM
   Name Server: DAVID.NS.CLOUDFLARE.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T11:02: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.