Domain report: nikon.de

Registration

info

.de country-code

i

.de is a country-code TLD (ccTLD)

Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

#1
✓ TLD delegated and signed #2

.de is delegated in the root zone and DNSSEC-signed.
i

Registration data not available

No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

#3

warn

ns1.webhosting.jp, ns3.webhosting.jp, ns4.webhosting.jp

Nameserver	Addresses	Network (AS)	Glue
ns1.webhosting.jp	129.80.65.57	AS31898 ORACLE-BMC-31898 - Oracle Corporation, US	-
ns3.webhosting.jp	138.91.4.77	AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US	-
ns4.webhosting.jp	143.47.126.139	AS31898 ORACLE-BMC-31898 - Oracle Corporation, US	-

✓ 3 nameservers #6

Delegated to ns1.webhosting.jp, ns3.webhosting.jp, ns4.webhosting.jp.
✓ Parent and zone agree #7

The parent delegation and the zone's NS records list the same nameservers.
✓ 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.
✓ Nameservers in different networks #10

The nameservers are spread over 3 IPv4 /24s and 0 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS31898 (ORACLE-BMC-31898 - Oracle Corporation, US): 2 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 1 address.
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
!

No IPv6

None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13

warn

3 of 3 addresses answer authoritatively

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.webhosting.jp 129.80.65.57	NOERROR, 103 ms, authoritative	no	yes / yes	refused	9.20.29
ns3.webhosting.jp 138.91.4.77	NOERROR, 235 ms, authoritative	no	yes / yes	refused	9.20.29
ns4.webhosting.jp 143.47.126.139	NOERROR, 103 ms, authoritative	no	yes / yes	refused	9.20.29

✓ All respond #14

All 3 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.
!

Software version disclosed

These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webhosting.jp: "9.20.29"; ns3.webhosting.jp: "9.20.29"; ns4.webhosting.jp: "9.20.29". Hide or replace the version string.

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✓ TCP supported #19

All nameservers answer over TCP.
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

pass

serial 2026071401 · primary ns1.webhosting.jp

✓ Serial 2026071401 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 3h, retry 1h, expire 7d, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver ns1.webhosting.jp is one of the listed nameservers.
✓ Contact sitemgr@webhosting.jp #25

The SOA RNAME sitemgr.webhosting.jp means sitemgr@webhosting.jp.
✓ Date-based serial #26

The serial 2026071401 follows the YYYYMMDDnn convention (2026-07-14).

info

Not signed

Lookup error: read udp 46.225.38.91:35455->129.80.65.57:53: i/o timeout

info

7 records at the apex

Type	Value	TTL
SOA	ns1.webhosting.jp. sitemgr.webhosting.jp. 2026071401 10800 3600 604800 86400	3600
A	217.114.94.2	3600
MX	10 mxb-00620203.gslb.pphosted.com.	1800
MX	10 mxa-00620203.gslb.pphosted.com.	1800
TXT	"v=spf1 -all"	3600
TXT	"facebook-domain-verification=unuz9f23own4sxvu31f20wljzp3w5g"	3600
TXT	"MS=ms91265508"	3600