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



X

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

Checked:
23.02.2021 12:06:54


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
exploitdiary.com
A
116.126.87.59
Sejong/Sejong-si/South Korea (KR) - SK Broadband Co Ltd
No Hostname found
yes
1
0

AAAA

yes


www.exploitdiary.com
A
116.126.87.59
Sejong/Sejong-si/South Korea (KR) - SK Broadband Co Ltd
No Hostname found
yes
1
0

AAAA

yes


*.exploitdiary.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 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 13.03.2021, 00:00:00 +, Signature-Inception: 20.02.2021, 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: 08.03.2021, 05:00:00 +, Signature-Inception: 23.02.2021, 04:00:00 +, KeyTag 42351, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 58540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.03.2021, 19:24:21 +, Signature-Inception: 19.02.2021, 19: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: exploitdiary.com
exploitdiary.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 "0fhad344g1k5ar7ad6eg6v29q7g1nvtu" between the hashed NSEC3-owner "0fhaa8es9i1ntl967ghuocpakhq9f46o" and the hashed NextOwner "0fhb4lu2hobl0c8eehmvtgmnnavu98oq". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 0fhaa8es9i1ntl967ghuocpakhq9f46o.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.03.2021, 06:22:31 +, Signature-Inception: 22.02.2021, 05:12:31 +, KeyTag 58540, 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 "exploitdiary.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: 01.03.2021, 05:40:44 +, Signature-Inception: 22.02.2021, 04:30:44 +, KeyTag 58540, Signer-Name: com



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.exploitdiary.com
  ns1.whoisdomain.kr

exploitdiary.com
  dns1.yesnic.com / ns1.whoisdomain.kr
211.206.125.156
Seoul/South Korea (KR) - SK Broadband Co Ltd


  dns2.yesnic.com
49.50.165.188
Seongnam-si/Gyeonggi-do/South Korea (KR) - NBP


  dns3.yesnic.com / ns3.whoisdomain.kr
110.45.166.139
Yongsan-dong/Seoul/South Korea (KR) - LG DACOM Corporation


  dns4.yesnic.com
219.251.156.134
Seoul/South Korea (KR) - Korea Internet Security Agency


  ns1.whoisdomain.kr / ns1.whoisdomain.kr
211.206.125.156
Seoul/South Korea (KR) - SK Broadband Co Ltd


  ns2.whoisdomain.kr
49.50.165.188
Seongnam-si/Gyeonggi-do/South Korea (KR) - NBP


  ns3.whoisdomain.kr / ns3.whoisdomain.kr
110.45.166.139
Yongsan-dong/Seoul/South Korea (KR) - LG DACOM Corporation


  ns4.whoisdomain.kr
219.251.156.134
Seoul/South Korea (KR) - Korea Internet Security Agency

com
  a.gtld-servers.net / nnn1-fra8


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-fra8


  d.gtld-servers.net / nnn1-fra8


  e.gtld-servers.net / nnn1-fra8


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-ein1


  k.gtld-servers.net / nnn1-ein1


  l.gtld-servers.net / nnn1-ein4


  m.gtld-servers.net / nnn1-ein5


4. SOA-Entries


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


Domain:exploitdiary.com
Zone-Name:exploitdiary.com
Primary:ns1.whoisdomain.kr
Mail:help.whois.co.kr
Serial:2021021801
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:8


Domain:www.exploitdiary.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://exploitdiary.com/
116.126.87.59 No GZip used - 412 / 474 - 86.92 % possible
200

Html is minified: 120.30 %
0.577
H
small visible content (num chars: 116)
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'> Exploit Diary
Date: Tue, 23 Feb 2021 11:09:52 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
P3P: CP="NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE"
Content-Length: 474
Connection: close
Content-Type: text/html; charset=euc-kr

• http://www.exploitdiary.com/
116.126.87.59 No GZip used - 412 / 474 - 86.92 % possible
200

Html is minified: 120.30 %
0.576
H
small visible content (num chars: 116)
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'> Exploit Diary
Date: Tue, 23 Feb 2021 11:09:53 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
P3P: CP="NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE"
Content-Length: 474
Connection: close
Content-Type: text/html; charset=euc-kr

• https://exploitdiary.com/
116.126.87.59
-14

10.016
T
Timeout - The operation has timed out

• https://www.exploitdiary.com/
116.126.87.59
-14

10.030
T
Timeout - The operation has timed out

• http://exploitdiary.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
116.126.87.59
302
http://exploitdiary.com/
0.550
D
Visible Content:
Date: Tue, 23 Feb 2021 11:10:13 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
P3P: CP="NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE"
Location: /
Content-Length: 0
Connection: close
Content-Type: text/html

• http://www.exploitdiary.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
116.126.87.59
302
http://www.exploitdiary.com/
0.600
D
Visible Content:
Date: Tue, 23 Feb 2021 11:10:14 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
P3P: CP="NOI CURa ADMa DEVa TAIa OUR DELa BUS IND PHY ONL UNI COM NAV INT DEM PRE"
Location: /
Content-Length: 0
Connection: close
Content-Type: text/html

• https://116.126.87.59/
116.126.87.59
-14

10.026
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "exploitdiary.com" is domain, 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: 55723 (complete: 142558)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: exploitdiary.com has only one ip address.
Warning: Only one ip address found: www.exploitdiary.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: exploitdiary.com has no ipv6 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: www.exploitdiary.com has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Dhttp://exploitdiary.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.126.87.59
302
http://exploitdiary.com/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.exploitdiary.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 116.126.87.59
302
http://www.exploitdiary.com/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
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 exploitdiary.com, 1 ip addresses.
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 www.exploitdiary.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
AInfo:: 29 Queries complete, 9 with IPv6, 20 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.
Ok (4 - 8):: An average of 3.6 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 8 different Name Servers found: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr, 4 Name Servers included in Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, 4 Name Servers included in 1 Zone definitions: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr, 1 Name Servers listed in SOA.Primary: ns1.whoisdomain.kr.
AGood: Only one SOA.Primary Name Server found.: ns1.whoisdomain.kr.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.whoisdomain.kr.
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.: dns1.yesnic.com (211.206.125.156): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: dns2.yesnic.com (49.50.165.188): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: dns3.yesnic.com (110.45.166.139): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: dns4.yesnic.com (219.251.156.134): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: ns1.whoisdomain.kr (211.206.125.156): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: ns2.whoisdomain.kr (49.50.165.188): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: ns3.whoisdomain.kr (110.45.166.139): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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.: ns4.whoisdomain.kr (219.251.156.134): Delegation: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, Zone: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr. Name Servers defined in Delegation, missing in Zone: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com.Name Servers defined in Zone, missing in Delegation: ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr.
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: 8 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 8 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 8 Name Servers, 2 Top Level Domains: kr, com
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 8 Name Servers, 1 Countries: KR
AInfo: Ipv4-Subnet-list: 8 Name Servers, 4 different subnets (first Byte): 110., 211., 219., 49., 4 different subnets (first two Bytes): 110.45., 211.206., 219.251., 49.50., 4 different subnets (first three Bytes): 110.45.166., 211.206.125., 219.251.156., 49.50.165.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 8 good Nameserver
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns1.yesnic.com / 211.206.125.156: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns1.whoisdomain.kr). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.whoisdomain.kr: 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.
Nameserver doesn't pass all EDNS-Checks: ns1.whoisdomain.kr / 211.206.125.156: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (ns1.whoisdomain.kr). COOKIE: ok. CLIENTSUBNET: ok.
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

Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. Creating a Letsencrypt certificate via http-01 challenge may not work. 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: 231700 milliseconds, 231.700 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

No CRT - CT-Log entries found


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: dns1.yesnic.com, dns2.yesnic.com, dns3.yesnic.com, dns4.yesnic.com, ns1.whoisdomain.kr, ns2.whoisdomain.kr, ns3.whoisdomain.kr, ns4.whoisdomain.kr

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
dns1.yesnic.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns00.whoisdns.net, ns1.yesnic.com

Answer: ns1.yesnic.com
61.97.184.104
3
dns2.yesnic.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns00.whoisdns.net, ns1.yesnic.com

Answer: ns1.yesnic.com
61.97.184.104
4
dns3.yesnic.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns00.whoisdns.net, ns1.yesnic.com

Answer: ns1.yesnic.com
61.97.184.104
5
dns4.yesnic.com
NS
b.gtld-servers.net (192.33.14.30)

Answer: ns00.whoisdns.net, ns1.yesnic.com

Answer: ns1.yesnic.com
61.97.184.104
6
kr
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: b.dns.kr, c.dns.kr, d.dns.kr, e.dns.kr, f.dns.kr, g.dns.kr
7
ns1.whoisdomain.kr
NS
d.dns.kr (2001:dcc:4::1)

Answer: ns00.whois.co.kr, ns00.whoisdns.net
8
ns2.whoisdomain.kr
NS
d.dns.kr (2001:dcc:4::1)

Answer: ns00.whois.co.kr, ns00.whoisdns.net
9
ns3.whoisdomain.kr
NS
d.dns.kr (2001:dcc:4::1)

Answer: ns00.whois.co.kr, ns00.whoisdns.net
10
ns4.whoisdomain.kr
NS
d.dns.kr (2001:dcc:4::1)

Answer: ns00.whois.co.kr, ns00.whoisdns.net
11
net
NS
b.root-servers.net (2001:500:200::b)

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
12
ns00.whoisdns.net: 115.85.181.16
NS
a.gtld-servers.net (2001:503:a83e::2:30)
13
ns00.whois.co.kr: 61.97.184.104
NS
d.dns.kr (2001:dcc:4::1)
14
dns1.yesnic.com: 211.206.125.156
A
ns00.whoisdns.net (115.85.181.16)
15
dns1.yesnic.com: No AAAA record found
AAAA
ns00.whoisdns.net (115.85.181.16)
16
dns2.yesnic.com: 49.50.165.188
A
ns00.whoisdns.net (115.85.181.16)
17
dns2.yesnic.com: No AAAA record found
AAAA
ns00.whoisdns.net (115.85.181.16)
18
dns3.yesnic.com: 110.45.166.139
A
ns00.whoisdns.net (115.85.181.16)
19
dns3.yesnic.com: No AAAA record found
AAAA
ns00.whoisdns.net (115.85.181.16)
20
dns4.yesnic.com: 219.251.156.134
A
ns00.whoisdns.net (115.85.181.16)
21
dns4.yesnic.com: No AAAA record found
AAAA
ns00.whoisdns.net (115.85.181.16)
22
ns1.whoisdomain.kr: 211.206.125.156
A
ns00.whois.co.kr (61.97.184.104)
23
ns1.whoisdomain.kr: No AAAA record found
AAAA
ns00.whois.co.kr (61.97.184.104)
24
ns2.whoisdomain.kr: 49.50.165.188
A
ns00.whois.co.kr (61.97.184.104)
25
ns2.whoisdomain.kr: No AAAA record found
AAAA
ns00.whois.co.kr (61.97.184.104)
26
ns3.whoisdomain.kr: 110.45.166.139
A
ns00.whois.co.kr (61.97.184.104)
27
ns3.whoisdomain.kr: No AAAA record found
AAAA
ns00.whois.co.kr (61.97.184.104)
28
ns4.whoisdomain.kr: 219.251.156.134
A
ns00.whois.co.kr (61.97.184.104)
29
ns4.whoisdomain.kr: No AAAA record found
AAAA
ns00.whois.co.kr (61.97.184.104)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.exploitdiary.com
0

no CAA entry found
1
0
exploitdiary.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
exploitdiary.com

ok
1
0
www.exploitdiary.com

ok
1
0
_acme-challenge.exploitdiary.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.exploitdiary.com

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

Name Error - The domain name does not exist
1
0
_acme-challenge.www.exploitdiary.com.exploitdiary.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.exploitdiary.com.www.exploitdiary.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=7dace48d-04fd-49cf-9253-d591357bd9bc


Last Result: https://check-your-website.server-daten.de/?q=exploitdiary.com - 2021-02-23 12:06:54


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

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