Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
04.09.2024 10:58:04

Older results

X - 19.06.2024 18:27:00

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
legy-jp-addr-long.line.naver.jp	A	147.92.146.129 Chiyoda/Tokyo/Japan (JP) - LINE Corporation No Hostname found	yes	1	0
	A	147.92.146.138 Chiyoda/Tokyo/Japan (JP) - LINE Corporation No Hostname found	yes	1	0
	A	147.92.185.1 Chiyoda/Tokyo/Japan (JP) - LINE Corporation No Hostname found	yes	1	0
	A	147.92.185.2 Chiyoda/Tokyo/Japan (JP) - LINE Corporation No Hostname found	yes	1	0
	A	147.92.249.185 Chiyoda/Tokyo/Japan (JP) - LINE Corporation No Hostname found	yes	1	0
	AAAA		yes
www.legy-jp-addr-long.line.naver.jp		Name Error	yes	1	0
*.line.naver.jp	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.legy-jp-addr-long.line.naver.jp	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20038, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2024, 00:00:00 +, Signature-Inception: 30.08.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: jp
jp	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 22111, DigestType 2 and Digest 5aQ1NLm+r7811saz6qHprn/itNiWElISb9Z7UXIyIoY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner jp., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.09.2024, 05:00:00 +, Signature-Inception: 04.09.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20038 used to validate the DS RRSet in the parent zone


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 6876, Flags 256


	Public Key with Algorithm 8, KeyTag 22111, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 60339, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner jp., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 05.10.2024, 18:45:00 +, Signature-Inception: 05.08.2024, 18:45:00 +, KeyTag 22111, Signer-Name: jp


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22111 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 22111, DigestType 2 and Digest "5aQ1NLm+r7811saz6qHprn/itNiWElISb9Z7UXIyIoY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: naver.jp
naver.jp	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "uqddusmc3fm829jfmq191to23onbvjja" between the hashed NSEC3-owner "uqcr93r0c2t760pq0pnnmtkltpp9v977" and the hashed NextOwner "uqdf3ov4parlda3bglqn310s9sepr8of". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner uqcr93r0c2t760pq0pnnmtkltpp9v977.jp., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.09.2024, 17:45:02 +, Signature-Inception: 31.08.2024, 17:45:02 +, KeyTag 60339, Signer-Name: jp


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "b9ccvllht15jm5het57bq8mlbaakpi82" as Owner. That's the Hash of "jp" with the NextHashedOwnerName "b9gclvhjofb3318piq42majldh459sfm". So that domain name is the Closest Encloser of "naver.jp". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner b9ccvllht15jm5het57bq8mlbaakpi82.jp., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 30.09.2024, 17:45:02 +, Signature-Inception: 31.08.2024, 17:45:02 +, KeyTag 60339, Signer-Name: jp


	0 DNSKEY RR found




Zone: line.naver.jp
line.naver.jp	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: legy-jp-addr-long.line.naver.jp
legy-jp-addr-long.line.naver.jp	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.legy-jp-addr-long.line.naver.jp
www.legy-jp-addr-long.line.naver.jp	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.legy-jp-addr-long.line.naver.jp	• adns1.naver.com
legy-jp-addr-long.line.naver.jp	• adns1.naver.com	125.209.248.6 Naju-si/Jeollanam-do/South Korea (KR) - NAVER Cloud Corp.	•
line.naver.jp	• adns1.naver.com	125.209.248.6 Naju-si/Jeollanam-do/South Korea (KR) - NAVER Cloud Corp.	•
naver.jp	• adns1.naver.com	125.209.248.6 Naju-si/Jeollanam-do/South Korea (KR) - NAVER Cloud Corp.	•
	• adns2.naver.com	125.209.249.6 Naju-si/Jeollanam-do/South Korea (KR) - NAVER Cloud Corp.	•
	• ns1.naver.jp	147.92.152.224 Chiyoda/Tokyo/Japan (JP) - LINE Corporation	•
	• ns2.naver.jp	147.92.162.216 Chiyoda/Tokyo/Japan (JP) - LINE Corporation	•
jp	• a.dns.jp		•
	• b.dns.jp		•
	• c.dns.jp		•
	• d.dns.jp		•
	• e.dns.jp		•
	• f.dns.jp		•
	• g.dns.jp		•
	• h.dns.jp		•
	• z.dns.jp

4. SOA-Entries

Domain:	jp
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	jp
Zone-Name:	jp
Primary:	z.dns.jp
Mail:	root.dns.jp
Serial:	1725439502
Refresh:	3600
Retry:	900
Expire:	1814400
TTL:	900
num Entries:	8

Domain:	naver.jp
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	naver.jp
Zone-Name:	naver.jp
Primary:	adns1.naver.com
Mail:	domain.linecorp.com
Serial:	1725433502
Refresh:	3578
Retry:	600
Expire:	604800
TTL:	3600
num Entries:	3

Domain:	line.naver.jp
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	legy-jp-addr-long.line.naver.jp
Zone-Name:	naver.jp
Primary:	adns1.naver.com
Mail:	domain.linecorp.com
Serial:	1725433502
Refresh:	3578
Retry:	600
Expire:	604800
TTL:	3600
num Entries:	1

Domain:	www.legy-jp-addr-long.line.naver.jp
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	Sec.	G
• http://legy-jp-addr-long.line.naver.jp/ 147.92.146.129	-14	10.110	T
Timeout - The operation has timed out.

• http://legy-jp-addr-long.line.naver.jp/ 147.92.146.138	-14	10.014	T
Timeout - The operation has timed out.

• http://legy-jp-addr-long.line.naver.jp/ 147.92.185.1	-14	10.023	T
Timeout - The operation has timed out.

• http://legy-jp-addr-long.line.naver.jp/ 147.92.185.2	-14	10.014	T
Timeout - The operation has timed out.

• http://legy-jp-addr-long.line.naver.jp/ 147.92.249.185	-14	10.017	T
Timeout - The operation has timed out.

• https://legy-jp-addr-long.line.naver.jp/ 147.92.146.129	404	8.870	M
Not Found
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://legy-jp-addr-long.line.naver.jp/ 147.92.146.138	404	8.743	M
Not Found
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://legy-jp-addr-long.line.naver.jp/ 147.92.185.1	404	8.750	M
Not Found
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://legy-jp-addr-long.line.naver.jp/ 147.92.185.2	404	8.774	M
Not Found
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://legy-jp-addr-long.line.naver.jp/ 147.92.249.185	404	8.853	M
Not Found
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.146.129	-14	10.017	T
Timeout - The operation has timed out.
Visible Content:

• http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.146.138	-14	10.010	T
Timeout - The operation has timed out.
Visible Content:

• http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.185.1	-14	10.013	T
Timeout - The operation has timed out.
Visible Content:

• http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.185.2	-14	10.010	T
Timeout - The operation has timed out.
Visible Content:

• http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.249.185	-14	10.017	T
Timeout - The operation has timed out.
Visible Content:

• https://147.92.185.1/ 147.92.185.1	404	8.667	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://147.92.185.2/ 147.92.185.2	404	8.750	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://147.92.146.129/ 147.92.146.129	404	8.750	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://147.92.146.138/ 147.92.146.138	404	8.740	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

• https://147.92.249.185/ 147.92.249.185	404	8.807	N
Not Found
Certificate error: RemoteCertificateNameMismatch
Server: legy
x-line-http: P,LP,HC
x-lcr: 290
Content-Length: 0

7. Comments

	1. General Results, most used to calculate the result
A	name "legy-jp-addr-long.line.naver.jp" is subdomain, public suffix is ".jp", top-level-domain is ".jp", top-level-domain-type is "country-code", Country is Japan, tld-manager is "Japan Registry Services Co., Ltd.", num .jp-domains preloaded: 1238 (complete: 245733)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: legy-jp-addr-long.line.naver.jp has 5 different ip addresses (authoritative).
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: legy-jp-addr-long.line.naver.jp has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
B	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.129	404		Missing HSTS-Header
B	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.138	404		Missing HSTS-Header
B	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.1	404		Missing HSTS-Header
B	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.2	404		Missing HSTS-Header
B	https://legy-jp-addr-long.line.naver.jp/ 147.92.249.185	404		Missing HSTS-Header
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
M	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.129	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.138	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.1	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.2	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://legy-jp-addr-long.line.naver.jp/ 147.92.249.185	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://147.92.146.129/ 147.92.146.129	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://147.92.146.138/ 147.92.146.138	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://147.92.185.1/ 147.92.185.1	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://147.92.185.2/ 147.92.185.2	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://147.92.249.185/ 147.92.249.185	404		Misconfiguration - main pages should never send http status 400 - 499
N	https://147.92.146.129/ 147.92.146.129	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
N	https://147.92.146.138/ 147.92.146.138	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
N	https://147.92.185.1/ 147.92.185.1	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
N	https://147.92.185.2/ 147.92.185.2	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
N	https://147.92.249.185/ 147.92.249.185	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain legy-jp-addr-long.line.naver.jp, 5 ip addresses.
	Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain legy-jp-addr-long.line.naver.jp, 5 ip addresses, 1 different http results.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.legy-jp-addr-long.line.naver.jp
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
F	legy-jp-addr-long.line.naver.jp 147.92.146.129	Content-Security-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.129	X-Content-Type-Options		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.129	Referrer-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.129	Permissions-Policy		Critical: Missing Header:
B	legy-jp-addr-long.line.naver.jp 147.92.146.129	Cross-Origin-Embedder-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.146.129	Cross-Origin-Opener-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.146.129	Cross-Origin-Resource-Policy		Info: Missing Header
F	legy-jp-addr-long.line.naver.jp 147.92.146.138	Content-Security-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.138	X-Content-Type-Options		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.138	Referrer-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.146.138	Permissions-Policy		Critical: Missing Header:
B	legy-jp-addr-long.line.naver.jp 147.92.146.138	Cross-Origin-Embedder-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.146.138	Cross-Origin-Opener-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.146.138	Cross-Origin-Resource-Policy		Info: Missing Header
F	legy-jp-addr-long.line.naver.jp 147.92.185.1	Content-Security-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.1	X-Content-Type-Options		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.1	Referrer-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.1	Permissions-Policy		Critical: Missing Header:
B	legy-jp-addr-long.line.naver.jp 147.92.185.1	Cross-Origin-Embedder-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.185.1	Cross-Origin-Opener-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.185.1	Cross-Origin-Resource-Policy		Info: Missing Header
F	legy-jp-addr-long.line.naver.jp 147.92.185.2	Content-Security-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.2	X-Content-Type-Options		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.2	Referrer-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.185.2	Permissions-Policy		Critical: Missing Header:
B	legy-jp-addr-long.line.naver.jp 147.92.185.2	Cross-Origin-Embedder-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.185.2	Cross-Origin-Opener-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.185.2	Cross-Origin-Resource-Policy		Info: Missing Header
F	legy-jp-addr-long.line.naver.jp 147.92.249.185	Content-Security-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.249.185	X-Content-Type-Options		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.249.185	Referrer-Policy		Critical: Missing Header:
F	legy-jp-addr-long.line.naver.jp 147.92.249.185	Permissions-Policy		Critical: Missing Header:
B	legy-jp-addr-long.line.naver.jp 147.92.249.185	Cross-Origin-Embedder-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.249.185	Cross-Origin-Opener-Policy		Info: Missing Header
B	legy-jp-addr-long.line.naver.jp 147.92.249.185	Cross-Origin-Resource-Policy		Info: Missing Header
	3. DNS- and NameServer - Checks
A	Info:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 9 Queries complete, 5 with IPv6, 4 with IPv4.
	Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
A	Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.naver.jp (147.92.152.224), ns2.naver.jp (147.92.162.216)
A	Good (1 - 3.0):: An average of 2.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp, 3 Name Servers included in Delegation: adns1.naver.com, ns1.naver.jp, ns2.naver.jp, 4 Name Servers included in 1 Zone definitions: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp, 1 Name Servers listed in SOA.Primary: adns1.naver.com.
A	Good: Only one SOA.Primary Name Server found.: adns1.naver.com.
A	Good: SOA.Primary Name Server included in the delegation set.: adns1.naver.com.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: adns1.naver.com (125.209.248.6): Delegation: adns1.naver.com, ns1.naver.jp, ns2.naver.jp, Zone: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp. Name Servers defined in Zone, missing in Delegation: adns2.naver.com.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: adns2.naver.com (125.209.249.6): Delegation: adns1.naver.com, ns1.naver.jp, ns2.naver.jp, Zone: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp. Name Servers defined in Zone, missing in Delegation: adns2.naver.com.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.naver.jp (147.92.152.224): Delegation: adns1.naver.com, ns1.naver.jp, ns2.naver.jp, Zone: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp. Name Servers defined in Zone, missing in Delegation: adns2.naver.com.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.naver.jp (147.92.162.216): Delegation: adns1.naver.com, ns1.naver.jp, ns2.naver.jp, Zone: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp. Name Servers defined in Zone, missing in Delegation: adns2.naver.com.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
	Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 different Name Servers found
A	Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 2 Top Level Domains: jp, com
A	Good: Name Servers with different domain names found.: 2 different Domains found
A	Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: JP, KR
A	Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 125., 147., 2 different subnets (first two Bytes): 125.209., 147.92., 4 different subnets (first three Bytes): 125.209.248., 125.209.249., 147.92.152., 147.92.162.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Good: Nameserver supports TCP connections: 1 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 1 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.146.129	-14		Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.146.138	-14		Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.185.1	-14		Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.185.2	-14		Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://legy-jp-addr-long.line.naver.jp/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 147.92.249.185	-14		Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.129	404	8.870 seconds	Warning: 404 needs more then one second
	https://legy-jp-addr-long.line.naver.jp/ 147.92.146.138	404	8.743 seconds	Warning: 404 needs more then one second
	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.1	404	8.750 seconds	Warning: 404 needs more then one second
	https://legy-jp-addr-long.line.naver.jp/ 147.92.185.2	404	8.774 seconds	Warning: 404 needs more then one second
	https://legy-jp-addr-long.line.naver.jp/ 147.92.249.185	404	8.853 seconds	Warning: 404 needs more then one second
	https://147.92.146.129/ 147.92.146.129	404	8.750 seconds	Warning: 404 needs more then one second
	https://147.92.146.138/ 147.92.146.138	404	8.740 seconds	Warning: 404 needs more then one second
	https://147.92.185.1/ 147.92.185.1	404	8.667 seconds	Warning: 404 needs more then one second
	https://147.92.185.2/ 147.92.185.2	404	8.750 seconds	Warning: 404 needs more then one second
	https://147.92.249.185/ 147.92.249.185	404	8.807 seconds	Warning: 404 needs more then one second
A	Duration: 1035997 milliseconds, 1035.997 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

legy-jp-addr-long.line.naver.jp

147.92.146.129

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

legy-jp-addr-long.line.naver.jp

147.92.146.129

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

legy-jp-addr-long.line.naver.jp

147.92.146.138

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

legy-jp-addr-long.line.naver.jp

147.92.146.138

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

legy-jp-addr-long.line.naver.jp

147.92.185.1

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

legy-jp-addr-long.line.naver.jp

147.92.185.1

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

legy-jp-addr-long.line.naver.jp

147.92.185.2

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

legy-jp-addr-long.line.naver.jp

147.92.185.2

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

legy-jp-addr-long.line.naver.jp

147.92.249.185

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

legy-jp-addr-long.line.naver.jp

147.92.249.185

443

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
No SNI required - domain included in main certificate

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

147.92.185.1

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

147.92.185.1

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

147.92.185.2

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

147.92.185.2

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

147.92.146.129

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

147.92.146.129

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

147.92.146.138

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

147.92.146.138

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

147.92.249.185

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

147.92.249.185

443

name does not match

Tls12

ECDH Ephermal

256

Aes128

128

Sha256

not supported

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

http/2 via ALPN supported
Cert sent without SNI

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Chain - incomplete	1	CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, C=JP, ST=Tokyo
	2	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

9. Certificates

CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, S=Tokyo, C=JP

03.01.2024

03.02.2025
expires in 146 days

*.line.naver.jp, line.naver.jp - 2 entries

CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, S=Tokyo, C=JP

03.01.2024

03.02.2025
expires in 146 days

*.line.naver.jp, line.naver.jp - 2 entries

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	3E6CC0798923683E5BB9A264
Thumbprint:	08C2CD51FAFBCEE5150A4051B119D893E45DD3F4
SHA256 / Certificate:	nXMktcDvolTSFpN2BDSz9zpXTlWhKmJMwOA/PJ8Bjtc=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	6e65acd57a3e16f3b3c979c19bce68605c7d77a68b23c7118f07180b43e1499c
SHA256 hex / Subject Public Key Information (SPKI):	6e65acd57a3e16f3b3c979c19bce68605c7d77a68b23c7118f07180b43e1499c (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.globalsign.com/gsrsaovsslca2018
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, S=Tokyo, C=JP

03.01.2024

03.02.2025
expires in 146 days

*.line.naver.jp, line.naver.jp - 2 entries

CN=*.line.naver.jp, O=LY Corporation, L=Chiyoda-ku, S=Tokyo, C=JP

03.01.2024

03.02.2025
expires in 146 days

*.line.naver.jp, line.naver.jp - 2 entries

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	3E6CC0798923683E5BB9A264
Thumbprint:	08C2CD51FAFBCEE5150A4051B119D893E45DD3F4
SHA256 / Certificate:	nXMktcDvolTSFpN2BDSz9zpXTlWhKmJMwOA/PJ8Bjtc=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	6e65acd57a3e16f3b3c979c19bce68605c7d77a68b23c7118f07180b43e1499c
SHA256 hex / Subject Public Key Information (SPKI):	6e65acd57a3e16f3b3c979c19bce68605c7d77a68b23c7118f07180b43e1499c (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.globalsign.com/gsrsaovsslca2018
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)

CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

21.11.2018

21.11.2028
expires in 1533 days

CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

21.11.2018

21.11.2028
expires in 1533 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	01EE5F221DFC623BD4333A8557
Thumbprint:	DFE83023062B997682708B4EAB8E819AFF5D9775
SHA256 / Certificate:	tnb/oxeeiBIJOhter+6HauemqvIxB42tG/shzSiTdko=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SHA256 hex / Subject Public Key Information (SPKI):	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Check unknown. No result 404 / 200
OCSP - Url:	http://ocsp2.globalsign.com/rootr3
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

21.11.2018

21.11.2028
expires in 1533 days

CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE

21.11.2018

21.11.2028
expires in 1533 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	01EE5F221DFC623BD4333A8557
Thumbprint:	DFE83023062B997682708B4EAB8E819AFF5D9775
SHA256 / Certificate:	tnb/oxeeiBIJOhter+6HauemqvIxB42tG/shzSiTdko=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SHA256 hex / Subject Public Key Information (SPKI):	8444e9815bda2c2d1bbdc186dedd1cbaa887bebe17c8fd8c4f00a2aa18115b05
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp2.globalsign.com/rootr3
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3

19.09.2018

28.01.2028
expires in 1235 days

CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3

19.09.2018

28.01.2028
expires in 1235 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	01EE5F169DFF97352B6465D66A
Thumbprint:	0BBFAB97059595E8D1EC48E89EB8657C0E5AAE71
SHA256 / Certificate:	RF7seLxhIVBEoDeWVqotXbXkL3bLcLjRTCB3qpQ9Trs=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SHA256 hex / Subject Public Key Information (SPKI):	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.globalsign.com/rootr1
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3

18.03.2009

18.03.2029
expires in 1650 days

CN=GlobalSign, O=GlobalSign, OU=GlobalSign Root CA - R3

18.03.2009

18.03.2029
expires in 1650 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	04000000000121585308A2
Thumbprint:	D69B561148F01C77C54578C10926DF5B856976AD
SHA256 / Certificate:	y7Ui17fxJ61qAROGW98c1BAufQdZr2NafPRyDcljxTs=
SHA256 hex / Cert (DANE * 0 1):	cbb522d7b7f127ad6a0113865bdf1cd4102e7d0759af635a7cf4720dc963c53b
SHA256 hex / PublicKey (DANE * 1 1):	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SHA256 hex / Subject Public Key Information (SPKI):	706bb1017c855c59169bad5c1781cf597f12d2cad2f63d1a4aa37493800ffb80
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE

01.09.1998

28.01.2028
expires in 1235 days

CN=GlobalSign Root CA, OU=Root CA, O=GlobalSign nv-sa, C=BE

01.09.1998

28.01.2028
expires in 1235 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	040000000001154B5AC394
Thumbprint:	B1BC968BD4F49D622AA89A81F2150152A41D829C
SHA256 / Certificate:	69QQQOS7PsdCyeOB0x7ypBpItmhclufO88HfbNQzHJk=
SHA256 hex / Cert (DANE * 0 1):	ebd41040e4bb3ec742c9e381d31ef2a41a48b6685c96e7cef3c1df6cd4331c99
SHA256 hex / PublicKey (DANE * 1 1):	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64
SHA256 hex / Subject Public Key Information (SPKI):	2bcee858158cf5465fc9d76f0dfa312fef25a4dca8501da9b46b67d1fbfa1b64
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuer				last 7 days	active	num Certs
CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US				0	2	3
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE				0	2	3
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	3
CN=Amazon RSA 2048 M02, O=Amazon, C=US				0	1	1
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US				0	0	1
CN=Amazon RSA 2048 M01, O=Amazon, C=US				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
8013073354 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2024-08-24 00:00:00	2025-08-27 23:59:59	*.line.naver.jp, line.naver.jp - 2 entries
7884875254 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2024-08-07 00:22:01	2025-02-03 01:06:01	*.line.naver.jp, line.naver.jp - 2 entries
6495554182 precert	CN=Amazon RSA 2048 M02, O=Amazon, C=US	2024-01-04 00:00:00	2025-02-01 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-apps-beta.com, .line-beta.me, .linecorp.com, .linegame.jp, .line-scdn.net, *.naver.jp, rr.img.line.naver.jp, rr.img.naver.jp, rr.img1.naver.jp - 12 entries
6488370203 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2024-01-03 01:06:02	2025-02-03 01:06:01	*.line.naver.jp, line.naver.jp - 2 entries
6175316647 precert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-11-13 00:00:00	2024-11-13 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-scdn.net, *.line-website.com, dl-hsp.profile.line.naver.jp, line-apps.com - 7 entries
6049439546 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2023-10-22 00:00:00	2024-10-22 23:59:59	*.line.naver.jp, line.naver.jp - 2 entries
4770040968 precert	CN=Amazon RSA 2048 M01, O=Amazon, C=US	2023-02-03 00:00:00	2024-03-03 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-apps-beta.com, .line-beta.me, .linecorp.com, .linegame.jp, .line-scdn.net, *.naver.jp, rr.img.line.naver.jp, rr.img.naver.jp, rr.img1.naver.jp - 12 entries
4666633526 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-01-11 00:00:00	2024-01-11 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-scdn.net, *.line-website.com, dl-hsp.profile.line.naver.jp, line-apps.com - 7 entries
4575942924 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2022-12-21 01:06:03	2024-01-22 01:06:02	*.line.naver.jp, line.naver.jp - 2 entries
4563067197 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2022-12-18 00:00:00	2023-12-20 23:59:59	*.line.naver.jp, line.naver.jp - 2 entries
3501761384 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-03-10 00:00:00	2023-03-11 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-scdn.net, *.line-website.com, dl-hsp.profile.line.naver.jp, line-apps.com - 7 entries
3485839406 leaf cert	CN=Amazon, OU=Server CA 1B, O=Amazon, C=US	2022-03-05 00:00:00	2023-04-03 23:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-apps-beta.com, .line-beta.me, .linecorp.com, .linegame.jp, .line-scdn.net, *.naver.jp, rr.img.line.naver.jp, rr.img.naver.jp, rr.img1.naver.jp - 12 entries

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US				0	2	3
CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE				0	2	3
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	1	2
CN=Amazon RSA 2048 M02, O=Amazon, C=US				0	1	1
CN=Amazon RSA 2048 M01, O=Amazon, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
14261116861 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2024-08-23 22:00:00	2025-08-27 21:59:59	*.line.naver.jp, line.naver.jp 2 entries
14024964006 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2024-08-06 22:22:01	2025-02-03 00:06:01	*.line.naver.jp, line.naver.jp 2 entries
11626115303 precert	CN=Amazon RSA 2048 M02, O=Amazon, C=US	2024-01-03 23:00:00	2025-02-01 22:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-apps-beta.com, .line-beta.me, .linecorp.com, .linegame.jp, .line-scdn.net, *.naver.jp, rr.img.line.naver.jp, rr.img.naver.jp, rr.img1.naver.jp 12 entries
11578237108 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2024-01-03 00:06:02	2025-02-03 00:06:01	*.line.naver.jp, line.naver.jp 2 entries
13816708774 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-11-12 23:00:00	2024-11-13 22:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-scdn.net, *.line-website.com, dl-hsp.profile.line.naver.jp, line-apps.com 7 entries
10856511662 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2023-10-21 22:00:00	2024-10-22 21:59:59	*.line.naver.jp, line.naver.jp 2 entries
8562087347 precert	CN=Amazon RSA 2048 M01, O=Amazon, C=US	2023-02-02 23:00:00	2024-03-03 22:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-apps-beta.com, .line-beta.me, .linecorp.com, .linegame.jp, .line-scdn.net, *.naver.jp, rr.img.line.naver.jp, rr.img.naver.jp, rr.img1.naver.jp 12 entries
10023130428 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2023-01-10 23:00:00	2024-01-11 22:59:59	.line.me, .line.naver.jp, .line-apps.com, .line-scdn.net, *.line-website.com, dl-hsp.profile.line.naver.jp, line-apps.com 7 entries
8248721281 precert	CN=GlobalSign RSA OV SSL CA 2018, O=GlobalSign nv-sa, C=BE	2022-12-21 00:06:03	2024-01-22 00:06:02	*.line.naver.jp, line.naver.jp 2 entries
8225452981 precert	CN=GeoTrust RSA CA 2018, OU=www.digicert.com, O=DigiCert Inc, C=US	2022-12-17 23:00:00	2023-12-20 22:59:59	*.line.naver.jp, line.naver.jp 2 entries

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: adns1.naver.com, adns2.naver.com, ns1.naver.jp, ns2.naver.jp

QNr.	Domain	Type	NS used
1	com	NS	d.root-servers.net (2001:500:2d::d)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	adns1.naver.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.naver.com, ns2.naver.com
	Answer: ns1.naver.com 125.209.248.6
	Answer: ns2.naver.com 125.209.249.6
3	adns2.naver.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.naver.com, ns2.naver.com
	Answer: ns1.naver.com 125.209.248.6
	Answer: ns2.naver.com 125.209.249.6
4	jp	NS	h.root-servers.net (2001:500:1::53)
	Answer: a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp, e.dns.jp, f.dns.jp, g.dns.jp, h.dns.jp
5	ns1.naver.jp: 147.92.152.224	NS	a.dns.jp (2001:dc4::1)
	Answer: ns2.naver.jp 147.92.162.216
6	adns1.naver.com: 125.209.248.6	A	ns1.naver.com (125.209.248.6)
7	adns1.naver.com: No AAAA record found	AAAA	ns1.naver.com (125.209.248.6)
8	adns2.naver.com: 125.209.249.6	A	ns1.naver.com (125.209.248.6)
9	adns2.naver.com: No AAAA record found	AAAA	ns1.naver.com (125.209.248.6)

13. CAA - Entries

Domainname	Value	∑ Queries
legy-jp-addr-long.line.naver.jp	no CAA entry found	1
line.naver.jp	no CAA entry found	1
naver.jp	no CAA entry found	1
jp	no CAA entry found	1

14. TXT - Entries

Domainname	Status	∑ Queries
line.naver.jp	ok	1
legy-jp-addr-long.line.naver.jp	ok	1
_acme-challenge.legy-jp-addr-long.line.naver.jp	Name Error - The domain name does not exist	1
_acme-challenge.legy-jp-addr-long.line.naver.jp.line.naver.jp	Name Error - The domain name does not exist	1
_acme-challenge.legy-jp-addr-long.line.naver.jp.legy-jp-addr-long.line.naver.jp	Name Error - The domain name does not exist	1

15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06, SMTP-TLS-Reporting is alpa - 2024-07-13)

No DomainServiceEntries entries found

16. Cipher Suites

Summary
Domain	IP	Port	num Ciphers	time	Std.Protocol	Forward Secrecy
legy-jp-addr-long.line.naver.jp	147.92.146.129	443	4 Ciphers	126.96 sec		0 without, 4 FS	100.00 %
legy-jp-addr-long.line.naver.jp	147.92.146.138	443	4 Ciphers	126.01 sec		0 without, 4 FS	100.00 %
legy-jp-addr-long.line.naver.jp	147.92.185.1	443	4 Ciphers	128.16 sec		0 without, 4 FS	100.00 %
legy-jp-addr-long.line.naver.jp	147.92.185.2	443	4 Ciphers	127.88 sec		0 without, 4 FS	100.00 %
legy-jp-addr-long.line.naver.jp	147.92.249.185	443	4 Ciphers	129.19 sec		0 without, 4 FS	100.00 %
Complete		5	20 Ciphers 4.00 Ciphers/Check	638.21 sec	127.64 sec/Check	0 without, 20 FS	100.00 %

Details
Domain	IP	Port	Cipher (OpenSsl / IANA)
legy-jp-addr-long.line.naver.jp	147.92.146.129	443	ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
4 Ciphers, 126.96 sec			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
			ECDHE-RSA-AES128-SHA		(Weak)	TLSv1	0xC0,0x13	FS
			TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
			ECDH		RSA	AES(128)	SHA1
			DHE-RSA-AES128-SHA		(Weak)	SSLv3	0x00,0x33	FS
			TLS_DHE_RSA_WITH_AES_128_CBC_SHA
			DH		RSA	AES(128)	SHA1
	147.92.146.138	443	ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
4 Ciphers, 126.01 sec			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
			ECDHE-RSA-AES128-SHA		(Weak)	TLSv1	0xC0,0x13	FS
			TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
			ECDH		RSA	AES(128)	SHA1
			DHE-RSA-AES128-SHA		(Weak)	SSLv3	0x00,0x33	FS
			TLS_DHE_RSA_WITH_AES_128_CBC_SHA
			DH		RSA	AES(128)	SHA1
	147.92.185.1	443	ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
4 Ciphers, 128.16 sec			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
			ECDHE-RSA-AES128-SHA		(Weak)	TLSv1	0xC0,0x13	FS
			TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
			ECDH		RSA	AES(128)	SHA1
			DHE-RSA-AES128-SHA		(Weak)	SSLv3	0x00,0x33	FS
			TLS_DHE_RSA_WITH_AES_128_CBC_SHA
			DH		RSA	AES(128)	SHA1
	147.92.185.2	443	ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
4 Ciphers, 127.88 sec			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
			ECDHE-RSA-AES128-SHA		(Weak)	TLSv1	0xC0,0x13	FS
			TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
			ECDH		RSA	AES(128)	SHA1
			DHE-RSA-AES128-SHA		(Weak)	SSLv3	0x00,0x33	FS
			TLS_DHE_RSA_WITH_AES_128_CBC_SHA
			DH		RSA	AES(128)	SHA1
	147.92.249.185	443	ECDHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0xC0,0x2F	FS
4 Ciphers, 129.19 sec			TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
			ECDH		RSA	AESGCM(128)	AEAD
			DHE-RSA-AES128-GCM-SHA256		(Secure)	TLSv1.2	0x00,0x9E	FS
			TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
			DH		RSA	AESGCM(128)	AEAD
			ECDHE-RSA-AES128-SHA		(Weak)	TLSv1	0xC0,0x13	FS
			TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
			ECDH		RSA	AES(128)	SHA1
			DHE-RSA-AES128-SHA		(Weak)	SSLv3	0x00,0x33	FS
			TLS_DHE_RSA_WITH_AES_128_CBC_SHA
			DH		RSA	AES(128)	SHA1

17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=237ba0cf-2142-4108-915e-8492616e94a5

Last Result: https://check-your-website.server-daten.de/?q=legy-jp-addr-long.line.naver.jp - 2024-09-04 10:58:04

Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=legy-jp-addr-long.line.naver.jp" target="_blank">Check this Site: legy-jp-addr-long.line.naver.jp</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=legy-jp-addr-long.line.naver.jp

Check DNS, Urls + Redirects, Certificates and Content of your Website

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

11. Html-Content - Entries

12. Nameserver - IP-Adresses

13. CAA - Entries

14. TXT - Entries

15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06, SMTP-TLS-Reporting is alpa - 2024-07-13)

16. Cipher Suites

17. Portchecks