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




X

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

Checked:
10.07.2024 10:30:26


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jae.energo.kg
A

yes
4
0

A
213.145.145.49
Bishkek/Gorod Bishkek/Kyrgyzstan (KG) - OJSC Kyrgyztelecom
Hostname: 213-145-145-49.static.ktnet.kg
yes
4
0

AAAA

yes


www.jae.energo.kg

Name Error
yes
2
0

A

yes
2
0

AAAA

yes


*.energo.kg
A

yes



AAAA

yes



CNAME

yes


*.jae.energo.kg
A

yes



AAAA

yes



CNAME

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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5613, Flags 256



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: 22.07.2024, 00:00:00 +, Signature-Inception: 01.07.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: kg
kg
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 45982, DigestType 2 and Digest 1kKvjJu3YeA1znekh1C7qmS0HPoHmdjZRJjPozX6E4A=



1 RRSIG RR to validate DS RR found



RRSIG-Owner kg., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.07.2024, 05:00:00 +, Signature-Inception: 10.07.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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3529, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner kg., Algorithm: 8, 1 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:51 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



RRSIG-Owner kg., Algorithm: 8, 1 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:51 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 45982, Signer-Name: kg



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



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



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

Zone: energo.kg
energo.kg
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "energo.kg" and the NextOwner "ENERGO-ES.kg". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found




Zone: jae.energo.kg
jae.energo.kg
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "ENERGO.KG" and the NextOwner "ENERGO-ES.kg". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



0 DNSKEY RR found






Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.

Zone: www.jae.energo.kg
www.jae.energo.kg
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "ENERGO.KG" and the NextOwner "ENERGO-ES.kg". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.



Bitmap: NS, RRSIG, NSEC Validated: RRSIG-Owner energo.kg., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.12.2024, 23:59:54 +, Signature-Inception: 10.07.2024, 04:00:16 +, KeyTag 3529, Signer-Name: kg



Status: Fatal / bogus. NoError+NoDataResult sent, the answer says, the query name exists, the NSEC confirms the existence of the Query Name, but there are not enough informations about wildcards: NoError - there must be a confirmed wildcard expansion to create the query name. Recalculate the zone or update the name server software. Or there is a Man in the middle, who has removed one of the required NSEC-Records, so DNSSEC works.


3. Name Servers

DomainNameserverNS-IP
www.jae.energo.kg
  as.asiainfo.kg / as.asiainfo.kg


  ns1.energo.kg


  proxy.energo.kg

jae.energo.kg
  as.asiainfo.kg / as.asiainfo.kg
195.38.160.38
Bishkek/Gorod Bishkek/Kyrgyzstan (KG) - ASIAINFO Network


 
2a11:a380::195:38:160:38
Bishkek/Gorod Bishkek/Kyrgyzstan (KG) - ASIAINFO TE


  ns1.energo.kg


  proxy.energo.kg
212.42.113.176
Lebedinovka/Chuy Region/Kyrgyzstan (KG) - "ElCat" Ltd.

energo.kg
  as.asiainfo.kg / as.asiainfo.kg
195.38.160.38
Bishkek/Gorod Bishkek/Kyrgyzstan (KG) - ASIAINFO Network


 
2a11:a380::195:38:160:38
Bishkek/Gorod Bishkek/Kyrgyzstan (KG) - ASIAINFO TE


  ns1.energo.kg
212.42.113.176
Lebedinovka/Chuy Region/Kyrgyzstan (KG) - "ElCat" Ltd.


  proxy.energo.kg
212.42.113.176
Lebedinovka/Chuy Region/Kyrgyzstan (KG) - "ElCat" Ltd.

kg
  kg.cctld.authdns.ripe.net / ns2.se-sto.authdns.ripe.net


  ns.kg / ns.kg


  ns2.kg / as.asiainfo.kg


4. SOA-Entries


Domain:kg
Zone-Name:kg
Primary:ns.kg
Mail:adm.infotel.kg
Serial:1720587601
Refresh:1800
Retry:600
Expire:604800
TTL:86400
num Entries:2


Domain:kg
Zone-Name:kg
Primary:ns.kg
Mail:adm.infotel.kg
Serial:1720598401
Refresh:1800
Retry:600
Expire:604800
TTL:86400
num Entries:1


Domain:energo.kg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:energo.kg
Zone-Name:energo.kg
Primary:ns1.energo.kg
Mail:hostmaster.energo.kg
Serial:2015030101
Refresh:3600
Retry:900
Expire:360000
TTL:3600
num Entries:2


Domain:jae.energo.kg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:3


Domain:jae.energo.kg
Zone-Name:jae.energo.kg
Primary:ns1.energo.kg
Mail:hostmaster.energo.kg
Serial:2015030101
Refresh:3600
Retry:900
Expire:360000
TTL:3600
num Entries:1


Domain:www.jae.energo.kg
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:www.jae.energo.kg
Zone-Name:jae.energo.kg
Primary:ns1.energo.kg
Mail:hostmaster.energo.kg
Serial:2015030101
Refresh:3600
Retry:900
Expire:360000
TTL:3600
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://jae.energo.kg/
213.145.145.49
-14

10.014
T
Timeout - The operation has timed out.

• https://jae.energo.kg/
213.145.145.49
-14

10.023
T
Timeout - The operation has timed out.

• http://jae.energo.kg/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
213.145.145.49
-14

10.010
T
Timeout - The operation has timed out.
Visible Content:

• https://213.145.145.49/
213.145.145.49
-14

10.013
T
Timeout - The operation has timed out.

7. Comments


1. General Results, most used to calculate the result

Aname "jae.energo.kg" is subdomain, public suffix is ".kg", top-level-domain is ".kg", top-level-domain-type is "country-code", Country is Kyrgyzstan, tld-manager is "AsiaInfo Telecommunication Enterprise", num .kg-domains preloaded: 21 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: jae.energo.kg 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: jae.energo.kg 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.
XFatal error: Nameserver doesn't support TCP connection: ns.kg: Timeout
XFatal error: Nameserver doesn't support TCP connection: proxy.energo.kg: NXDOMAIN
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 jae.energo.kg, 1 ip addresses.
BNo _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.jae.energo.kg

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

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 1 Name Servers.
AInfo:: 7 Queries complete, 5 with IPv6, 2 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 7.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: as.asiainfo.kg, ns1.energo.kg, proxy.energo.kg, 2 Name Servers included in Delegation: AS.ASIAINFO.KG, PROXY.ENERGO.KG, 3 Name Servers included in 3 Zone definitions: AS.ASIAINFO.KG, PROXY.ENERGO.KG, ns1.energo.kg, 1 Name Servers listed in SOA.Primary: ns1.energo.kg.
AGood: Only one SOA.Primary Name Server found.: ns1.energo.kg.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.energo.kg.
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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: proxy.energo.kg (212.42.113.176): Delegation: AS.ASIAINFO.KG, PROXY.ENERGO.KG, Zone: ns1.energo.kg. Name Servers defined in Delegation, missing in Zone: AS.ASIAINFO.KG, PROXY.ENERGO.KG.Name Servers defined in Zone, missing in Delegation: ns1.energo.kg.
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: Some Name Servers have IPv6 addresses: 1 Name Servers with IPv6 found (1 Name Servers without IPv6)
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: kg
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: KG
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 195., 212., 2 different subnets (first two Bytes): 195.38., 212.42., 2 different subnets (first three Bytes): 195.38.160., 212.42.113.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2a11:, 1 different subnets (first two blocks): 2a11:a380:, 1 different subnets (first three blocks): 2a11:a380:0000:, 1 different subnets (first four blocks): 2a11:a380:0000:0000:
Fatal: All Name Server IPv6 addresses from the same subnet.
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports TCP connections: 3 good Nameserver
AGood: Nameserver supports Echo Capitalization: 3 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 3 good Nameserver
Nameserver doesn't pass all EDNS-Checks: as.asiainfo.kg: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (as.asiainfo.kg). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: as.asiainfo.kg / 195.38.160.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (as.asiainfo.kg). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: as.asiainfo.kg / 195.38.160.38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (as.asiainfo.kg). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: as.asiainfo.kg / 2a11:a380::195:38:160:38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (as.asiainfo.kg). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: as.asiainfo.kg / 2a11:a380::195:38:160:38: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (as.asiainfo.kg). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.energo.kg: 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.energo.kg: 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.

4. Content- and Performance-critical Checks

http://jae.energo.kg/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 213.145.145.49
-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: 1029387 milliseconds, 1029.387 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" > of the last months 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: as.asiainfo.kg, proxy.energo.kg

QNr.DomainTypeNS used
1
kg
NS
k.root-servers.net (2001:7fd::1)

Answer: kg.cctld.authdns.ripe.net, ns.kg, ns2.kg
2
as.asiainfo.kg
NS
kg.cctld.authdns.ripe.net (2001:67c:e0::84)

Answer: dap.asiainfo.kg, das.asiainfo.kg

Answer: dap.asiainfo.kg
195.38.160.44

Answer: das.asiainfo.kg
195.38.160.55
3
proxy.energo.kg
NS
kg.cctld.authdns.ripe.net (2001:67c:e0::84)

Answer: AS.ASIAINFO.KG, PROXY.ENERGO.KG

Answer: AS.ASIAINFO.KG
2a11:a380::195:38:160:38

Answer: PROXY.ENERGO.KG
212.42.113.176
4
as.asiainfo.kg: 195.38.160.38
A
dap.asiainfo.kg (195.38.160.44)
5
as.asiainfo.kg: 2a11:a380::195:38:160:38
AAAA
dap.asiainfo.kg (195.38.160.44)
6
proxy.energo.kg: No A record found
A
as.asiainfo.kg (2a11:a380::195:38:160:38)
7
proxy.energo.kg: No AAAA record found
AAAA
as.asiainfo.kg (2a11:a380::195:38:160:38)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.jae.energo.kg
0

no CAA entry found
1
0
jae.energo.kg
0

no CAA entry found
1
0
energo.kg
0

no CAA entry found
1
0
kg
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
energo.kg

ok
1
0
jae.energo.kg

ok
1
0
www.jae.energo.kg

ok
1
0
_acme-challenge.jae.energo.kg

missing entry or wrong length
1
0
_acme-challenge.www.jae.energo.kg

missing entry or wrong length
1
0
_acme-challenge.jae.energo.kg.energo.kg

perhaps wrong
1
0
_acme-challenge.jae.energo.kg.jae.energo.kg

perhaps wrong
1
0
_acme-challenge.www.jae.energo.kg.jae.energo.kg

perhaps wrong
1
0
_acme-challenge.www.jae.energo.kg.www.jae.energo.kg

perhaps wrong
1
0


15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06)

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=25aff887-b9c6-4f06-938b-baa078caaa5e


Last Result: https://check-your-website.server-daten.de/?q=jae.energo.kg - 2024-07-10 10:30:26


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

<a href="https://check-your-website.server-daten.de/?q=jae.energo.kg" target="_blank">Check this Site: jae.energo.kg</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