Dataweaz

babelcarp.org

Summary

Registrar
pair Networks, Inc. d/b/a pair Domains
Status
clientTransferProhibited
Created on
July 29, 2011
Expires on
July 29, 2027
Name servers
ns2.access.net, ns1.access.net
Mail servers
custmx.panix.com
DKIM
No key found among the common selectors

Authorized senders (SPF)

Neutral

The record gives no instruction for other servers.

SPF lists the servers allowed to send e-mails for babelcarp.org.

RuleValueResult
includecustspf.panix.comAllowed
all—Neutral

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:custspf.panix.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 babelcarp.org arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from babelcarp.org 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 @babelcarp.org 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

babelcarp.org  MX  10 mx1.babelcarp.org.
babelcarp.org  MX  20 mx2.babelcarp.org.

What the record contains

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

babelcarp.org  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.babelcarp.org, 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.babelcarp.org  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.babelcarp.org, 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.babelcarp.org  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 babelcarp.org

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.

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
ns2.access.net198.7.0.2
ns1.access.net198.7.0.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @babelcarp.org 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
150custmx.panix.com166.84.1.73

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.babelcarp.org.

NameContent
babelcarp.orgv=spf1 include:custspf.panix.com ?all

Related IP addresses

IPv4 addresses used by babelcarp.org: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
166.84.62.251Website166.84.62.0/24
166.84.62.123Website166.84.62.0/24
198.7.0.2Name server ns2.access.net198.7.0.0/24
198.7.0.1Name server ns1.access.net198.7.0.0/24
166.84.1.73Mail server custmx.panix.com166.84.1.0/24

WHOIS of the domain babelcarp.org

Domain Name: babelcarp.org
Registry Domain ID: REDACTED
Registrar WHOIS Server: whois.pairdomains.com
Registrar URL: https://whois.pairdomains.com
Updated Date: 2026-08-11T23:28:01Z
Creation Date: 2011-07-29T01:26:29Z
Registry Expiry Date: 2027-07-29T01:26:29Z
Registrar: pair Networks, Inc. d/b/a pair Domains
Registrar IANA ID: 99
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4123815195
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns1.access.net
Name Server: ns2.access.net
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-02T21:48:20Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.  The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

    Domain Name: babelcarp.org
    Registry Domain ID: 2060fa285c1c452397372fa89fcb6d43-LROR
    Registrar WHOIS Server: pairdomains.com
    Registrar URL: pairdomains.com
    Updated Date: 2026-06-26T17:32:01+0000Z
    Creation Date: 2011-07-29T01:26:29+0000Z
    Registrar Registration Expiration Date: 2027-07-29T01:26:29+0000Z
    Registrar: Pair Domains
    Registrar IANA ID: 99
    Registrar Abuse Contact Email: [email protected]
    Registrar Abuse Contact Phone: +1.4123815195
    Domain Status: ok https://icann.org/epp#ok
    Domain Status: clientTransferProhibited
    Registrant Registry ID: GDPR Redacted
    Registrant Name: GDPR Redacted
    Registrant Street: GDPR Redacted
    Registrant Street2: GDPR Redacted
    Registrant City:  GDPR Redacted
    Registrant State/Province: NY
    Registrant Postal Code: GDPR Redacted
    Registrant Country: US
    Registrant Phone: GDPR Redacted
    Registrant Fax: GDPR Redacted
    Registrant Email: https://whois.pairdomains.com/contact?domain=babelcarp.org&type=registrant



    Name Server: NS2.ACCESS.NET
    Name Server: NS1.ACCESS.NET
    DNSSEC: unsigned
    URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
    >>> Last update of WHOIS database: 2026-10-02T21:48:21+0000Z <<<


NOTICE AND TERMS OF USE: 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: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone, or
facsimile of mass, unsolicited, commercial advertising or solicitations; or (b)
enable high volume, automated, electronic processes that send queries or data
to the systems of any Registry Operator or ICANN-Accredited registrar, except
as reasonably necessary to register domain names or modify existing
registrations. Pair Networks reserves all rights and remedies it now has or may have
in the future, including, but not limited to, the right to terminate your
access to the WHOIS database in its sole discretion, for any violations by you
of these terms of use, including without limitation, for excessive querying of
the WHOIS database or for failure to otherwise abide by these terms of use.
Pair Networks reserves the right to modify these terms at any time.

** Register Now at http://www.PairDomains.com/ **

% Query time: 1745 msec
% WHEN: Fri Oct 02 21:48:20 UTC 2026