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



X

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

Checked:
16.09.2020 06:20:20


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pra.lottenc.com
A
210.93.165.70
Seoul/South Korea (KR) - Lotte Data Communication Company
No Hostname found
yes
1
0

AAAA

yes


www.pra.lottenc.com

Name Error
yes
1
0
*.lottenc.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.pra.lottenc.com
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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2020, 00:00:00 +, Signature-Inception: 09.09.2020, 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: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.09.2020, 21:00:00 +, Signature-Inception: 15.09.2020, 20:00:00 +, KeyTag 46594, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24966, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.09.2020, 18:24:21 +, Signature-Inception: 12.09.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: lottenc.com
lottenc.com
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 "tmbnhui3djtmkrk2jd7kr0fg41glfisn" between the hashed NSEC3-owner "tmbn1u0p83lbe7cr0ndlbfl319fgp4dp" and the hashed NextOwner "tmbnqledljcu7gop2l41p1c5ngbeo33i". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner tmbn1u0p83lbe7cr0ndlbfl319fgp4dp.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 19.09.2020, 04:27:56 +, Signature-Inception: 12.09.2020, 03:17:56 +, KeyTag 24966, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "lottenc.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.09.2020, 04:41:59 +, Signature-Inception: 15.09.2020, 03:31:59 +, KeyTag 24966, Signer-Name: com



0 DNSKEY RR found




Zone: pra.lottenc.com
pra.lottenc.com
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.pra.lottenc.com
www.pra.lottenc.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.pra.lottenc.com
  svrns1.bizlotte.com

pra.lottenc.com
  svrns1.bizlotte.com
124.243.17.5
Seoul/South Korea (KR) - Lotte Data Communication Company

lottenc.com
  svrns1.bizlotte.com
124.243.17.5
Seoul/South Korea (KR) - Lotte Data Communication Company


  svrns2.bizlotte.com
124.243.17.129
Seoul/South Korea (KR) - Lotte Data Communication Company

com
  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


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1600229985
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1600230005
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:12


Domain:lottenc.com
Zone-Name:lottenc.com
Primary:svrns1.bizlotte.com
Mail:svrns1.bizlotte.com
Serial:2015082129
Refresh:10800
Retry:3600
Expire:2419200
TTL:900
num Entries:2


Domain:pra.lottenc.com
Zone-Name:lottenc.com
Primary:svrns1.bizlotte.com
Mail:svrns1.bizlotte.com
Serial:2015082129
Refresh:10800
Retry:3600
Expire:2419200
TTL:900
num Entries:1


Domain:www.pra.lottenc.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://pra.lottenc.com/
210.93.165.70
-14

10.013
T
Timeout - The operation has timed out

• https://pra.lottenc.com/
210.93.165.70
-14

10.030
T
Timeout - The operation has timed out

• http://pra.lottenc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
210.93.165.70
-14

10.043
T
Timeout - The operation has timed out
Visible Content:

• https://210.93.165.70/
210.93.165.70
-14

10.030
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "pra.lottenc.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: pra.lottenc.com has only one ip address.
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: pra.lottenc.com has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
ADNS: "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.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain pra.lottenc.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: 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.svrns1.bizlotte.com (124.243.17.5), svrns2.bizlotte.com (124.243.17.129)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: svrns1.bizlotte.com, svrns2.bizlotte.com, 2 Name Servers included in Delegation: svrns1.bizlotte.com, svrns2.bizlotte.com, 1 Name Servers included in 1 Zone definitions: svrns2.bizlotte.com, 1 Name Servers listed in SOA.Primary: svrns1.bizlotte.com.
AGood: Only one SOA.Primary Name Server found.: svrns1.bizlotte.com.
AGood: SOA.Primary Name Server included in the delegation set.: svrns1.bizlotte.com.
XFatal: 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.: svrns1.bizlotte.com (124.243.17.5): Delegation: svrns1.bizlotte.com, svrns2.bizlotte.com, Zone: svrns2.bizlotte.com. Name Servers defined in Delegation, missing in Zone: svrns1.bizlotte.com.
XFatal: 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.: svrns2.bizlotte.com (124.243.17.129): Delegation: svrns1.bizlotte.com, svrns2.bizlotte.com, Zone: svrns2.bizlotte.com. Name Servers defined in Delegation, missing in Zone: svrns1.bizlotte.com.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: bizlotte.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: KR
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 124., 1 different subnets (first two Bytes): 124.243., 1 different subnets (first three Bytes): 124.243.17.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: svrns1.bizlotte.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: 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.

3. Content- and Performance-critical Checks

http://pra.lottenc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 210.93.165.70
-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.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 123006 milliseconds, 123.006 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

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

No CertSpotter - CT-Log entries found


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

Issuerlast 7 daysactivenum Certs
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2179831979
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2019-12-11 23:00:00
2022-02-26 22:59:59
*.lottenc.com, lottenc.com
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: svrns1.bizlotte.com, svrns2.bizlotte.com

QNr.DomainTypeNS used
1
com
NS
f.root-servers.net (2001:500:2f::f)

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
svrns1.bizlotte.com: 124.243.17.5
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: svrns2.bizlotte.com
124.243.17.129


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
pra.lottenc.com
0

no CAA entry found
1
0
lottenc.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
lottenc.com
MS=ms14412411
ok
1
0
lottenc.com
v=spf1 ip4:124.243.13.159 ip4:124.243.13.160 -all
ok
1
0
pra.lottenc.com

ok
1
0
_acme-challenge.pra.lottenc.com

Name Error - The domain name does not exist
1
0
_acme-challenge.pra.lottenc.com.lottenc.com

Name Error - The domain name does not exist
1
0
_acme-challenge.pra.lottenc.com.pra.lottenc.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=22258f1f-fbee-4e8a-8c7a-8c51253f096e


Last Result: https://check-your-website.server-daten.de/?q=pra.lottenc.com - 2020-09-16 06:20:20


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

<a href="https://check-your-website.server-daten.de/?q=pra.lottenc.com" target="_blank">Check this Site: pra.lottenc.com</a>