Dataweaz

global.ntt

Summary

Registrar
Japan Registry Services Co.,Ltd.
Status
ok
Created on
April 25, 2019
Expires on
April 25, 2027
Name servers
ns4-04.azure-dns.info, ns3-04.azure-dns.org, ns1-04.azure-dns.com, ns2-04.azure-dns.net
Mail servers
mxb-004dc302.gslb.pphosted.com, mxa-004dc302.gslb.pphosted.com, 185.183.30.93, 185.132.183.33
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 global.ntt but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
—
Failure reports
—

Record

v=DMARC1; p=reject; pct=100;

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for global.ntt.

RuleValueResult
ip466.159.232.79Allowed
ip4143.55.149.229Allowed
includespf.protection.outlook.comAllowed
ip4104.40.229.156Allowed
ip452.169.0.179Allowed
ip4199.91.137.26Allowed
ip474.119.8.195Allowed
ip4204.10.94.6Allowed
ip483.231.199.204Allowed
includespf1.global.nttAllowed
includespf2.global.nttAllowed
includespf3.global.nttAllowed
includespf4.global.nttAllowed
includespf5.global.nttAllowed
includespf6.global.nttAllowed
includespf7.global.nttAllowed
exists%{i}._spf.mta.salesforce.comAllowed
all—Rejected

Top-level DNS lookups: 9 of 10 allowed

Record

v=spf1 ip4:66.159.232.79 ip4:143.55.149.229 include:spf.protection.outlook.com ip4:104.40.229.156 ip4:52.169.0.179 ip4:199.91.137.26 ip4:74.119.8.195 ip4:204.10.94.6 ip4:83.231.199.204 include:spf1.global.ntt include:spf2.global.ntt include:spf3.global.ntt include:spf4.global.ntt include:spf5.global.ntt include:spf6.global.ntt include:spf7.global.ntt exists:%{i}._spf.mta.salesforce.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
mandrillMandrillRSA 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 global.ntt arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from global.ntt 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 @global.ntt 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

global.ntt  MX  10 mx1.global.ntt.
global.ntt  MX  20 mx2.global.ntt.

What the record contains

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

global.ntt  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.global.ntt, 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.global.ntt  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.global.ntt, 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.global.ntt  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 global.ntt

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
A45.60.83.32
A45.60.134.32

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
ns4-04.azure-dns.info208.84.5.4
ns3-04.azure-dns.org204.14.183.4
ns1-04.azure-dns.com13.107.236.4
ns2-04.azure-dns.net150.171.21.4

Mail servers (MX)

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

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.global.ntt.

NameContent
global.nttatlassian-domain-verification=YT/0TamTnmfHlD02D5ICYAsDoPfiOY1hH8LmDbOXOKkVTLBZ0xDBSUk4D9a8S0sj
global.nttopenai-domain-verification=dv-bEAMjIJ1NJcT7QLX4gCKLTvj
global.nttslack-domain-verification=QFYROKmhjGMWue20AKty2kWBnF6xldNGUbGZfJB1
global.nttdtm-domain-verification=TIP0t5E2uOL7dzyD4GODEb2LhT8uA6uM5EhfPOHm378
global.nttopenai-domain-verification=dv-mHdcYVI4G4EGv4i3C2WnqJJg
global.nttcursor-domain-verification-bbz8x6=Zi9FAD7zHTn2lQXbEZPlf38Bj
global.nttpardot1119643=bf4e18c5c4c22570a0ee23eb20934499016ff77ed34da2fc5d3a67bcce85e9b7
global.nttpardot1172231=34c65616dc3e549e4da2748d338a82a8698fe11e2a368539ca999c08ecc0ef36
global.ntt00D3i000000qweR=1TBPU000000060b
global.ntt00DOu000008XEXB=1TBOu00000002Jd
global.ntt_cxxi78pf2t15a8sz9vzlee48ab763qz
global.nttautodesk-domain-verification=_vySAFXP__KPIEy2Pc-w
global.nttpoppulo-domain-verification=4dfbd810-0b3f-492f-ac8f-fa2e3e60fdc4
global.nttSFMC-rlZakpVqL5zHGBBBoaOYqJ7b_dGTpYVjwwaKt5_s
global.ntt1e68987ae29c46b184c04798293dc4b4
global.ntt0ed1fe018a4de36d38e9cd4085bbec729fbbde8603
global.nttN0T3T58237
global.nttv=spf1 ip4:66.159.232.79 ip4:143.55.149.229 include:spf.protection.outlook.com ip4:104.40.229.156 ip4:52.169.0.179 ip4:199.91.137.26 ip4:74.119.8.195 ip4:204.10.94.6 ip4:83.231.199.204 include:spf1.global.ntt include:spf2.global.ntt include:spf3.global.ntt include:spf4.global.ntt include:spf5.global.ntt include:spf6.global.ntt include:spf7.global.ntt exists:%{i}._spf.mta.salesforce.com -all
global.nttonetrust-domain-verification=561c0731669c402a9975fa47528ce9ec
global.nttsywjm5gskk40qkhr4vv2zmfg3d31by1k
global.nttpaloaltonetworks-site-verification=628f1a25eefe7012175ebec231bb2fb1336d6778f6d65f5e0bbfc43990aadae6
global.nttdocusign=2b107879-7a1c-468a-b69e-7af1c9ad8a34
global.nttadobe-idp-site-verification=873e8b68496325b13e1fd57b6dbd45160e01f963b8532c307db6c8febcb2017b
global.nttatlassian-domain-verification=02zf6btl8AqxEX/Fxbqe/SXzZ82okZVmKYptVAcqGtl3URNbV2jkz2gTrPz4N5Ju
_dmarc.global.nttv=DMARC1; p=reject; pct=100;
selector1._domainkey.global.nttv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyAf9XyI0pr16mo/7KU5aQ6qndf9m9bQ039iW+GmB70Ib2Vu0xcpE1taUqC6KFTimjMW0CGAsXZggwB5H7/gjMNbpbzqEJX92xyMUgJ7nkHk5MoZo0j7G65S8e8didSRY+FN3mLBdbUxwM4MUpxuLRJ1u+698QOZhmzlTGATrYgXfgkxWJSISVMnw3Sys96ht952MVSJlc7P07DfsZgRYGJgZqiq/4+tYURKMSc4arKoKoZSSM1O1orye1W7WDPE6OBmGDt2+/64+6uNMKH20glx6XY6/R/1R1n3oSqdTTPhrCG+zXRfMtG53lLEQsm3OhPouY5rVcEnVSEhJSXR07QIDAQAB;
k2._domainkey.global.nttv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.global.nttv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
mandrill._domainkey.global.nttv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey.global.nttk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw6grrTE439rzwxi3hyOGMaMBp7/DnV5ndDCxy5adDKpF45V/gTiQJhTSD4nNrREZlszaq4SjoSHH2CLLodqDW3VNK4xqf/3juId3UUjydrdXQRJeJ1YlVkiT6jVEGIvhhuhjyA5nWrO8oABWb0LaO64+iWlKbtkWuatDSqYP61fqKNR/DZ4SS6haDtAcJqIhnlGp0WcTzYMI1Quk+jm/06kV7skKHii4RCisigZktGlpMOQ+yjzgPao2a7ugAbq0YIk4QQCQ04STfuCzO9mWxeypErLc9tOtj63HiQJN+y5KzZEM8BYFzh1ZX/WVOe1FmlQGi+vUaX0G6qW1+6CRZQIDAQAB
s2._domainkey.global.nttk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApM6X6a+FrqgY3/wSSh8/Ny7/4gZwwOEZNcNMxWa6Nh/Z+aueEbpqKRLLbvEAznDEfSaTXOaN13q+oqpmuhsIcu+JUavyJcwkPgAtskp7VJG+5l/eyqE5scK3OAz/emhzDjR+p+NHOhQ9X5aWvVwZC+V4JITt3bIUK2CPRXfq5O1zsQpzbE5XckD9vm0hJBl26yR5ycV9zRuRm8Ju+4bJkCvzKa8E2mLML3dq2IGiDJC5kJ9xCImii1JTFVp+oyuFXECS1rM5wGOxpm4xJXntZCbPt4KkZplNXRPjTnkV9eqvdMQ9moNbCbCC32S7vPpjVIeuUiCVAwzGTAJ0A1N/GQIDAQAB

Related IP addresses

IPv4 addresses used by global.ntt: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
45.60.83.32Website45.60.83.0/24
45.60.134.32Website45.60.134.0/24
208.84.5.4Name server ns4-04.azure-dns.info208.84.5.0/24
204.14.183.4Name server ns3-04.azure-dns.org204.14.183.0/24
13.107.236.4Name server ns1-04.azure-dns.com13.107.236.0/24
150.171.21.4Name server ns2-04.azure-dns.net150.171.21.0/24
185.132.183.33Mail server mxb-004dc302.gslb.pphosted.com185.132.183.0/24
185.183.30.93Mail server mxa-004dc302.gslb.pphosted.com185.183.30.0/24
66.159.232.79Authorized by SPF66.159.232.0/24
143.55.149.229Authorized by SPF143.55.149.0/24
104.40.229.156Authorized by SPF104.40.229.0/24
52.169.0.179Authorized by SPF52.169.0.0/24
199.91.137.26Authorized by SPF199.91.137.0/24
74.119.8.195Authorized by SPF74.119.8.0/24
204.10.94.6Authorized by SPF204.10.94.0/24
83.231.199.204Authorized by SPF83.231.199.0/24

WHOIS of the domain global.ntt

Domain Name: GLOBAL.NTT
Registry Domain ID: 00000JUW5GIWHBW0TYO01Y8T6-NTT
Registrar WHOIS Server: whois.registrar.ntt
Registrar URL: https://jprs.jp/registrar
Updated Date: 2026-03-11T00:15:01Z
Creation Date: 2019-04-25T04:31:14Z
Registry Expiry Date: 2027-04-25T04:31:14Z
Registrar: Japan Registry Services Co.,Ltd.
Registrar IANA ID: 1485
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +81.352158451
Domain Status: ok  https://icann.org/epp#ok
Registry Registrant ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Registrant Name: NTT, Inc.
Registrant Organization: Public Relation Department
Registrant Street: 1-5-1 Otemachi
Registrant City: Chiyoda-ku
Registrant State/Province: Tokyo
Registrant Postal Code: 100-8116
Registrant Country: JP
Registrant Phone: +81.9050281770
Registrant Email: [email protected]
Registry Admin ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Admin Name: NTT, Inc.
Admin Organization: Public Relation Department
Admin Street: 1-5-1 Otemachi
Admin City: Chiyoda-ku
Admin State/Province: Tokyo
Admin Postal Code: 100-8116
Admin Country: JP
Admin Phone: +81.9050281770
Admin Email: [email protected]
Registry Tech ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Tech Name: NTT, Inc.
Tech Organization: Public Relation Department
Tech Street: 1-5-1 Otemachi
Tech City: Chiyoda-ku
Tech State/Province: Tokyo
Tech Postal Code: 100-8116
Tech Country: JP
Tech Phone: +81.9050281770
Tech Email: [email protected]
Name Server: NS1-04.AZURE-DNS.COM
Name Server: NS2-04.AZURE-DNS.NET
Name Server: NS3-04.AZURE-DNS.ORG
Name Server: NS4-04.AZURE-DNS.INFO
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T16:13:19Z <<<

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

NTT WHOIS LEGAL DISCLAIMER:

The WHOIS service (the "Service") offered by NTT, Inc. (NTT) and the access to the records in the NTT WHOIS database (the "Database") are provided for information purposes and query-based public access.

Neither NTT nor any of its officers, directors, employees or agents makes any warranty as to the results to be obtained from use of the Service.  NTT specifically disclaims all warranties of any kind, whether express, implied or statutory, including, but not limited to, any warranties of title, non-infringement, merchantability or fitness for a particular purpose.
In no event shall NTT nor anyone else involved in creating, supporting, producing or delivering the Service be liable to you for any lost profits or costs, even if NTT or such person has been advised of the possibility of such damages.

NTT allows you to use the Service only for lawful purposes and that, under no circumstances shall you use the Service to: (a) allow, enable or otherwise support the transmission by e-mail, telephone, postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of NTT or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations.

By submitting the query you agree to abide by these terms and further agree that NTT may take measures to limit the use of the Service in order to protect the privacy of its registrants or the integrity of the Database.

NTT reserves the right to modify or change these terms at any time without prior or subsequent notification of any kind.
Domain Name: GLOBAL.NTT
Registry Domain ID: 00000JUW5GIWHBW0TYO01Y8T6-NTT
Registrar WHOIS Server: whois.registrar.ntt
Registrar URL: https://jprs.jp/registrar
Updated Date: 2026-03-11T00:15:01Z
Creation Date: 2019-04-25T04:31:14Z
Registrar Registration Expiration Date: 2027-04-25T04:31:14Z
Registrar: Japan Registry Services Co.,Ltd.
Registrar IANA ID: 1485
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +81.352158451
Domain Status: ok  https://icann.org/epp#ok
Registry Registrant ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Registrant Name: NTT, Inc.
Registrant Organization: Public Relation Department
Registrant Street: 1-5-1 Otemachi
Registrant City: Chiyoda-ku
Registrant State/Province: Tokyo
Registrant Postal Code: 100-8116
Registrant Country: JP
Registrant Phone: +81.9050281770
Registrant Email: [email protected]
Registry Admin ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Admin Name: NTT, Inc.
Admin Organization: Public Relation Department
Admin Street: 1-5-1 Otemachi
Admin City: Chiyoda-ku
Admin State/Province: Tokyo
Admin Postal Code: 100-8116
Admin Country: JP
Admin Phone: +81.9050281770
Admin Email: [email protected]
Registry Tech ID: 00000MC9UPENQZL0OSA02W6UZ-NTT
Tech Name: NTT, Inc.
Tech Organization: Public Relation Department
Tech Street: 1-5-1 Otemachi
Tech City: Chiyoda-ku
Tech State/Province: Tokyo
Tech Postal Code: 100-8116
Tech Country: JP
Tech Phone: +81.9050281770
Tech Email: [email protected]
Name Server: NS1-04.AZURE-DNS.COM
Name Server: NS2-04.AZURE-DNS.NET
Name Server: NS3-04.AZURE-DNS.ORG
Name Server: NS4-04.AZURE-DNS.INFO
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T16:13:24Z <<<

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

JPRS WHOIS LEGAL DISCLAIMER:

The WHOIS service (the "Service") offered by Japan Registry Services Co., Ltd. (JPRS) and the access to the records in the JPRS WHOIS database (the "Database") are provided for information purposes and query-based public access.

Neither JPRS nor any of its officers, directors, employees or agents makes any warranty as to the results to be obtained from use of the Service.  JPRS specifically disclaims all warranties of any kind, whether express, implied or statutory, including, but not limited to, any warranties of title, non-infringement, merchantability or fitness for a particular purpose.
In no event shall JPRS nor anyone else involved in creating, supporting, producing or delivering the Service be liable to you for any lost profits or costs, even if JPRS or such person has been advised of the possibility of such damages.

JPRS allows you to use the Service only for lawful purposes and that, under no circumstances shall you use the Service to: (a) allow, enable or otherwise support the transmission by e-mail, telephone, postal mail, facsimile or other means of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of any registry operator or ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations.

By submitting the query you agree to abide by these terms and further agree that JPRS may take measures to limit the use of the Service in order to protect the privacy of its registrants or the integrity of the Database.

JPRS reserves the right to modify or change these terms at any time without prior or subsequent notification of any kind.

% Query time: 2655 msec
% WHEN: Thu Oct 01 16:13:22 UTC 2026