Dataweaz

enbridge.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
September 23, 1998
Expires on
September 22, 2028
Name servers
blue.foundationdns.net, blue.foundationdns.com, blue.foundationdns.org
Mail servers
mxb-001f4f02.gslb.pphosted.com, mxa-001f4f02.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 enbridge.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 enbridge.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 enbridge.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive
default—RSA 1024 bits · shortActive
dkim—RSA 1024 bits · shortActive

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

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

enbridge.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.enbridge.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.enbridge.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.enbridge.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.enbridge.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 enbridge.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
A150.171.110.117
AAAA2603:1061:14:6a::1

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
blue.foundationdns.net162.159.60.31
blue.foundationdns.com162.159.60.1
blue.foundationdns.org172.64.40.61

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @enbridge.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
0mxb-001f4f02.gslb.pphosted.com205.220.182.187
0mxa-001f4f02.gslb.pphosted.com205.220.170.187

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

NameContent
enbridge.com6ca610ddf17842939724882ff5b1038d
enbridge.comDynatrace-site-verification=48e44240-6408-4f98-b0b5-c54a4d3d2746__nt9totgoq9t8q99jpoj7nbopkd
enbridge.comapple-domain-verification=ilLzL1rxKvv4Gqbe
enbridge.comfacebook-domain-verification=cvp1231dztjhtqgdwsn69z14vq4br0
enbridge.comMS=ms49130958
enbridge.comadobe-idp-site-verification=847a64d9e346b89598f22e71f20639b63d240d9e0e098cba2bdb6a7bbe718bbd
enbridge.comXmedius-Verification=543bb6a56fe83b69d1975b979218603f6e3ff55b347e7a8c232193948cf261ea
enbridge.comdocusign=4ebaebdb-60f2-447c-b026-cde50d05c026
enbridge.comgoogle-site-verification=xIY97ilzRHjEKbggEecMHwovX-ZZfr2r9qhGOoU7Ssk
enbridge.comfigma-domain-verification=753c8e89bf741e504dea3c993b016d89b265a7b3cc40f8815efe51188137333a-1761234814
enbridge.comcisco-ci-domain-verification=20d0f3e64dfa61051792c2faf6fc7f8fbc30e0cb11ccbcf6036b09e94148e62b
enbridge.comDynatrace-site-verification=e5370cc8-4b66-4a31-add2-e4c5397e9ad1__kda1rm67go4rgvsa5v8hb7uhlp
enbridge.compendo-domain-verification=4e5d0c6f-6f68-48c1-89db-5d335c6f13b7
enbridge.comckh26RfkNGrfMAvYqGeiuC9A6xtmPh88mUVYez3mNKZTQaHXQOHE+q56qIM2Duyki8c8RxuuVhEfrCyV3zGpDQ==
enbridge.comgoogle-site-verification=kpwF7-EM65xxLgAY9BGKskzEd7P7V7Di5opMmn3r2Zw
enbridge.comdocusign=075174c7-e92c-46d6-955b-0e195d0d2cab
enbridge.comadobe-sign-verification=e5864ab952b853ec877f71dc97d899f
enbridge.compaloaltonetworks-site-verification=288e0650e6fee330ab08439efc64556d4c100913d33a54dfa2af7f688681f2f9
enbridge.comdocker-verification=a58e584e-b3f6-4149-9a75-d7f636fb6567
enbridge.comv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
enbridge.com64a4c7342e8444b1bb9e5e52fcda55ef
enbridge.comoati-domain-verification=5F3C1A2D1E05D51BAABA9E73884272CB1D1A708B33FF4269E0DCA1D7DA54DC23
enbridge.comadobe-sign-verification=7a19b8eb4ef42d2f194791ca7fad62
enbridge.comgoogle-site-verification=wmJY7p1K2Rc2RcPBmzzCNnLlgtrPDCondYhyq6gVyjs
_dmarc.enbridge.comv=DMARC1; p=reject; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected]
k2._domainkey.enbridge.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.enbridge.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s1._domainkey.enbridge.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA10onRtcr4fuQkEGZIv4Z4PtVzt6YMERqtRmQLt/Zk4xDwtkQp1vbkaeJx2mPi578GaZILVTE90azyu3tgFo0R5T2muGU1tireJf3fJmWr/HYaNwmMsQFd0vCVmmtzvKke0szIbI+KcbPmT0Q1KdcgcJImrsLpvab6ksntinSNqjB4gXt9zebCBlVpc7pw/63pWU+qxbNNEi64WueKS7xQlqUA5BfQEWMG62AIYCjH2SaBWq1VFtc/Pf3kSd8T47alkUgRHy8XnxkosBFfG10lmpjEA9YvgXQEh6+IrhUxQmiNb6KdDlHgk5FitSSeSWzmNgXebURFg8Jwpmio9eytQIDAQAB
s2._domainkey.enbridge.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyMqoajmV2q5kI7/WoBoEo+Q1zCq8CFrtAC6a56YVYKM8ZapuSvOyk1voB0jpW7zzEbXMNO5G9vbmNtO2E2XLpqgokfDaFGjxkRqGAVAXOMXuChESm3nofv6qbl2jOQOfqbLqApv/yZ7zST1W9/3d86TtsEnnhGs03YzXaQRkm1g2C9815a8HjJEj2PZLinUeZ1o8XSq5bOeP53qlInz79e7m5zvBEhxVdorZfo2i2airtTNenebXdw8a5bDYfpx/9DoOF6JEbOw7Ug5+OxyIcXgFP1eVwS48RB5NOy2EvPX9VJ++j0tBLL5Ugoqy9tIcTLuKebVlCUaFki+6gzWIiQIDAQAB
default._domainkey.enbridge.comv=DKIM1;k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDkgOkfMpaFMVkO/Dn2hQriEFdaMPGacB6cs5XmwcGlRqHpglAfcRjJjyoiqO5VE/d94Zy2W/3AAFDQtS9yZUiYhbTIzVWi3nQ/3gaalcpqJ8iC2iYQYahxPjwaoNwU6dpmuUA30t2u1CL3/I3GdW4Ir6UX0wOnEmWccI8doCSSCQIDAQAB
dkim._domainkey.enbridge.comv=DKIM1;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCf7ogFx+CO40jW1fEZsN6iGCE+7r8Xpqp9DZvqMI/VdTZSVw/OKDj7Q5p7G/L8wI3GVItuFAxLb+eyFGJ3yWCMoNyM+uDfv1kEVIs7FDrfWOxnTKPVtjzalePUVJokDpMH0FAxOB4qNPP2bon+lMzan+YyUyOSzLgK4PMkCLL8UQIDAQAB;

Related IP addresses

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

IP addressUsed for/24 block
150.171.110.117Website150.171.110.0/24
162.159.60.31Name server blue.foundationdns.net162.159.60.0/24
162.159.60.1Name server blue.foundationdns.com162.159.60.0/24
172.64.40.61Name server blue.foundationdns.org172.64.40.0/24
205.220.182.187Mail server mxb-001f4f02.gslb.pphosted.com205.220.182.0/24
205.220.170.187Mail server mxa-001f4f02.gslb.pphosted.com205.220.170.0/24

WHOIS of the domain enbridge.com

Domain Name: ENBRIDGE.COM
   Registry Domain ID: 2079647_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2026-08-21T10:04:48Z
   Creation Date: 1998-09-23T04:00:00Z
   Registry Expiry Date: 2028-09-22T04:00:00Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   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: BLUE.FOUNDATIONDNS.COM
   Name Server: BLUE.FOUNDATIONDNS.NET
   Name Server: BLUE.FOUNDATIONDNS.ORG
   DNSSEC: signedDelegation
   DNSSEC DS Data: 2371 13 2 6D821835B5333528D28FBCEF43E4BFF79EF43E2FA0EF1CB9DA25C2749EDEF8F7
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T14:38:58Z <<<

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.