Email infrastructure of do-reg.jp
According to Live Direct Marketing's daily DNS scan (September 7, 2026), do-reg.jp (Tranco rank #27,203) points its inbound MX to Self-Hosted. Its observed DMARC policy is p=none (monitoring). Policy alone does not establish inbox or spam placement.
Last updated: .
| Mailbox provider (MX) | Self-Hosted |
|---|---|
| ESPs in SPF | none detected |
| SaaS senders in SPF | none detected |
| DMARC policy | p=none |
| DMARC record | v=DMARC1; p=none |
| Tranco rank | #27,203 |
| Snapshot | 2026-09-07 (updated daily) |
Keep an eye on do-reg.jp
Get a first health report, then meaningful changes to SPF, DMARC, MX, sampled MX PTR and blocklists. See your domain history and run a real inbox placement test from your private watchlist.
Manage existing subscriptions →How do-reg.jp compares
Same daily dataset, three views: how its mailbox provider is trending, how strict DMARC is at its position in the list, and where its own policy sits among all DMARC publishers in the dataset.
Market share of Self-Hosted
DMARC enforced by list position
Policy maturity of all DMARC publishers
From observation to a useful check
- What was observed
- The DNS records and classifications in this snapshot.
- What it means
- MX describes inbound mail; SPF authorizes senders.
- What is unknown
- The actual sending IP, nested SPF dependencies, inbox placement and commercial relationships. MTA-STS, TLS-RPT and BIMI adoption are not measured.
- Next check
- Verify current DNS and test a real message: run an inbox placement test.
DNS records
Source: OpenINTEL / Tranco. Capture: 2026-09-07. These are answers from the measurement vantage point, not a live DNS check. TTL is the observed cache lifetime in seconds.
do-reg.jp · A — Answer records observed
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
Query observed at: 2026-09-07T00:29:05Z.
Response code: 0.
- do-reg.jp · A · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
203.183.220.196
do-reg.jp · AAAA — Unknown: no conclusive answer in this capture
IPv6 addresses for this name. An address record does not test service availability.
do-reg.jp · NS — Answer records observed
Name servers listed for the DNS zone.
Query observed at: 2026-09-07T00:29:05Z.
Response code: 0.
- do-reg.jp · NS · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
ns1.do-reg.jp. - do-reg.jp · NS · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
ns2.do-reg.jp. - do-reg.jp · NS · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
ns3.do-reg.jp. - do-reg.jp · NS · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
ns4.do-reg.jp.
do-reg.jp · MX — Answer records observed
Servers named to receive mail. Lower preference numbers are tried first.
Query observed at: 2026-09-07T00:29:06Z.
Response code: 0.
- do-reg.jp · MX · TTL 900 s · 2026-09-07T00:29:06Z · AD=0
10 mail.do-reg.jp. - do-reg.jp · MX · TTL 900 s · 2026-09-07T00:29:06Z · AD=0
200 mxi.do-reg.jp.
do-reg.jp · SOA — Answer records observed
Zone administration data. The serial is a version number, not a creation date or clock.
Query observed at: 2026-09-07T00:29:04Z.
Response code: 0.
- do-reg.jp · SOA · TTL 900 s · 2026-09-07T00:29:04Z · AD=0
expire=86400; minimum=3600; mname=ns1.do-reg.jp.; refresh=900; retry=900; rname=hostmaster.do-reg.jp.; serial=2026021001
do-reg.jp · CAA — Unknown: no conclusive answer in this capture
Rules for certificate issuance. These do not show whether an existing certificate is valid.
do-reg.jp · TXT — Answer records observed
Text records can publish mail policies, domain-control challenges or other data.
Query observed at: 2026-09-07T00:29:06Z.
Response code: 0.
SPF: authorized mail senders; not proof that mail was sent.
Raw TXT value
do-reg.jp · TXT · TTL 900 s · 2026-09-07T00:29:06Z · AD=0"v=spf1 redirect=_spf.do-reg.jp"
do-reg.jp · DNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
do-reg.jp · DS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
do-reg.jp · CDS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
do-reg.jp · CDNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
www.do-reg.jp · A — Answer records observed
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
Query observed at: 2026-09-07T00:29:05Z.
Response code: 0.
- d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · A · TTL 300 s · 2026-09-07T00:29:05Z · AD=0
66.22.66.62 - d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · RRSIG · TTL 300 s · 2026-09-07T00:29:05Z · AD=0
algorithm=8; key_tag=52788; labels=4; original_ttl=300; signature=01d9a9b1680cd5ca08f558c209e4a2cd3d6824fd93b206402f818ac930849c0b5406011ab703eb20046a03f48012984a7d574b69478e0f21b879d523fb84e2aeedb4b23aa3a4466171f9f182eb87c1cb77f29360e71568116b4140552ba8d54f2be4c92be79e75e3e97bff1aa4b66d41781593c0291de14f67a260a0f1a75b78; signature_expiration=1790449304; signature_inception=1788548504; signer_name=radwarecloud.net.; type_covered=A - www.do-reg.jp · CNAME · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net.
www.do-reg.jp · AAAA — Answer records observed
IPv6 addresses for this name. An address record does not test service availability.
Query observed at: 2026-09-07T00:29:05Z.
Response code: 0.
- www.do-reg.jp · CNAME · TTL 900 s · 2026-09-07T00:29:05Z · AD=0
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net.
_dmarc.do-reg.jp · TXT — Answer records observed
Text records can publish mail policies, domain-control challenges or other data.
Query observed at: 2026-09-07T00:29:06Z.
Response code: 0.
DMARC: published handling and reporting policy for authentication failures.
Raw TXT value
_dmarc.do-reg.jp · TXT · TTL 900 s · 2026-09-07T00:29:06Z · AD=0"v=DMARC1; p=none"
DNSSEC records are shown only when returned. An unset AD flag is not proof that a zone is unsigned. MTA-STS, TLS-RPT, BIMI and arbitrary DKIM selectors are not measured here; their absence cannot be inferred.
Recorded DNS history
Registry presence: first seen 2026-04-28; last seen 2026-09-07. These are appearances in our domain registry, not domain registration dates or earlier DNS values.
This history starts with saved RR captures. Provider market-share charts are aggregate context, not this domain’s DNS history. Dates identify observations; no continuous validity between them is implied. Equivalent RR states are combined, ignoring response TTL and capture-time changes. Up to 30 distinct RR states and 60 dated captures are retained within a per-domain byte limit.
Recent observed differences
2026-09-05 → 2026-09-07
www.do-reg.jp · A
Before: 2026-09-05 — Answer records observed
- d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · A
66.22.66.62 - www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
After: 2026-09-07 — Answer records observed
- d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · A
66.22.66.62 - d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · RRSIG
algorithm=8; key_tag=52788; labels=4; original_ttl=300; signature=01d9a9b1680cd5ca08f558c209e4a2cd3d6824fd93b206402f818ac930849c0b5406011ab703eb20046a03f48012984a7d574b69478e0f21b879d523fb84e2aeedb4b23aa3a4466171f9f182eb87c1cb77f29360e71568116b4140552ba8d54f2be4c92be79e75e3e97bff1aa4b66d41781593c0291de14f67a260a0f1a75b78; signature_expiration=1790449304; signature_inception=1788548504; signer_name=radwarecloud.net; type_covered=A - www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
Available saved snapshots
2026-09-07
Each query below keeps its own observation date; unknown checks may retain older values.
_dmarc.do-reg.jp · TXT
2026-09-07 — Answer records observed
DMARC: published handling and reporting policy for authentication failures.
Raw TXT value
_dmarc.do-reg.jp · TXT"v=DMARC1; p=none"
do-reg.jp · A
2026-09-07 — Answer records observed
- do-reg.jp · A
203.183.220.196
do-reg.jp · MX
2026-09-07 — Answer records observed
- do-reg.jp · MX
10 mail.do-reg.jp - do-reg.jp · MX
200 mxi.do-reg.jp
do-reg.jp · NS
2026-09-07 — Answer records observed
- do-reg.jp · NS
ns1.do-reg.jp - do-reg.jp · NS
ns2.do-reg.jp - do-reg.jp · NS
ns3.do-reg.jp - do-reg.jp · NS
ns4.do-reg.jp
do-reg.jp · SOA
2026-09-07 — Answer records observed
- do-reg.jp · SOA
expire=86400; minimum=3600; mname=ns1.do-reg.jp; refresh=900; retry=900; rname=hostmaster.do-reg.jp; serial=2026021001
do-reg.jp · TXT
2026-09-07 — Answer records observed
SPF: authorized mail senders; not proof that mail was sent.
Raw TXT value
do-reg.jp · TXT"v=spf1 redirect=_spf.do-reg.jp"
www.do-reg.jp · A
2026-09-07 — Answer records observed
- d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · A
66.22.66.62 - d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · RRSIG
algorithm=8; key_tag=52788; labels=4; original_ttl=300; signature=01d9a9b1680cd5ca08f558c209e4a2cd3d6824fd93b206402f818ac930849c0b5406011ab703eb20046a03f48012984a7d574b69478e0f21b879d523fb84e2aeedb4b23aa3a4466171f9f182eb87c1cb77f29360e71568116b4140552ba8d54f2be4c92be79e75e3e97bff1aa4b66d41781593c0291de14f67a260a0f1a75b78; signature_expiration=1790449304; signature_inception=1788548504; signer_name=radwarecloud.net; type_covered=A - www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
www.do-reg.jp · AAAA
2026-09-07 — Answer records observed
- www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
2026-09-05
Each query below keeps its own observation date; unknown checks may retain older values.
_dmarc.do-reg.jp · TXT
2026-09-05 — Answer records observed
DMARC: published handling and reporting policy for authentication failures.
Raw TXT value
_dmarc.do-reg.jp · TXT"v=DMARC1; p=none"
do-reg.jp · A
2026-09-05 — Answer records observed
- do-reg.jp · A
203.183.220.196
do-reg.jp · MX
2026-09-05 — Answer records observed
- do-reg.jp · MX
10 mail.do-reg.jp - do-reg.jp · MX
200 mxi.do-reg.jp
do-reg.jp · NS
2026-09-05 — Answer records observed
- do-reg.jp · NS
ns1.do-reg.jp - do-reg.jp · NS
ns2.do-reg.jp - do-reg.jp · NS
ns3.do-reg.jp - do-reg.jp · NS
ns4.do-reg.jp
do-reg.jp · SOA
2026-09-05 — Answer records observed
- do-reg.jp · SOA
expire=86400; minimum=3600; mname=ns1.do-reg.jp; refresh=900; retry=900; rname=hostmaster.do-reg.jp; serial=2026021001
do-reg.jp · TXT
2026-09-05 — Answer records observed
SPF: authorized mail senders; not proof that mail was sent.
Raw TXT value
do-reg.jp · TXT"v=spf1 redirect=_spf.do-reg.jp"
www.do-reg.jp · A
2026-09-05 — Answer records observed
- d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net · A
66.22.66.62 - www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
www.do-reg.jp · AAAA
2026-09-05 — Answer records observed
- www.do-reg.jp · CNAME
d3770974ec564da8b5615d557198ec67.v1.radwarecloud.net
Changes to do-reg.jp
No entry for this domain appears in the current public change feed. The feed is a selected sample, so this does not establish that its DNS stayed unchanged.
Start monitoring to build a history from your first check, or explore observed changes across the dataset.
SPF diagnostics
Static observations from the published SPF record. No nested include or redirect dependencies were evaluated. The actual sending IP and evaluation path are needed to assess the RFC 7208 limit of 10 DNS-dependent terms.
Modern mail security across the dataset
The required DNS labels are not queried. Adoption is unknown for this domain and for the population. Apex TXT anomalies are listed separately in the security posture report.
Reverse DNS of inbound MX hosts
These are separately dated observations of inbound MX addresses. They do not identify the actual sending IP. To assess outbound mail, check current forward and reverse DNS of the actual sending IP; FCrDNS and delivery were not measured here.
mail.do-reg.jp
No current PTR conclusion. The cached observation is stale. Legacy data lacks per-address DNS result codes.
DNS attempt: 2026-07-27 11:50:12 UTC. Per-address query coverage is unavailable in this legacy observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
203.183.220.202 | mail.do-reg.jp | PTR observed |
Observed PTR names belong to this domain or its subdomains. Name relationships are not a forward-confirmed reverse DNS test.
mxi.do-reg.jp
No current PTR conclusion. The cached observation is stale. Legacy data lacks per-address DNS result codes.
DNS attempt: 2026-07-27 11:50:12 UTC. Per-address query coverage is unavailable in this legacy observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
203.183.220.206 | mxi.do-reg.jp | PTR observed |
Observed PTR names belong to this domain or its subdomains. Name relationships are not a forward-confirmed reverse DNS test.
Where do-reg.jp stands
The same snapshot cut by zone, by list position and by how alive the published policies are.
- In .jp 22.8% of 9,560 DMARC publishers enforce their policy.
- At this list position the top three mailbox providers hold 60.1% of domains (Google Workspace, Microsoft 365, Unknown / Other).
- Across the dataset 25.1% of DMARC records are inert — policy does nothing and no reports are collected.
Context of .jp
Most used sending platforms among 5,428 SPF-publishing domains in Japan: Amazon SES 25.4% · Salesforce 8.6% · Zendesk 5.9% · SendGrid (Twilio) 5.5%. do-reg.jp runs a stack that is not among the most common in this zone.
How to interpret these observations
MX identifies the observed inbound mailbox or gateway. SPF includes identify services authorised to send for the domain. DMARC shows the published authentication policy. The dataset currently contains 2 populated signal groups for this page.
Observed deliverability context: based on the available observations, this page describes DNS configuration only. It does not represent a complete audit of do-reg.jp and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does do-reg.jp use?
do-reg.jp uses Self-Hosted for inbound mail (detected from its primary MX record) as of September 7, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
Does do-reg.jp enforce DMARC?
No — do-reg.jp publishes p=none, which only monitors and does not block spoofing (as of September 7, 2026).
Related domain statistics
Nearby domains in the Tranco ranking: thaiticketmajor.com · unomaha.edu · fortinetipssubmit.com · airpaz.com
Browse provider data · Compare historical periods · Run an inbox placement test
Data: Email infrastructure of the Tranco top-1M, daily snapshot 2026-09-07, derived from OpenINTEL forward-DNS measurements. Cite with the date — records change daily.