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




X

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

Checked:
15.05.2024 11:06:50


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
onion.ly
A
209.141.39.59
Las Vegas/Nevada/United States (US) - FranTech Solutions
No Hostname found
yes
1
0

AAAA

yes


www.onion.ly
A
209.141.39.59
Las Vegas/Nevada/United States (US) - FranTech Solutions
No Hostname found
yes
1
0

AAAA

yes


*.onion.ly
A
209.141.39.59
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5613, 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: 01.06.2024, 00:00:00 +, Signature-Inception: 11.05.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: ly
ly
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 62311, DigestType 2 and Digest COmsVvYFpyjQSMgDeHqwRLDIHK6iAx6snt6ncVChvb4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ly., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 28.05.2024, 05:00:00 +, Signature-Inception: 15.05.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 15271, Flags 256



Public Key with Algorithm 8, KeyTag 59151, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ly., Algorithm: 8, 1 Labels, original TTL: 172800 sec, Signature-expiration: 28.05.2024, 18:00:00 +, Signature-Inception: 11.05.2024, 18:00:00 +, KeyTag 62311, Signer-Name: ly



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



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

Zone: onion.ly
onion.ly
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 "lsff7mfoporfo86rq4igujv2sa7q4nm8" between the hashed NSEC3-owner "lotpsqvriiivuau1ntq9i58dh01fb9dm" and the hashed NextOwner "n5m05fd66gv7315venjsg0i1op0ftei9". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner lotpsqvriiivuau1ntq9i58dh01fb9dm.ly., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 21.05.2024, 07:00:00 +, Signature-Inception: 04.05.2024, 07:00:00 +, KeyTag 59151, Signer-Name: ly



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "qm4tdng76q673jehubmr82blvob78uh0" as Owner. That's the Hash of "ly" with the NextHashedOwnerName "r6hkfn314d18s92dl5gpm4sqrshn9cm1". So that domain name is the Closest Encloser of "onion.ly". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner qm4tdng76q673jehubmr82blvob78uh0.ly., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 21.05.2024, 07:00:00 +, Signature-Inception: 04.05.2024, 07:00:00 +, KeyTag 59151, Signer-Name: ly



0 DNSKEY RR found




Zone: www.onion.ly
www.onion.ly
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.onion.ly
  ns1.linode.com

onion.ly
  ns1.linode.com
92.123.94.2
Milan/Lombardy/Italy (IT) - Akamai Technologies


 
2600:14c0:6::2
Secaucus/New Jersey/United States (US) - Akamai International B.V.


T  ns2.linode.com
92.123.94.3
Milan/Lombardy/Italy (IT) - Akamai Technologies


 
2600:14c0:6::3
Secaucus/New Jersey/United States (US) - Akamai International B.V.


  ns3.linode.com
92.123.95.3
Milan/Lombardy/Italy (IT) - Akamai Technologies


 
2600:14c0:7::3
Piscataway/New Jersey/United States (US) - Akamai International B.V.


  ns4.linode.com
92.123.95.4
Milan/Lombardy/Italy (IT) - Akamai Technologies


 
2600:14c0:7::4
Piscataway/New Jersey/United States (US) - Akamai International B.V.


  ns5.linode.com
92.123.95.2
Milan/Lombardy/Italy (IT) - Akamai Technologies


 
2600:14c0:7::2
Piscataway/New Jersey/United States (US) - Akamai International B.V.

ly
  dns.lttnet.net


  dns1.lttnet.net


  ns-ly.afrinic.net / s01-ns2.pkl


  pch.ltt.ly / 4.ams.pch


  phloem.uoregon.edu


4. SOA-Entries


Domain:ly
Zone-Name:ly
Primary:dns.lttnet.net
Mail:khaleds.lttnet.net
Serial:2024051508
Refresh:3600
Retry:900
Expire:604800
TTL:600
num Entries:2


Domain:ly
Zone-Name:ly
Primary:dns.lttnet.net
Mail:khaleds.lttnet.net
Serial:2024051509
Refresh:3600
Retry:900
Expire:604800
TTL:600
num Entries:3


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


Domain:onion.ly
Zone-Name:onion.ly
Primary:ns1.linode.com
Mail:admin.onion.casa
Serial:2021000073
Refresh:14400
Retry:14400
Expire:1209600
TTL:86400
num Entries:9


Domain:www.onion.ly
Zone-Name:onion.ly
Primary:ns1.linode.com
Mail:admin.onion.casa
Serial:2021000073
Refresh:14400
Retry:14400
Expire:1209600
TTL:86400
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://onion.ly/
209.141.39.59
-14

10.013
T
Timeout - The operation has timed out.

• http://www.onion.ly/
209.141.39.59
-14

10.010
T
Timeout - The operation has timed out.

• https://onion.ly/
209.141.39.59
-14

10.010
T
Timeout - The operation has timed out.

• https://www.onion.ly/
209.141.39.59
-14

10.013
T
Timeout - The operation has timed out.

• http://onion.ly/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
209.141.39.59
-14

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

• http://www.onion.ly/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
209.141.39.59
-14

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

• https://209.141.39.59/
209.141.39.59
-14

10.014
T
Timeout - The operation has timed out.

7. Comments


1. General Results, most used to calculate the result

Aname "onion.ly" is domain, public suffix is ".ly", top-level-domain is ".ly", top-level-domain-type is "country-code", Country is Libya, tld-manager is "General Post and Telecommunication Company", num .ly-domains preloaded: 24 (complete: 244198)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: onion.ly has only one ip address.
Warning: Only one ip address found: www.onion.ly 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: onion.ly 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.onion.ly has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
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: dns.lttnet.net: Timeout
XFatal error: Nameserver doesn't support TCP connection: dns1.lttnet.net: Timeout
XFatal error: Nameserver doesn't support TCP connection: ns5.linode.com / 2600:14c0:7::2: Fatal error (0)
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 onion.ly, 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.onion.ly, 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.onion.ly

2. Header-Checks

U

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

3. DNS- and NameServer - Checks

AInfo:: 38 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
AInfo:: 38 Queries complete, 38 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 7.6 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 5 different Name Servers found: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com, 2 Name Servers included in Delegation: ns1.linode.com, ns2.linode.com, 5 Name Servers included in 1 Zone definitions: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com, 1 Name Servers listed in SOA.Primary: ns1.linode.com.
AGood: Only one SOA.Primary Name Server found.: ns1.linode.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.linode.com (92.123.94.2): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.linode.com (2600:14c0:6::2): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.linode.com (92.123.94.3): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.linode.com (2600:14c0:6::3): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.linode.com (92.123.95.3): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.linode.com (2600:14c0:7::3): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.linode.com (92.123.95.4): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns4.linode.com (2600:14c0:7::4): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.linode.com (92.123.95.2): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns5.linode.com (2600:14c0:7::2): Delegation: ns1.linode.com, ns2.linode.com, Zone: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com. Name Servers defined in Zone, missing in Delegation: ns3.linode.com, ns4.linode.com, ns5.linode.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: 5 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 5 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.: 5 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: linode.com
AGood: Name servers with different Country locations found: 5 Name Servers, 2 Countries: IT, US
AInfo: Ipv4-Subnet-list: 5 Name Servers, 1 different subnets (first Byte): 92., 1 different subnets (first two Bytes): 92.123., 2 different subnets (first three Bytes): 92.123.94., 92.123.95.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 5 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:14c0:, 2 different subnets (first three blocks): 2600:14c0:0006:, 2600:14c0:0007:, 2 different subnets (first four blocks): 2600:14c0:0006:0000:, 2600:14c0:0007:0000:
AGood: Name Server IPv6 addresses from different subnets found.
XNameserver Timeout checking Echo Capitalization: ns2.linode.com / 92.123.94.3
XNameserver Timeout checking EDNS512: ns2.linode.com / 92.123.94.3
Nameserver doesn't pass all EDNS-Checks: ns1.linode.com: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.linode.com / 92.123.94.2: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.linode.com / 2600:14c0:6::2: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.linode.com / 92.123.94.3: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.linode.com / 2600:14c0:6::3: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.linode.com / 92.123.95.3: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.linode.com / 2600:14c0:7::3: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns4.linode.com / 92.123.95.4: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns4.linode.com / 2600:14c0:7::4: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns5.linode.com / 92.123.95.2: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns5.linode.com / 2600:14c0:7::2: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. 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.

4. Content- and Performance-critical Checks

http://onion.ly/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 209.141.39.59
-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://www.onion.ly/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 209.141.39.59
-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: 334170 milliseconds, 334.170 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)

Issuerlast 7 daysactivenum Certs
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
3
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6993005896
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2024-03-24 00:00:00
2024-06-22 23:59:59
*.onion.ly, onion.ly - 2 entries


6843027685
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-02-29 00:00:00
2024-05-29 23:59:59
*.onion.ly, onion.ly - 2 entries


6472088756
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-12-31 00:00:00
2024-03-30 23:59:59
*.onion.ly, onion.ly - 2 entries


6376743038
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2023-12-16 00:00:00
2024-03-15 23:59:59
*.onion.ly, onion.ly - 2 entries


6115246370
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-11-02 00:00:00
2024-01-31 23:59:59
*.onion.ly, onion.ly - 2 entries



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

Issuerlast 7 daysactivenum Certs
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
4
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
4

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
12488302765
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2024-03-23 23:00:00
2024-06-22 21:59:59
*.onion.ly, onion.ly
2 entries


12227577028
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-02-28 23:00:00
2024-05-29 21:59:59
*.onion.ly, onion.ly
2 entries


11591569041
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-12-30 23:00:00
2024-03-30 22:59:59
*.onion.ly, onion.ly
2 entries


11466851953
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2023-12-15 23:00:00
2024-03-15 22:59:59
*.onion.ly, onion.ly
2 entries


10974699929
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-11-01 23:00:00
2024-01-31 22:59:59
*.onion.ly, onion.ly
2 entries


10808488021
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2023-10-16 22:00:00
2024-01-15 22:59:59
*.onion.ly, onion.ly
2 entries


10485178717
leaf cert
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2023-09-02 22:00:00
2023-12-02 22:59:59
*.onion.ly, onion.ly
2 entries


10297222391
leaf cert
CN=ZeroSSL RSA Domain Secure Site CA, O=ZeroSSL, C=AT
2023-08-17 22:00:00
2023-11-16 22:59:59
*.onion.ly, onion.ly
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: ns1.linode.com, ns2.linode.com, ns3.linode.com, ns4.linode.com, ns5.linode.com

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

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
ns1.linode.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
3
ns2.linode.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
4
ns3.linode.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
5
ns4.linode.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
6
ns5.linode.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-249.akam.net, a12-65.akam.net, a16-64.akam.net, a3-67.akam.net, a4-64.akam.net, a7-65.akam.net
7
net
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
8
a1-249.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
9
a12-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
10
a16-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
11
a3-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
12
a4-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
13
a7-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43
14
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43
15
a1-249.akam.net: 193.108.91.249
A
a1-67.akam.net (2600:1401:2::43)
16
a1-249.akam.net: 2600:1401:2::f9
AAAA
a1-67.akam.net (2600:1401:2::43)
17
a12-65.akam.net: 184.26.160.65
A
a1-67.akam.net (2600:1401:2::43)
18
a12-65.akam.net: 2600:1480:f000::41
AAAA
a1-67.akam.net (2600:1401:2::43)
19
a16-64.akam.net: 23.211.132.64
A
a1-67.akam.net (2600:1401:2::43)
20
a16-64.akam.net: 2600:1406:1b::40
AAAA
a1-67.akam.net (2600:1401:2::43)
21
a3-67.akam.net: 96.7.49.67
A
a1-67.akam.net (2600:1401:2::43)
22
a3-67.akam.net: 2600:1408:1c::43
AAAA
a1-67.akam.net (2600:1401:2::43)
23
a4-64.akam.net: 72.246.46.64
A
a1-67.akam.net (2600:1401:2::43)
24
a4-64.akam.net: 2600:1480:9000::40
AAAA
a1-67.akam.net (2600:1401:2::43)
25
a7-65.akam.net: 23.61.199.65
A
a1-67.akam.net (2600:1401:2::43)
26
a7-65.akam.net: 2600:1406:32::41
AAAA
a1-67.akam.net (2600:1401:2::43)
27
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
28
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
29
ns1.linode.com: 92.123.94.2
A
a1-249.akam.net (2600:1401:2::f9)
30
ns1.linode.com: 2600:14c0:6::2
AAAA
a1-249.akam.net (2600:1401:2::f9)
31
ns2.linode.com: 92.123.94.3
A
a1-249.akam.net (2600:1401:2::f9)
32
ns2.linode.com: 2600:14c0:6::3
AAAA
a1-249.akam.net (2600:1401:2::f9)
33
ns3.linode.com: 92.123.95.3
A
a1-249.akam.net (2600:1401:2::f9)
34
ns3.linode.com: 2600:14c0:7::3
AAAA
a1-249.akam.net (2600:1401:2::f9)
35
ns4.linode.com: 92.123.95.4
A
a1-249.akam.net (2600:1401:2::f9)
36
ns4.linode.com: 2600:14c0:7::4
AAAA
a1-249.akam.net (2600:1401:2::f9)
37
ns5.linode.com: 92.123.95.2
A
a1-249.akam.net (2600:1401:2::f9)
38
ns5.linode.com: 2600:14c0:7::2
AAAA
a1-249.akam.net (2600:1401:2::f9)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.onion.ly
0

no CAA entry found
1
0
onion.ly
0

no CAA entry found
1
0
ly
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
onion.ly
hex:76 3D 73 70 66 31 20 69 6E 63 6C 75 64 65 3A 63 61 72 62 6F 6E 6D 78 2E 6E 65 74 20 2D 61 6C 6C 09
ok
1
0
www.onion.ly

ok
1
0
_acme-challenge.onion.ly

missing entry or wrong length
1
0
_acme-challenge.www.onion.ly

missing entry or wrong length
1
0
_acme-challenge.onion.ly.onion.ly

perhaps wrong
1
0
_acme-challenge.www.onion.ly.onion.ly

perhaps wrong
1
0
_acme-challenge.www.onion.ly.www.onion.ly

perhaps wrong
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

onion.ly
10
mx1.carbonmx.net
01ok

A


51.38.159.116
01ok

CNAME


00ok
_dmarc
TXT
_dmarc.onion.ly

hex:76 3D 44 4D 41 52 43 31 3B 20 70 3D 6E 6F 6E 65 0A
013A _dmarc TXT Entry must start with "'v=DMARC1". Do you really want to create a DMARC? Or is it the effect of a wildcard * DNS?



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=57bff118-78df-4fde-bcb4-53b1131575ba


Last Result: https://check-your-website.server-daten.de/?q=onion.ly - 2024-05-15 11:06:50


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

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

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