konicaminolta.com

Checked 22 October 2026, 09:32 UTC · via 8.8.8.8
✗Problems found
23 passed 2 warnings 1 failed 8 info

Registration

info

.com generic · 1API GmbH · expires 2027-01-07

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
1API GmbH
Registered
7 January 2003
Last changed
25 December 2025
Expires
7 January 2027
Status
client transfer prohibited
Registry nameservers
dns-b.iij.ad.jp, dns-c.iij.ad.jp
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-01-07 #3
    The registration is valid until 2027-01-07 (76 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns-b.iij.ad.jp, dns-c.iij.ad.jp

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns-b.iij.ad.jp, dns-c.iij.ad.jp
NS in the zone
ns020-31ong4vgembe42fr.3.d-53.info, ns020-31ong4vgembe42fr.3.d-53.jp, ns020-31ong4vgembe42fr.3.d-53.org
NameserverAddressesNetwork (AS)Glue
dns-b.iij.ad.jp (parent only)202.32.219.51 2001:240:bb81::28:51AS2497 IIJ - Internet Initiative Japan Inc., JP AS2497 IIJ - Internet Initiative Japan Inc., JP-
dns-c.iij.ad.jp (parent only)210.138.20.111 2001:240:bb81::29:111AS2497 IIJ - Internet Initiative Japan Inc., JP AS2497 IIJ - Internet Initiative Japan Inc., JP-
ns020-31ong4vgembe42fr.3.d-53.info (zone only)202.32.219.51 2001:240:bb81::28:51AS2497 IIJ - Internet Initiative Japan Inc., JP AS2497 IIJ - Internet Initiative Japan Inc., JP-
ns020-31ong4vgembe42fr.3.d-53.jp (zone only)203.180.146.111 2001:240:bb81::29:1111AS2497 IIJ - Internet Initiative Japan Inc., JP AS2497 IIJ - Internet Initiative Japan Inc., JP-
ns020-31ong4vgembe42fr.3.d-53.org (zone only)210.138.20.111 2001:240:bb81::29:111AS2497 IIJ - Internet Initiative Japan Inc., JP AS2497 IIJ - Internet Initiative Japan Inc., JP-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns-b.iij.ad.jp, dns-c.iij.ad.jp.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: dns-b.iij.ad.jp, dns-c.iij.ad.jp; only in the zone: ns020-31ong4vgembe42fr.3.d-53.info, ns020-31ong4vgembe42fr.3.d-53.jp, ns020-31ong4vgembe42fr.3.d-53.org. dns-b.iij.ad.jp, dns-c.iij.ad.jp, ns020-31ong4vgembe42fr.3.d-53.info, ns020-31ong4vgembe42fr.3.d-53.jp, ns020-31ong4vgembe42fr.3.d-53.org report NS ns020-31ong4vgembe42fr.3.d-53.info ns020-31ong4vgembe42fr.3.d-53.jp ns020-31ong4vgembe42fr.3.d-53.org.
    #7
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:240:bb81::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS2497 (IIJ - Internet Initiative Japan Inc., JP): 10 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .jp
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

10 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns-b.iij.ad.jp 202.32.219.51NOERROR, 218 ms, authoritativenoyes / yesrefused-
dns-b.iij.ad.jp 2001:240:bb81::28:51NOERROR, 236 ms, authoritativenoyes / yesrefused-
dns-c.iij.ad.jp 210.138.20.111NOERROR, 17 ms, authoritativenoyes / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K
dns-c.iij.ad.jp 2001:240:bb81::29:111NOERROR, 22 ms, authoritativenono / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K
ns020-31ong4vgembe42fr.3.d-53.info 202.32.219.51NOERROR, 218 ms, authoritativenoyes / yesrefused-
ns020-31ong4vgembe42fr.3.d-53.info 2001:240:bb81::28:51NOERROR, 237 ms, authoritativenoyes / yesrefused-
ns020-31ong4vgembe42fr.3.d-53.jp 203.180.146.111NOERROR, 17 ms, authoritativenoyes / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K
ns020-31ong4vgembe42fr.3.d-53.jp 2001:240:bb81::29:1111NOERROR, 25 ms, authoritativenono / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K
ns020-31ong4vgembe42fr.3.d-53.org 210.138.20.111NOERROR, 23 ms, authoritativenoyes / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K
ns020-31ong4vgembe42fr.3.d-53.org 2001:240:bb81::29:111NOERROR, 21 ms, authoritativenono / yesrefusedIIJ_DNS_PLATFORM_SERVICE_K

Checks

  • ✓ All respond #14
    All 10 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns-c.iij.ad.jp: "IIJ_DNS_PLATFORM_SERVICE_K"; ns020-31ong4vgembe42fr.3.d-53.jp: "IIJ_DNS_PLATFORM_SERVICE_K"; ns020-31ong4vgembe42fr.3.d-53.org: "IIJ_DNS_PLATFORM_SERVICE_K".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns-c.iij.ad.jp (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:51092->[2001:240:bb81::29:111]:53: read: connection reset by peer; ns020-31ong4vgembe42fr.3.d-53.jp (2001:240:bb81::29:1111): read tcp [2a01:4f8:1c1c:eebf::1]:55110->[2001:240:bb81::29:1111]:53: read: connection reset by peer; ns020-31ong4vgembe42fr.3.d-53.org (2001:240:bb81::29:111): read tcp [2a01:4f8:1c1c:eebf::1]:51094->[2001:240:bb81::29:111]:53: read: connection reset by peer.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 1048 · primary ns000.d-53.net

Found

Primary (MNAME)
ns000.d-53.net
Contact (RNAME)
dns-managers.iij.ad.jp
Serial
1048
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
dns-b.iij.ad.jp (202.32.219.51)1048
dns-b.iij.ad.jp (2001:240:bb81::28:51)1048
dns-c.iij.ad.jp (210.138.20.111)1048
dns-c.iij.ad.jp (2001:240:bb81::29:111)1048
ns020-31ong4vgembe42fr.3.d-53.info (202.32.219.51)1048
ns020-31ong4vgembe42fr.3.d-53.info (2001:240:bb81::28:51)1048
ns020-31ong4vgembe42fr.3.d-53.jp (203.180.146.111)1048
ns020-31ong4vgembe42fr.3.d-53.jp (2001:240:bb81::29:1111)1048
ns020-31ong4vgembe42fr.3.d-53.org (210.138.20.111)1048
ns020-31ong4vgembe42fr.3.d-53.org (2001:240:bb81::29:111)1048

Checks

  • ✓ Serial 1048 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 15m.
  • i
    Hidden master (not resolvable)
    The primary nameserver ns000.d-53.net is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.
    #24
  • ✓ Contact dns-managers@iij.ad.jp #25
    The SOA RNAME dns-managers.iij.ad.jp means dns-managers@iij.ad.jp.
  • ✓ Counter serial #26
    The serial 1048 is a plain counter.

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC3
NSEC3
0 iterations, 0-byte salt
Signatures valid until
20 November 2026

DNSKEY in the zone

Key tagRoleAlgorithm
45130ZSK (256)ECDSAP256SHA256 (13)
23943ZSK (256)ECDSAP256SHA256 (13)
35186KSK (257)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Signatures valid until 2026-11-20 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-20 08:20 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

13 records at the apex

Found

Read from
202.32.219.51:53
TypeValueTTL
SOAns000.d-53.net. dns-managers.iij.ad.jp. 1048 3600 600 604800 900600
NSns020-31ong4vgembe42fr.3.d-53.info.600
NSns020-31ong4vgembe42fr.3.d-53.jp.600
NSns020-31ong4vgembe42fr.3.d-53.org.600
A3.114.251.146600
MX10 gw9150.fortimail.com.600
TXT"atlassian-domain-verification=gZ3MXXc6XjCBcW/XyvFtHyNeylop2j161Twvay/XRbh6B5IpCgi1H85Mu5/wZM48"600
TXT"v=spf1 a:gw9150.fortimail.com include:_spf.salesforce.com include:webcas.net include:auth.msgapp.com include:spf.protection.outlook.com include:44981724.spf01.hubspotemail.net include:amazonses.com ~all"600
TXT"93o1h07pd3s0hpdh0mhkah00ep"600
TXT"facebook-domain-verification=h62459rgw4gh18do9ldmh65gcnmbkp"600
TXT"globalsign-domain-verification=nSTDJ5AMW_nMkY6zTzrNRccJKFs7Fp_hbryLsdWph9"600
TXT"sending_domain466361=0d11090f2bbc10cbd9510d981ac38d3b2c9accc87055117544ae6cfc8fcb583a"600
TXT"atlassian-domain-verification=ZXDwlWX4UEEILBGreoLHpyKc2mWvAQNfJm4q6tvZLqa92Yzk0PEBaDLayloTUM4K"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 10m, NS 10m. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35