Dataweaz

bloomberg.net

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
March 8, 1997
Expires on
March 9, 2027
Name servers
pdns1.ultradns.net, dns4.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, pdns3.ultradns.org, pdns5.ultradns.info, dns1.p01.nsone.net
Mail servers
mx3b.igslb.bloomberg.net, mx3c.igslb.bloomberg.net, mx4c.igslb.bloomberg.net, mx4a.igslb.bloomberg.net, mx4b.igslb.bloomberg.net, mx3a.igslb.bloomberg.net, mx2a.igslb.bloomberg.net, mx4d.igslb.bloomberg.net
DMARC
Reject
DKIM
No key found among the common selectors

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 bloomberg.net 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; adkim=r; aspf=r; ruf=mailto:[email protected]; fo=1; rua=mailto:[email protected]

Authorized senders (SPF)

Delegated

The policy is defined by the domain _spf.main.dmarc-bloomberg.com (redirect).

SPF lists the servers allowed to send e-mails for bloomberg.net.

RuleValueResult
redirect_spf.main.dmarc-bloomberg.com—

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 redirect=_spf.main.dmarc-bloomberg.com

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

bloomberg.net  MX  10 mx1.bloomberg.net.
bloomberg.net  MX  20 mx2.bloomberg.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.bloomberg.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

bloomberg.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.bloomberg.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.bloomberg.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.bloomberg.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.bloomberg.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 bloomberg.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.

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
pdns1.ultradns.net204.74.108.1
dns4.p01.nsone.net198.51.45.65
dns2.p01.nsone.net198.51.45.1
dns3.p01.nsone.net198.51.44.65
pdns3.ultradns.org199.7.68.1
pdns5.ultradns.info204.74.114.1
dns1.p01.nsone.net198.51.44.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @bloomberg.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
0mx3b.igslb.bloomberg.net69.191.192.21
0mx3c.igslb.bloomberg.net69.191.192.122
0mx4c.igslb.bloomberg.net69.191.192.168
0mx4a.igslb.bloomberg.net69.191.192.142
0mx4b.igslb.bloomberg.net69.191.192.167
0mx3a.igslb.bloomberg.net69.191.244.24
0mx2a.igslb.bloomberg.net69.191.244.206
0mx4d.igslb.bloomberg.net69.191.244.35

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

NameContent
bloomberg.netMS=ms52253197
bloomberg.netdocusign=0ab30edc-33e5-46d9-8b03-7fb1c776b908
bloomberg.netDirectFedAuthUrl=https://bssobeta.blpprofessional.com/idp/SSO.saml2
bloomberg.netasv=37428241661a5d47504db9b6a7641607
bloomberg.netbluebeam-verification=osghffhpims2uzv9ew5cizeq06xb4x
bloomberg.netstripe-verification=5ad236f66979d90b1770ee17bd480808cbad415c6206d7a6d24d3767d3f018ef
bloomberg.netgoogle-site-verification=XCaCc-Gdo4jXVwIR9Coc3wtI2xI1WZN1Wmo4fcCMOxQ
bloomberg.net00D4W000002UARg=1TBaZ0000000K8P
bloomberg.netduo_sso_verification=7ftMcGSeP4E2JJ7yqvEcAULgRUGaHn8Nslrw0UA9t8Np9O37IsbsbXtlcG2W9b3E
bloomberg.netmiro-verification=0b70e4fe3ab6620216f250a8680479af9d93a128
bloomberg.netMS=ms76872452
bloomberg.netcisco-ci-domain-verification=620a8920edea896e42c74e4e7501bbb46f62d0e5927d24b777ac8f3d9e0d072b
bloomberg.netjamf-site-verification=cwV36tJ5lz537qzmBasmHg
bloomberg.netflexera-domain-verification-vakdmfbmhpmkvopf
bloomberg.netyahoo-verification-key=3WXBd1Kl/9o66jj2v4Zx5hzL3Dtz9qUW+6EsugZDiq0=
bloomberg.netatlassian-domain-verification=gK9LJEftkavNAe/keDgXDWOhGwUV02GQTz9BbfKLplkTTtpciOH5eL1W6u7BRfVR
bloomberg.neta01f679b-6acf-464b-a852-7a8431337fee
bloomberg.netparallels-domain-verification=47460854911b478da11221dc20e8cc0340a92adf1e6b4ff08a5e941f5379c267
bloomberg.netextensis-domain-verification=707df5b4-0868-499f-af75-51718e082698
bloomberg.netZOOM_verify_rl-mcFScS8W6864E30mlZg
bloomberg.netanthropic-domain-verification-4en7bq=UBdA5SfLIzrRI2wUzWIgAQgt9
bloomberg.netslack-domain-verification=I1M2KKVDnker5VBVARalcRKSWefZ8sgDhAfe31Fr
bloomberg.netairtable-verification=15d4376d6d99cc906abbcb295b4245da
bloomberg.netdocusign=2b3e6c43-c369-4603-83a6-46333bd0e3ad
bloomberg.netstripe-verification=5b9397a063b64cf8214e14b6f949b7c87ba98278a72649a6acf5bc125e31dc84
bloomberg.netv=spf1 redirect=_spf.main.dmarc-bloomberg.com
bloomberg.netcanva-site-verification=7OjKWUEXYiW1iOPJ_-ydOg
bloomberg.netMS=770DC9D08640DFEA8B4F936EEDFA7EF315D3A5A3
bloomberg.netms76872452.msv1.invalid
_dmarc.bloomberg.netv=DMARC1; p=reject; adkim=r; aspf=r; ruf=mailto:[email protected]; fo=1; rua=mailto:[email protected]

Related IP addresses

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

IP addressUsed for/24 block
15.197.146.156Website15.197.146.0/24
3.33.146.110Website3.33.146.0/24
204.74.108.1Name server pdns1.ultradns.net204.74.108.0/24
198.51.45.65Name server dns4.p01.nsone.net198.51.45.0/24
198.51.45.1Name server dns2.p01.nsone.net198.51.45.0/24
198.51.44.65Name server dns3.p01.nsone.net198.51.44.0/24
199.7.68.1Name server pdns3.ultradns.org199.7.68.0/24
204.74.114.1Name server pdns5.ultradns.info204.74.114.0/24
198.51.44.1Name server dns1.p01.nsone.net198.51.44.0/24
69.191.192.21Mail server mx3b.igslb.bloomberg.net69.191.192.0/24
69.191.192.122Mail server mx3c.igslb.bloomberg.net69.191.192.0/24
69.191.192.168Mail server mx4c.igslb.bloomberg.net69.191.192.0/24
69.191.192.142Mail server mx4a.igslb.bloomberg.net69.191.192.0/24
69.191.192.167Mail server mx4b.igslb.bloomberg.net69.191.192.0/24
69.191.244.24Mail server mx3a.igslb.bloomberg.net69.191.244.0/24
69.191.244.206Mail server mx2a.igslb.bloomberg.net69.191.244.0/24
69.191.244.35Mail server mx4d.igslb.bloomberg.net69.191.244.0/24

WHOIS of the domain bloomberg.net

Domain Name: BLOOMBERG.NET
   Registry Domain ID: 318433_DOMAIN_NET-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-03-05T06:03:49Z
   Creation Date: 1997-03-08T05:00:00Z
   Registry Expiry Date: 2027-03-09T04: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: DNS1.P01.NSONE.NET
   Name Server: DNS2.P01.NSONE.NET
   Name Server: DNS3.P01.NSONE.NET
   Name Server: DNS4.P01.NSONE.NET
   Name Server: PDNS1.ULTRADNS.NET
   Name Server: PDNS3.ULTRADNS.ORG
   Name Server: PDNS5.ULTRADNS.INFO
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T03:14: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.