Dataweaz

techmahindra.com

Summary

Registrar
GoDaddy.com, LLC
Status
clientDeleteProhibited
Created on
December 22, 2005
Expires on
December 22, 2026
Name servers
ns2.techmahindra.com, ns1.techmahindra.com
Mail servers
techmahindra-com.mail.protection.outlook.com
DMARC
Reject

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 techmahindra.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; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1; ri=86400

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for techmahindra.com.

RuleValueResult
mx—Allowed
includespf.protection.outlook.comAllowed
include_spf.google.comAllowed
ab.spf.service-now.comAllowed
ac.spf.service-now.comAllowed
ad.spf.service-now.comAllowed
ip4119.151.8.99/32Allowed
ip4119.151.8.112/31Allowed
ip4203.143.187.82/31Allowed
ip4203.143.187.84/30Allowed
ip4191.41.204.80/29Allowed
ip4103.23.24.78/32Allowed
ip4103.23.26.70/32Allowed
ip4119.151.20.178/32Allowed
ip413.126.171.136/32Allowed
ip4119.151.20.179/32Allowed
ip4129.145.20.114/32Allowed
all—Rejected

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 mx include:spf.protection.outlook.com include:_spf.google.com a:b.spf.service-now.com a:c.spf.service-now.com a:d.spf.service-now.com ip4:119.151.8.99/32 ip4:119.151.8.112/31 ip4:203.143.187.82/31 ip4:203.143.187.84/30 ip4:191.41.204.80/29 ip4:103.23.24.78/32 ip4:103.23.26.70/32 ip4:119.151.20.178/32 ip4:13.126.171.136/32 ip4:119.151.20.179/32 ip4:129.145.20.114/32 -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive
selector2Microsoft 365RSA 2048 bitsActive
s1SendGridRSA 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 techmahindra.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from techmahindra.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 @techmahindra.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

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

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

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.techmahindra.com202.41.204.43
ns1.techmahindra.com203.143.187.45

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @techmahindra.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
5techmahindra-com.mail.protection.outlook.com52.101.144.3

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

NameContent
techmahindra.comduo_sso_verification=fE7QwooS3gEzoDaYrAw6CDGiMPeAsTJGDsaBgh54a1xpvf0hetU6n6UlZ74dmGXc
techmahindra.comv=spf1 mx include:spf.protection.outlook.com include:_spf.google.com a:b.spf.service-now.com a:c.spf.service-now.com a:d.spf.service-now.com ip4:119.151.8.99/32 ip4:119.151.8.112/31 ip4:203.143.187.82/31 ip4:203.143.187.84/30 ip4:191.41.204.80/29 ip4:103.23.24.78/32 ip4:103.23.26.70/32 ip4:119.151.20.178/32 ip4:13.126.171.136/32 ip4:119.151.20.179/32 ip4:129.145.20.114/32 -all
techmahindra.com_2rq3fokmjopqkzp97lazj8o73inhc5h
techmahindra.combox-domain-verification=4ddd0babd72c2c8598291015e44a80212f87ff497acca03e96c5c854bdbbf043
techmahindra.comatlassian-domain-verification=uREf2R/KqrdRvKMu3UkOX0aohbAz/ee/QsYFfVk5Nzbos6vehrYmJfClCKuz1CYF
techmahindra.com_iwdxd3znjvbpor9oxrt7ueu97pre0d3
techmahindra.com_np1dvjpumbffc7c9bhqyldrvqj6qp5u
techmahindra.comatlassian-domain-verification=wBrOFASBvgMlndoPMoLnMXMQ0t0IIHBccg5cHWmjXhAG9EC6iB9ECCaYRauSjrH8
techmahindra.comgoogle-site-verification=3qiu0Ide6c_Gope8k2o9oecD6hKbWmnbjWHc4wp3gMw
techmahindra.comapple-domain-verification=nZJtwjBRd3g62bv7
techmahindra.comjamf-site-verification=RKJ23nlNbYXTomhKfn4kFA
techmahindra.comcisco-ci-domain-verification=43add812b931648ada7b7f1ff1180518ca774678da26842cc0c4522179c9758c
techmahindra.comNqA107OZxFT3GGSumGoeMFxVsIV03sUyQY5H5nbffSc=
techmahindra.comzoho-verification=zb56422924.zmverify.zoho.com
techmahindra.comanthropic-domain-verification-fs80sa=IjQ2HQhdWeSlodlsu18tG17FS
techmahindra.comduo_sso_verification=9YXDYXB3qHsNLubjB8bCEvMhIDy00qsW6uYSdi2pxczlp3MZVAvPwXmzpFFPgZV1
techmahindra.com_p484nemitzl0n6u8w5x9zml2p1a6liq
techmahindra.comcursor-domain-verification-33q7c5=KbVnlwN8S732PGfdhJ5l8kF8L
techmahindra.com_kj6f8plxxbzp0tt0ucj23nxnlbnla8b
techmahindra.comgoogle-site-verification=VpIfniqUnwUwajlc0EOcKUJg54-fFSXps7qyE2J13wI
techmahindra.comvmware-cloud-verification-3f13823e-3431-4b3f-946c-497a80925af0
techmahindra.commou0AlwiUxqJhPjs81cdDSWQ3jsDMRl5Kn8Xe7v3p+y5QoYQbLjW/bQs03KJxVaXKQs/9mlSHCOcXPE6YNifmA==
techmahindra.commongodb-site-verification=tGHKhQ3sT7vJGNoofFBzim544ND2MBuC
techmahindra.comatlassian-domain-verification=ryRbflywjrNYa0Tll0MtSRsnxQYflUjz6L3FUhPSPG9kLiLeNdbBPU5j3IbFiUqx
techmahindra.comwombat-verification=3KwxVCQV1HEp-aRXRTKKaZ5G0frhk
_dmarc.techmahindra.comv=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1; ri=86400
selector1._domainkey.techmahindra.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7FvbKCTySZs8yArYSbxhHSKHDPyHorgkkk86pHp3FnJhbqmJwSYpOYdr3Hhz0ipYXdQfNYBH4R+6zebL9hRqVxqM5UT9L9YEvVRJNkeS28cYZqZPhw0VNir8kXqvVBgAlLtDS01EcjJdj94VcWOAmezCG0dxdoPOvbfDphyBGIcm388UnbEtwB0fvFvm+BHGBCCqucLzZEzyTWBznaHjsHQ/PEKoZ8f7GrfMIPEzefbU1NQWuYPoqOClBjp9bF5rc0aDayp/A/fLvLmNJT4zXn/2heAeIhbrY1JiJMYUJux+9gWKGB1v5l9WcDHWmHSHFb2thmD5HtCp0z+j4PtyqQIDAQAB;
selector2._domainkey.techmahindra.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwmY2E83I25oHIX8HfFeUMLbtd19KIKZ/7AKzXUyS8mCVK+FFHRVseruW1s+OJfM71FhLLLLKdVIQ7+OJvLptiJcqS91mkY3XzbB62gujGt1CNwrFPMhujuFejJmpcxeSsSikquOOW5FUow3z4NkNMNItkdCB9OUA2dMt+37lwG0NvWMjiDvxzNAAfF4+eGfzTm+tYO4NWo7zV51D/1NOO0eU/Oyn3ujhDS7DEcNdDN1uKeu/LJUBINzd19my73Bng4xYlriJ+mm1p//gzVAQIz6JJfQrco5gMnaeGbCM5yErFJD9lR31QTF5SmzGhd9p8GmdCkOeRIMOqCFhLaY0DQIDAQAB;
s1._domainkey.techmahindra.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7nCP1IFmbquQBYYnJASy1v3CbzB4ex8FBnLE1L7xjyo6q96M7QShhM6L7HzJjhn8PNy3AOxbD3jgSh8I4Cdn3yLNg7zNvSYsVaJIcw2PeiI4zhp2m8Nm1cNTDQv+AJD5lk8h8oKRD92yb1y5lzO+CA8QfBzkdvjGzsgr7GsRRGtJv7SOfmq+BILuhsQ2s7TM39wK1xIBt+bBQnObh3L7g8SBpT41T55KQL/thdoKXiY38J8nGAfMl7CHV5luvQ8UxQnMk6D67ps0MXYhv21TRVZZHJykfTzyhVDZ1imQRDd+ez2wi1zllQRJ42hwjN5LVWJDIW7H2/3f2QlcyQ9j6QIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
15.197.154.138Website15.197.154.0/24
76.223.114.253Website76.223.114.0/24
202.41.204.43Name server ns2.techmahindra.com202.41.204.0/24
203.143.187.45Name server ns1.techmahindra.com203.143.187.0/24
52.101.144.3Mail server techmahindra-com.mail.protection.outlook.com52.101.144.0/24
119.151.8.99Authorized by SPF119.151.8.0/24
103.23.24.78Authorized by SPF103.23.24.0/24
103.23.26.70Authorized by SPF103.23.26.0/24
119.151.20.178Authorized by SPF119.151.20.0/24
13.126.171.136Authorized by SPF13.126.171.0/24
119.151.20.179Authorized by SPF119.151.20.0/24
129.145.20.114Authorized by SPF129.145.20.0/24

WHOIS of the domain techmahindra.com

Domain Name: TECHMAHINDRA.COM
   Registry Domain ID: 294131390_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.godaddy.com
   Registrar URL: http://www.godaddy.com
   Updated Date: 2024-07-20T14:08:33Z
   Creation Date: 2005-12-22T09:19:16Z
   Registry Expiry Date: 2026-12-22T09:19:16Z
   Registrar: GoDaddy.com, LLC
   Registrar IANA ID: 146
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 480-624-2505
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: NS1.TECHMAHINDRA.COM
   Name Server: NS2.TECHMAHINDRA.COM
   DNSSEC: signedDelegation
   DNSSEC DS Data: 57491 8 2 FA745E27419AD508103C247CBAE67DBFFB40EEE5FF73960997F69DA1D66E07A3
   DNSSEC DS Data: 46535 8 2 8FF23E881E548DCE7E7852E6574CBD7061669F0A1F5EEDA4EF7B62B78618C178
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T21:06: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.