Dataweaz

credence.tech

Summary

Registrar
GoDaddy.com, LLC
Status
clientRenewProhibited
Created on
November 13, 2018
Expires on
November 14, 2027
Name servers
cbj6dnsv601.tm.com.my, brf08dnsv601.tm.com.my
Mail servers
credence-tech.mail.protection.outlook.com

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

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

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

Record

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for credence.tech.

RuleValueResult
mx—Allowed
a—Allowed
ip4202.188.145.11/32Allowed
ip4202.188.145.12/32Allowed
ip458.27.122.11/32Allowed
ip458.27.122.12/32Allowed
includeaspmx.pardot.comAllowed
includespf.protection.outlook.comAllowed
all—Rejected

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 mx a ip4:202.188.145.11/32 ip4:202.188.145.12/32 ip4:58.27.122.11/32 ip4:58.27.122.12/32 include:aspmx.pardot.com include:spf.protection.outlook.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive

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

credence.tech  MX  10 mx1.credence.tech.
credence.tech  MX  20 mx2.credence.tech.

What the record contains

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

credence.tech  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.credence.tech, 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.credence.tech  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.credence.tech, 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.credence.tech  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 credence.tech

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
A192.0.78.239
A192.0.78.190

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
cbj6dnsv601.tm.com.my202.188.134.137
brf08dnsv601.tm.com.my202.188.146.25

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @credence.tech 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
0credence-tech.mail.protection.outlook.com52.101.137.2

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.credence.tech.

NameContent
credence.tech_globalsign-domain-verification=dZoL3E9cSLh6WnbYyA_mTMoriDbi2ARakvXh3Hcv1k
credence.techv=spf1 mx a ip4:202.188.145.11/32 ip4:202.188.145.12/32 ip4:58.27.122.11/32 ip4:58.27.122.12/32 include:aspmx.pardot.com include:spf.protection.outlook.com -all
credence.tech_globalsign-domain-verification=CQG_FWjS3fwpwlzamSyAZYX0N_ciTgPbCu-EBuC536
credence.techpardot1002681=1ca8063e85c65aceac5fbf400f3b5137b311d0f11710328dea0284a6f8913d0b
credence.techglobalsign-domain-verification=C6F6F11242902A85B78A471113DFB28E
credence.techbkajbdqn61em4hpfvbbvgdhluq
credence.techMS=ms53489305
credence.techrovag_verification_token=765F6043136A42FCA59F2CDC58D58D79
credence.techVDk3nVK1LcgMto3yattMgH/cyzFoar3CXlOdpz3PyNw=
credence.techglobalsign-domain-verification=97A15CDF98D368EDF26FBCBA6DD3CE53
_dmarc.credence.techv=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]
selector1._domainkey.credence.techv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzKFqUxI1wyl7QuCuiNkx48RsieonwlR0KjjZpkILHz7GdjpbDjUbgqkMlGxuMILslagpZ73saiWJAEyzOWz29rvGoaQkjV63/dO3+V6M1+15ExReLDi49bVKILSTFfO/D8FIdXc2bvld53wU6Ipd2Nxd3q3dBrRjQWvs4mrKQjo/aouqX/VCLTF1agZWg6OB1/PVy1PVuL9wkrEzaUQQc8U5yIFvNKZu71nhhu/1VjqSXATRdbFX3no7KmF3ERW4W0joatPDK4hkvbP4hlt/BUt1dktHlgKtOKPCmzz2laSv5dWjfycr59awvbU69/mwNzzwQ+8GeUGPyjvus/P5kQIDAQAB;

Related IP addresses

IPv4 addresses used by credence.tech: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
192.0.78.239Website192.0.78.0/24
192.0.78.190Website192.0.78.0/24
202.188.134.137Name server cbj6dnsv601.tm.com.my202.188.134.0/24
202.188.146.25Name server brf08dnsv601.tm.com.my202.188.146.0/24
52.101.137.2Mail server credence-tech.mail.protection.outlook.com52.101.137.0/24
202.188.145.11Authorized by SPF202.188.145.0/24
202.188.145.12Authorized by SPF202.188.145.0/24
58.27.122.11Authorized by SPF58.27.122.0/24
58.27.122.12Authorized by SPF58.27.122.0/24

WHOIS of the domain credence.tech

Domain Name: credence.tech
Registry Domain ID: D83299839-CNIC
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://godaddy.com
Updated Date: 2026-09-07T06:25:53.794Z
Creation Date: 2018-11-13T15:46:48.000Z
Registry Expiry Date: 2027-11-13T23:59:59.000Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: 
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: brf08dnsv601.tm.com.my
Name Server: cbj6dnsv601.tm.com.my
DNSSEC: unsigned
URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

>>> Last update of WHOIS database: 2026-10-01T18:19:22.581Z <<<

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

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Tucows Registry for informational
purposes only, and it does not guarantee its accuracy. Tucows Registry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Tucows Registry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass  unsolicited, commercial advertising
or solicitations to entities other than your existing  customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Tucows Registry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.
Domain Name: credence.tech
Registry Domain ID: D83299839-CNIC
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2026-09-02T06:24:33Z
Creation Date: 2018-11-13T15:46:48Z
Registrar Registration Expiration Date: 2027-11-13T23:59:59Z
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registry Registrant ID: CR847286790
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Registrant Street: DomainsByProxy.com
Registrant Street: 100 S. Mill Ave, Suite 1600
Registrant City: Tempe
Registrant State/Province: Arizona
Registrant Postal Code: 85281
Registrant Country: US
Registrant Phone: +1.4806242599
Registrant Phone Ext:
Registrant Fax: 
Registrant Fax Ext:
Registrant Email: https://www.godaddy.com/whois/results.aspx?domain=credence.tech&action=contactDomainOwner
Registry Tech ID: CR847286792
Tech Name: Registration Private
Tech Organization: Domains By Proxy, LLC
Tech Street: DomainsByProxy.com
Tech Street: 100 S. Mill Ave, Suite 1600
Tech City: Tempe
Tech State/Province: Arizona
Tech Postal Code: 85281
Tech Country: US
Tech Phone: +1.4806242599
Tech Phone Ext:
Tech Fax: 
Tech Fax Ext:
Tech Email: https://www.godaddy.com/whois/results.aspx?domain=credence.tech&action=contactDomainOwner
Name Server: CBJ6DNSV601.TM.COM.MY
Name Server: BRF08DNSV601.TM.COM.MY
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T18:19:22Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

TERMS OF USE: The data contained in this registrar's Whois database, while believed by the
registrar to be reliable, is provided "as is" with no guarantee or warranties regarding its
accuracy. This information is provided for the sole purpose of assisting you in obtaining
information about domain name registration records. Any use of this data for any other purpose
is expressly forbidden without the prior written permission of this registrar. By submitting
an inquiry, you agree to these terms and limitations of warranty. In particular, you agree not
to use this data to allow, enable, or otherwise support the dissemination or collection of this
data, in part or in its entirety, for any purpose, such as transmission by e-mail, telephone,
postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations
of any kind, including spam. You further agree not to use this data to enable high volume, automated
or robotic electronic processes designed to collect or compile this data for any purpose, including
mining this data for your own personal or commercial purposes. Failure to comply with these terms
may result in termination of access to the Whois database. These terms may be subject to modification
at any time without notice.

**NOTICE** This WHOIS server is being retired. Please use our RDAP service instead.

% Query time: 588 msec
% WHEN: Thu Oct 01 18:19:22 UTC 2026