Dataweaz

rcn.net

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
May 2, 1995
Expires on
May 3, 2027
Name servers
auth1.dns.rcn.net, auth3.dns.rcn.net, auth2.dns.rcn.net, auth4.dns.rcn.net
Mail servers
rcn-net.mail.protection.outlook.com
SPF
Soft
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

DMARC tells mail servers what to do with an e-mail that claims to come from rcn.net but fails SPF and DKIM checks.

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

Record

v=DMARC1;p=quarantine;sp=none;pct=100;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 rcn.net.

RuleValueResult
ip4207.172.159.1Allowed
ip4207.172.4.0/24Allowed
ip4207.172.157.0/24Allowed
ip4208.58.56.0/24Allowed
ip4198.183.9.0/24Allowed
ip474.205.21.242Allowed
ip4130.250.130.230Allowed
ip4146.115.106.224/27Allowed
ip466.235.59.86Allowed
ip62610:80::/29Allowed
ip4208.58.242.106Allowed
ip4208.58.242.107Allowed
include_spf.google.comAllowed
include_spf.brainier.comAllowed
includespf.protection.outlook.comAllowed
all—Suspicious

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 ip4:207.172.159.1 ip4:207.172.4.0/24 ip4:207.172.157.0/24 ip4:208.58.56.0/24 ip4:198.183.9.0/24 ip4:74.205.21.242 ip4:130.250.130.230 ip4:146.115.106.224/27 ip4:66.235.59.86 ip6:2610:80::/29 ip4:208.58.242.106 ip4:208.58.242.107 include:_spf.google.com include:_spf.brainier.com include:spf.protection.outlook.com ~all

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

rcn.net  MX  10 mx1.rcn.net.
rcn.net  MX  20 mx2.rcn.net.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.rcn.net.
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

rcn.net  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.rcn.net, 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.rcn.net  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.rcn.net, 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.rcn.net  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 rcn.net

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
A207.172.16.156

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
auth1.dns.rcn.net66.44.1.44
auth3.dns.rcn.net207.96.3.153
auth2.dns.rcn.net207.237.14.120
auth4.dns.rcn.net207.172.3.22

Mail servers (MX)

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

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.rcn.net.

NameContent
rcn.netsqrnh03865easdhfecs36dd7rc
rcn.netatb52h5ovp80lp46stnduemnjt
rcn.netsmartsheet-site-validation=h1gcp3Io_xB6AatpP611JWVbybfGDC8y
rcn.nethtfj5a6b3cg3arbs7ooq7cub91
rcn.netsFEX/C9HCBaiZu/OIBYdh121+ 8ZbFHEGKdgujLjXuAk=
rcn.netv=spf1 ip4:207.172.159.1 ip4:207.172.4.0/24 ip4:207.172.157.0/24 ip4:208.58.56.0/24 ip4:198.183.9.0/24 ip4:74.205.21.242 ip4:130.250.130.230 ip4:146.115.106.224/27 ip4:66.235.59.86 ip6:2610:80::/29 ip4:208.58.242.106 ip4:208.58.242.107 include:_spf.google.com include:_spf.brainier.com include:spf.protection.outlook.com ~all
rcn.net4fdverpd2u7sjngf44apf389ps
rcn.neta42ofon7g25u3f1fvsqa0f02do
rcn.netvqloi8gt2iuq1h6im4nv0f0gfo
rcn.netgtq3t4u4oqo90c9pdded0392n6
rcn.netki57vo31fsk9458nafqc3vv230
rcn.netgoogle-site-verification=k0_lxzLLxBNuEnwUJQu3eJA83-6C0EZC9-OB7O0WmQE
rcn.net46tv82crv6ejktv6ikufiu2100
rcn.netao2nnuo3d1lo76aep2m6kv7ci5
rcn.netgoogle-site-verification=vndJz4k9oR9MSCK5pPHGESVxkvd4mpJ86wwplPOAP6I
rcn.netMS=ms71022474
rcn.netgtq3t4u4oqo90c9pdded0392n6.
rcn.netccvsq88mj3be4rr200nji1gpuc
_dmarc.rcn.netv=DMARC1;p=quarantine;sp=none;pct=100;fo=1;rua=mailto:[email protected];ruf=mailto:[email protected]

Related IP addresses

IPv4 addresses used by rcn.net: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
207.172.16.156Website207.172.16.0/24
66.44.1.44Name server auth1.dns.rcn.net66.44.1.0/24
207.96.3.153Name server auth3.dns.rcn.net207.96.3.0/24
207.237.14.120Name server auth2.dns.rcn.net207.237.14.0/24
207.172.3.22Name server auth4.dns.rcn.net207.172.3.0/24
52.101.41.122Mail server rcn-net.mail.protection.outlook.com52.101.41.0/24
207.172.159.1Authorized by SPF207.172.159.0/24
74.205.21.242Authorized by SPF74.205.21.0/24
130.250.130.230Authorized by SPF130.250.130.0/24
66.235.59.86Authorized by SPF66.235.59.0/24
208.58.242.106Authorized by SPF208.58.242.0/24
208.58.242.107Authorized by SPF208.58.242.0/24

WHOIS of the domain rcn.net

Domain Name: RCN.NET
   Registry Domain ID: 2916220_DOMAIN_NET-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2025-01-13T02:58:03Z
   Creation Date: 1995-05-02T04:00:00Z
   Registry Expiry Date: 2027-05-03T04:00:00Z
   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: AUTH1.DNS.RCN.NET
   Name Server: AUTH2.DNS.RCN.NET
   Name Server: AUTH3.DNS.RCN.NET
   Name Server: AUTH4.DNS.RCN.NET
   DNSSEC: signedDelegation
   DNSSEC DS Data: 48620 8 2 7161E6AE5AE14E7A79CFF4730E7F3BE78F2FCC0BFF36195311C02BBBA90D6560
   DNSSEC DS Data: 59278 13 2 1EBB896D7D956E7BA34626F1A9F84D576B7908BF116879EFC70F55B6E0379380
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T01:31: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.