Dataweaz

nttdata.com

Summary

Registrar
PSI-Japan, Inc.
Status
clientTransferProhibited
Created on
July 24, 1995
Expires on
July 23, 2027
Name servers
ns02.nttdata.co.jp, ns6.via.or.jp, ns6.intervia.ad.jp, ns01.nttdata.co.jp, ns03.nttdata.co.jp
Mail servers
mxa-004dc302.gslb.pphosted.com, mxb-004dc302.gslb.pphosted.com
SPF
Soft

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 nttdata.com but fails SPF and DKIM checks.

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed

Record

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

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

RuleValueResult
include3sb1up9ca5.powerspf.comAllowed
all—Suspicious

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:3sb1up9ca5.powerspf.com ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
k1MailchimpRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive

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

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

nttdata.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.nttdata.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.nttdata.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.nttdata.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.nttdata.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 nttdata.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
ns02.nttdata.co.jp163.135.156.55
ns6.via.or.jp203.182.20.46
ns6.intervia.ad.jp203.182.20.14
ns01.nttdata.co.jp163.135.156.25
ns03.nttdata.co.jp163.135.156.85

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @nttdata.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
5mxa-004dc302.gslb.pphosted.com185.183.30.93
5mxb-004dc302.gslb.pphosted.com185.183.30.93

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

NameContent
nttdata.comsmartsheet-site-validation=V05zDz4bvPwH5MRRJ_AK4m4v3eqtQNoV
nttdata.compardot836223=81fff967169843b79ee61a5bd539f1d3bfc3d63aa700db5d5221630e20d411e1
nttdata.comanthropic-domain-verification-qcf6e8=6qTmGfWurpAOofIqwWHJ5zt6r
nttdata.commiro-verification=bcef0e4977e1e8f8c2f7a9b22901201860d479f8
nttdata.comadobe-idp-site-verification=00054bd1d50ba05bd6162db4438c40f16fd606fb03e65720a26a6c2d0f11d021
nttdata.comMS=ms42059975
nttdata.comopenai-domain-verification=dv-IG4kU1T6Nkl3ZzfjtTU5o4ze
nttdata.comsending_domain1119643=2a100e29a378150a70c7f0caa439ae1fefdebb8402550487158fc6fd74c4a949
nttdata.comopenai-domain-verification=dv-07ddp1v0dSWt7s0PYKkoJJEo
nttdata.com_y2taxe9rryb17ayfqfre4n1615l84rs
nttdata.comonetrust-domain-verification=60e2acaa4969477595782338db87250a
nttdata.compardot836203=03da1353d816fe74d78c7d37d70d538ab6c3e231139a098f7d9a96e590a19a12
nttdata.comverification_token=4mPyNGWrwX5zVnbknJKNcxOS5
nttdata.comsmartsheet-site-validation=RxjBTyQA_g_7bC3fmA8UkB0FT9nRyCaz
nttdata.comsitecore-domain-verification=bceae7c64fb24f4bab270a0011c89e68
nttdata.com7ua9clj3facquaetc5rgo61mqj
nttdata.compardot547422=a066810a35420ac4d8d632fd5ec5318f9d78af2e9d462942c572477f6c4333d9
nttdata.comverification_token=bgmH2j7DoH6VQ3BFKXdxf7ceU
nttdata.compardot1000551=cc4638b8c6a348a640faf736adaf79559ed382dc05977f6624b21ca3955c96ec
nttdata.comwrike-verification=NTQ4NzY0MDo3NGJmOGJhMWM1NTQxMWU1N2Q3ZDllNjNhZmY3ZmE0YmY3YjhmZmY4ZjAxZjJmOThlODY0NmNmZDMyMTIwZThk
nttdata.commiro-verification=74a3ffd0198a638bbfdf92ea861249ce8cb8f3f7
nttdata.comapple-domain-verification=giwucGLa1aJYBgaY
nttdata.comgoogle-site-verification=1xfaqC5-BYsOMr7fLawPypNuey3xg1TqHmgmWrGFFa4
nttdata.combmi4np3vlaomihesdodj57mg74
nttdata.compardot_312401_*=d10d98f5ac7269584abf0eec79b76732e7ec6226d1562b71d2a82a7e507d46b5
nttdata.com_globalsign-domain-verification=ds-N2WIymaPgeQStMRRFBCpoCD_bXwTWDXdnyQ0t6O
nttdata.comv=spf1 include:3sb1up9ca5.powerspf.com ~all
nttdata.compardot836193=1224cc34fa604c049943d26ff7c94be3112921c5e1282d0baccaa431e816a5ad
nttdata.comIYCaPpE/G9R7+Cdz3PZ0H9lxeWw/+4+i+nf0x9WH+jt8Qtb5b2xqMQzKwmciZs8/vE91adHML9HagZ28erFCPw==
nttdata.com_glft57mvaa4dl11qnk2m0ku3x5os294
nttdata.com00D3i000000qweR=1TBPU00000001Va
nttdata.comonetrust-domain-verification=2b8fad1cb3f845e2a4197d09ddf1b958
nttdata.comgoogle-gws-recovery-domain-verification=73739344
nttdata.comwebexdomainverification.4C675B8B7EAAB136E053AB06FC0A3F65=f1961d37-d75a-4f6b-8224-b5d3d802b2df
nttdata.comsending_domain1000551=492779bffe5f417616dfa9871a9439bb8d27720e93786ff0c7bbde38b39b930d
nttdata.comMS=ms39092878
nttdata.compardot970163=9ca945a28c4cffe8a45d45a51fcd625f635fc9ee6ad95f1b548a3b7837bc325b
nttdata.comgoogle-site-verification=VGLMdzXGjSiXupIiBQ_vU1SLuxqSlQoseHpLRGvbey0
nttdata.com_globalsign-domain-verification=HhWkAnOsUjQnnHsmq4cUPogJecCGIsSvsFbNVee9T_
nttdata.compoppulo-domain-verification=fba51459-cefa-4274-b2e0-06d4778c7c9b
nttdata.com_globalsign-domain-verification=3jhOdyiS_ljFU1WJ7ecEQdr8D_jNmSvi0tafKAxEgq
nttdata.com_globalsign-domain-verification=rQdx77wa6So8uPqamBGMsOKTCiSUrZ7EPpvKc_M2nZ
nttdata.compardot60932=2ad556ca193e6979db6b2c9c90ae48e42bed4f1d7e126e8b068baf942ecba215
nttdata.compardot1119643=a53e547985eb8e356836e71b45c3ac540d0edf7a5eb31be4f36dd6aa40de7ee2
_dmarc.nttdata.comv=DMARC1; p=none; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected],mailto:[email protected]; fo=1;
k1._domainkey.nttdata.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
s1._domainkey.nttdata.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1PNgEZ9Y8IdOWLCvzm63MJqUJ3mYCegY9dDFRRYB5TQjEAd2LGKyWIih5E5TQ5ixySg6h8En7srmngOB5u1UU3BQaVNYD/0pTp3QGkB7qwhZq9wDZRfikOb0q60HI0pv7BOw0p//Rz5ENKhFrnaZNMS3m+d1MRslJp6AMXrfUzaCNIY1LvhVrF8yzM2XQ7cXPlWIbhL6Py1Cl8QT0fYK9CuAHCl8ZTc7AoAKCD+jSkWd+n3HrfZoBj2Xs8MburuR7txBrPaZRq7hgUCI+mYosGGmP5yM/r8+byPT1afITF9ZVpDSO/bbgKL0Motq2iZ6GyCYUJVyrYaK14ydKF2hnQIDAQAB
s2._domainkey.nttdata.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAo5EmpjaGSTHmK/9SeidAwbl6TxMztt57FpGSTbuaADh+3kB2c2fRLbCRK0Pfv2TUb8t86ynKoi2DU/c5/0/xqrIziT73zLDJEp61/bRzUZNy8yB2KrtTljTiOTUthQDxMuyLLEPXcVKk38ae60821I/1X1L6JwTIIgNLSlgufKWHWO4BNqYSXb9leOijNWAWlWl+s5C016tVVrXnY7rIE6SEYr6KLKLdEWuCMTBmRaKh7AzWXwPw6zUcL+NhpjHSQ1ImD/MFQvpGqvJos6sCUiHZyGS/p2HbOCpjabwwhJLcSQZmWqalxWtX0RwwcSdGjA8nXIyV8by4Za+G0xc8zQIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
15.197.144.111Website15.197.144.0/24
3.33.142.69Website3.33.142.0/24
163.135.156.55Name server ns02.nttdata.co.jp163.135.156.0/24
203.182.20.46Name server ns6.via.or.jp203.182.20.0/24
203.182.20.14Name server ns6.intervia.ad.jp203.182.20.0/24
163.135.156.25Name server ns01.nttdata.co.jp163.135.156.0/24
163.135.156.85Name server ns03.nttdata.co.jp163.135.156.0/24
185.183.30.93Mail server mxa-004dc302.gslb.pphosted.com, Mail server mxb-004dc302.gslb.pphosted.com185.183.30.0/24

WHOIS of the domain nttdata.com

Domain Name: NTTDATA.COM
   Registry Domain ID: 1211022_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.psi.jp
   Registrar URL: https://psi.jp/
   Updated Date: 2026-07-24T08:01:53Z
   Creation Date: 1995-07-24T04:00:00Z
   Registry Expiry Date: 2027-07-23T04:00:00Z
   Registrar: PSI-Japan, Inc.
   Registrar IANA ID: 78
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +81.332346921
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS01.NTTDATA.CO.JP
   Name Server: NS02.NTTDATA.CO.JP
   Name Server: NS03.NTTDATA.CO.JP
   Name Server: NS6.INTERVIA.AD.JP
   Name Server: NS6.VIA.OR.JP
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T11:22: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.