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




X

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

Checked:
25.05.2023 17:07:54


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ns1.tdshosting.bj
A
102.215.93.63
Porto-Novo/Ouémé/Benin (BJ) - Technodata Solutions
Hostname: ns1.tdshosting.bj
yes
1
0

AAAA

yes


www.ns1.tdshosting.bj

Name Error
yes
1
0
*.tdshosting.bj
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.ns1.tdshosting.bj
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 60955, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 26617, DigestType 2 and Digest 9AjAs8KNh6dhdTSLJ/bSbKRyMfwpBxq2tfhJd3xlSLU=



1 RRSIG RR to validate DS RR found



RRSIG-Owner bj., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2023, 13:00:00 +, Signature-Inception: 25.05.2023, 12:00:00 +, KeyTag 60955, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 31441, Flags 256



Public Key with Algorithm 8, KeyTag 51976, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner bj., Algorithm: 8, 1 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2023, 00:00:00 +, Signature-Inception: 24.05.2023, 00:00:00 +, KeyTag 26617, Signer-Name: bj



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



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

Zone: tdshosting.bj
tdshosting.bj
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 "u101isolkaj94kbj7pabs7mpd8lrdhpm" between the hashed NSEC3-owner "u03r1q9lermh1jd797m35kv5cg0lpuhu" and the hashed NextOwner "u1i98hoohcb0kols6peu2ed9v3ng49s3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner u03r1q9lermh1jd797m35kv5cg0lpuhu.bj., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 11.06.2023, 07:00:00 +, Signature-Inception: 04.05.2023, 07:00:00 +, KeyTag 31441, Signer-Name: bj



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "4f6lrgdjha6mkgngpj7apcn6ti3b1kkj" as Owner. That's the Hash of "bj" with the NextHashedOwnerName "4fqj3lclmagmq9fsa4cjabc5s6t3lfem". So that domain name is the Closest Encloser of "tdshosting.bj". Opt-Out: True.
Bitmap: NS, SOA, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 4f6lrgdjha6mkgngpj7apcn6ti3b1kkj.bj., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 11.06.2023, 07:00:00 +, Signature-Inception: 04.05.2023, 07:00:00 +, KeyTag 31441, Signer-Name: bj



0 DNSKEY RR found




Zone: ns1.tdshosting.bj
ns1.tdshosting.bj
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.ns1.tdshosting.bj
www.ns1.tdshosting.bj
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.ns1.tdshosting.bj
  ns1.tdshosting.bj

ns1.tdshosting.bj
  ns1.tdshosting.bj
102.215.93.63
Porto-Novo/Ouémé/Benin (BJ) - Technodata Solutions

tdshosting.bj
  ns1.tdshosting.bj
102.215.93.63
Porto-Novo/Ouémé/Benin (BJ) - Technodata Solutions


  ns2.tdshosting.bj
102.215.93.127
Porto-Novo/Ouémé/Benin (BJ) - Technodata Solutions

bj
  ns1.nic.bj


  ns2.nic.bj


  ns-bj.afrinic.net / s01-ns2.jinx


  ns-bj.nic.fr / dns.ams.nic.fr


  pch.nic.bj / 2.ber.pch


4. SOA-Entries


Domain:bj
Zone-Name:bj
Primary:pch.nic.bj
Mail:tech.nic.bj
Serial:2023052516
Refresh:21600
Retry:1800
Expire:2419200
TTL:7200
num Entries:5


Domain:tdshosting.bj
Zone-Name:tdshosting.bj
Primary:ns1.tdshosting.bj
Mail:fdako.technodatasolutions.bj
Serial:202224101
Refresh:21600
Retry:3600
Expire:1209600
TTL:10800
num Entries:1


Domain:tdshosting.bj
Zone-Name:tdshosting.bj
Primary:ns1.tdshosting.bj
Mail:info.technodatasolutions.bj
Serial:2023042103
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:1


Domain:ns1.tdshosting.bj
Zone-Name:tdshosting.bj
Primary:ns1.tdshosting.bj
Mail:fdako.technodatasolutions.bj
Serial:202224101
Refresh:21600
Retry:3600
Expire:1209600
TTL:10800
num Entries:1


Domain:www.ns1.tdshosting.bj
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://ns1.tdshosting.bj/
102.215.93.63
-2

1.387
V
ConnectFailure - Unable to connect to the remote server

• https://ns1.tdshosting.bj/
102.215.93.63
-2

1.393
V
ConnectFailure - Unable to connect to the remote server

• http://ns1.tdshosting.bj/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
102.215.93.63
-2

1.390
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• https://102.215.93.63/
102.215.93.63
-2

1.387
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "ns1.tdshosting.bj" is subdomain, public suffix is ".bj", top-level-domain is ".bj", top-level-domain-type is "country-code", Country is Benin, tld-manager is "Benin Telecoms S.A.", num .bj-domains preloaded: 5 (complete: 221801)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: ns1.tdshosting.bj 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: ns1.tdshosting.bj 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.
Vhttp://ns1.tdshosting.bj/ 102.215.93.63
-2

Connect failure - perhaps firewall
Vhttps://ns1.tdshosting.bj/ 102.215.93.63
-2

Connect failure - perhaps firewall
Vhttp://ns1.tdshosting.bj/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 102.215.93.63
-2

Connect failure - perhaps firewall
Vhttps://102.215.93.63/ 102.215.93.63
-2

Connect failure - perhaps firewall
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 ns1.tdshosting.bj, 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.ns1.tdshosting.bj

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:: 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.ns1.tdshosting.bj (102.215.93.63), ns2.tdshosting.bj (102.215.93.127)
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: ns1.tdshosting.bj, ns2.tdshosting.bj, 2 Name Servers included in Delegation: ns1.tdshosting.bj, ns2.tdshosting.bj, 2 Name Servers included in 1 Zone definitions: ns1.tdshosting.bj, ns2.tdshosting.bj, 1 Name Servers listed in SOA.Primary: ns1.tdshosting.bj.
AGood: Only one SOA.Primary Name Server found.: ns1.tdshosting.bj.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.tdshosting.bj.
AGood: Consistency 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. Ordered list of name servers: ns1.tdshosting.bj, ns2.tdshosting.bj
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: bj
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: tdshosting.bj
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: BJ
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 102., 1 different subnets (first two Bytes): 102.215., 1 different subnets (first three Bytes): 102.215.93.
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: ns1.tdshosting.bj: 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: ns-bj.nic.fr: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns.ams.nic.fr). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. 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://ns1.tdshosting.bj/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 102.215.93.63
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. 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: 80200 milliseconds, 80.200 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)

Small Code Update - wait one minute


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

Small Code Update - wait one minute


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.tdshosting.bj, ns2.tdshosting.bj

QNr.DomainTypeNS used
1
bj
NS
h.root-servers.net (2001:500:1::53)

Answer: ns-bj.afrinic.net, ns-bj.nic.fr, ns1.nic.bj, ns2.nic.bj, pch.nic.bj
2
ns1.tdshosting.bj: 102.215.93.63
NS
ns-bj.afrinic.net (2001:43f8:120::33)

Answer: ns2.tdshosting.bj
102.215.93.127


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
ns1.tdshosting.bj
0

no CAA entry found
1
0
tdshosting.bj
0

no CAA entry found
1
0
bj
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tdshosting.bj
google-site-verification=SmHuNCWJBDqbN-yCwxuM5y1gQ5hW94eV4pjK9D6n1aU
ok
1
0
tdshosting.bj
google-site-verification=ZAkJDtu7DT2ntvb1ZTqgyQDSFHL7Qe9NkxTQFPlZKIA
ok
1
0
tdshosting.bj
v=spf1 +a +mx +a:tdshosting.bj -all
ok
1
0
ns1.tdshosting.bj

ok
1
0
_acme-challenge.ns1.tdshosting.bj

Name Error - The domain name does not exist
1
0
_acme-challenge.ns1.tdshosting.bj.tdshosting.bj

Name Error - The domain name does not exist
1
0
_acme-challenge.ns1.tdshosting.bj.ns1.tdshosting.bj

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
ns1.tdshosting.bj
102.215.93.63
21
FTP



ns1.tdshosting.bj
102.215.93.63
21
FTP



ns1.tdshosting.bj
102.215.93.63
22
SSH



ns1.tdshosting.bj
102.215.93.63
22
SSH



ns1.tdshosting.bj
102.215.93.63
25
SMTP



ns1.tdshosting.bj
102.215.93.63
25
SMTP



ns1.tdshosting.bj
102.215.93.63
53
DNS
open


ns1.tdshosting.bj
102.215.93.63
53
DNS
open


ns1.tdshosting.bj
102.215.93.63
110
POP3



ns1.tdshosting.bj
102.215.93.63
110
POP3



ns1.tdshosting.bj
102.215.93.63
143
IMAP



ns1.tdshosting.bj
102.215.93.63
143
IMAP



ns1.tdshosting.bj
102.215.93.63
465
SMTP (encrypted)



ns1.tdshosting.bj
102.215.93.63
465
SMTP (encrypted)



ns1.tdshosting.bj
102.215.93.63
587
SMTP (encrypted, submission)



ns1.tdshosting.bj
102.215.93.63
587
SMTP (encrypted, submission)



ns1.tdshosting.bj
102.215.93.63
993
IMAP (encrypted)



ns1.tdshosting.bj
102.215.93.63
993
IMAP (encrypted)



ns1.tdshosting.bj
102.215.93.63
995
POP3 (encrypted)



ns1.tdshosting.bj
102.215.93.63
995
POP3 (encrypted)



ns1.tdshosting.bj
102.215.93.63
1433
MS SQL



ns1.tdshosting.bj
102.215.93.63
1433
MS SQL



ns1.tdshosting.bj
102.215.93.63
2082
cPanel (http)



ns1.tdshosting.bj
102.215.93.63
2082
cPanel (http)



ns1.tdshosting.bj
102.215.93.63
2083
cPanel (https)



ns1.tdshosting.bj
102.215.93.63
2083
cPanel (https)



ns1.tdshosting.bj
102.215.93.63
2086
WHM (http)



ns1.tdshosting.bj
102.215.93.63
2086
WHM (http)



ns1.tdshosting.bj
102.215.93.63
2087
WHM (https)



ns1.tdshosting.bj
102.215.93.63
2087
WHM (https)



ns1.tdshosting.bj
102.215.93.63
2089
cPanel Licensing



ns1.tdshosting.bj
102.215.93.63
2089
cPanel Licensing



ns1.tdshosting.bj
102.215.93.63
2095
cPanel Webmail (http)



ns1.tdshosting.bj
102.215.93.63
2095
cPanel Webmail (http)



ns1.tdshosting.bj
102.215.93.63
2096
cPanel Webmail (https)



ns1.tdshosting.bj
102.215.93.63
2096
cPanel Webmail (https)



ns1.tdshosting.bj
102.215.93.63
2222
DirectAdmin (http)



ns1.tdshosting.bj
102.215.93.63
2222
DirectAdmin (http)



ns1.tdshosting.bj
102.215.93.63
2222
DirectAdmin (https)



ns1.tdshosting.bj
102.215.93.63
2222
DirectAdmin (https)



ns1.tdshosting.bj
102.215.93.63
3306
mySql



ns1.tdshosting.bj
102.215.93.63
3306
mySql



ns1.tdshosting.bj
102.215.93.63
5224
Plesk Licensing



ns1.tdshosting.bj
102.215.93.63
5224
Plesk Licensing



ns1.tdshosting.bj
102.215.93.63
5432
PostgreSQL



ns1.tdshosting.bj
102.215.93.63
5432
PostgreSQL



ns1.tdshosting.bj
102.215.93.63
8080
Ookla Speedtest (http)



ns1.tdshosting.bj
102.215.93.63
8080
Ookla Speedtest (http)



ns1.tdshosting.bj
102.215.93.63
8080
Ookla Speedtest (https)



ns1.tdshosting.bj
102.215.93.63
8080
Ookla Speedtest (https)



ns1.tdshosting.bj
102.215.93.63
8083
VestaCP http



ns1.tdshosting.bj
102.215.93.63
8083
VestaCP http



ns1.tdshosting.bj
102.215.93.63
8083
VestaCP https



ns1.tdshosting.bj
102.215.93.63
8083
VestaCP https



ns1.tdshosting.bj
102.215.93.63
8443
Plesk Administration (https)



ns1.tdshosting.bj
102.215.93.63
8443
Plesk Administration (https)



ns1.tdshosting.bj
102.215.93.63
8447
Plesk Installer + Updates



ns1.tdshosting.bj
102.215.93.63
8447
Plesk Installer + Updates



ns1.tdshosting.bj
102.215.93.63
8880
Plesk Administration (http)



ns1.tdshosting.bj
102.215.93.63
8880
Plesk Administration (http)



ns1.tdshosting.bj
102.215.93.63
10000
Webmin (http)



ns1.tdshosting.bj
102.215.93.63
10000
Webmin (http)



ns1.tdshosting.bj
102.215.93.63
10000
Webmin (https)



ns1.tdshosting.bj
102.215.93.63
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=27fe3d15-9606-4e50-92b7-745ddb2bb5a3


Last Result: https://check-your-website.server-daten.de/?q=ns1.tdshosting.bj - 2023-05-25 17:07: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=ns1.tdshosting.bj" target="_blank">Check this Site: ns1.tdshosting.bj</a>

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