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

...

skip EDNS-Check

skip Content-Check

check links

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

Checked:
15.05.2024 17:58:45

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
majortom.myvnc.com	A	141.144.243.35 Frankfurt am Main/Hesse/Germany (DE) - Oracle Corporation No Hostname found	yes	1	0
	AAAA		yes
www.majortom.myvnc.com		Name Error	yes	1	0
*.majortom.myvnc.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 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: com
com	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner com., 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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 956, Flags 256


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.05.2024, 14:02:35 +, Signature-Inception: 07.05.2024, 13:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


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

Zone: myvnc.com
myvnc.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 "j5l72bki1lioluuj1g9kn11lbbe9ncv9" between the hashed NSEC3-owner "j5l7207embrikhmnfcdg15pb397m0db4" and the hashed NextOwner "j5l778fktckdjg303dfa4dqomnbfvn46". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner j5l7207embrikhmnfcdg15pb397m0db4.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2024, 06:37:58 +, Signature-Inception: 13.05.2024, 05:27:58 +, KeyTag 956, 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 "ck0q2d6ni4i7eqh8na30ns61o48ul8g5". So that domain name is the Closest Encloser of "myvnc.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2024, 04:25:01 +, Signature-Inception: 13.05.2024, 03:15:01 +, KeyTag 956, Signer-Name: com


	0 DNSKEY RR found




Zone: majortom.myvnc.com
majortom.myvnc.com	0 DS RR in the parent zone found


	0 DNSKEY RR found




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

3. Name Servers

Domain	Nameserver	NS-IP
www.majortom.myvnc.com	• nf1.no-ip.com
majortom.myvnc.com	• nf1.no-ip.com / frana1	194.62.182.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1820::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
myvnc.com	• nf1.no-ip.com / frana1	194.62.182.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1820::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf2.no-ip.com / frana1	45.54.64.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2607:f740:e626::53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf3.no-ip.com / frana1	204.16.253.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e61::53 Piscataway/New Jersey/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf4.no-ip.com / frana1	194.62.183.53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2a07:dc00:1830::53 Washington/District of Columbia/United States (US) - Vitalwerks Internet Solutions, LLC	•
	• nf5.no-ip.com / frana1	204.16.253.53 Reno/Nevada/United States (US) - Vitalwerks Internet Solutions, LLC	•
	•	2620:0:2e61::53 Piscataway/New Jersey/United States (US) - Vitalwerks Internet Solutions, LLC	•
com	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-defra-5		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-ein1		•
	• k.gtld-servers.net / nnn1-ein4		•
	• l.gtld-servers.net / nnn1-nlams-2e		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

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

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

Domain:	myvnc.com
Zone-Name:	myvnc.com
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2044556202
Refresh:	90
Retry:	120
Expire:	604800
TTL:	60
num Entries:	8

Domain:	myvnc.com
Zone-Name:	myvnc.com
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2044556203
Refresh:	90
Retry:	120
Expire:	604800
TTL:	60
num Entries:	2

Domain:	majortom.myvnc.com
Zone-Name:	myvnc.com
Primary:	nf1.no-ip.com
Mail:	hostmaster.no-ip.com
Serial:	2044556203
Refresh:	90
Retry:	120
Expire:	604800
TTL:	60
num Entries:	2

Domain:	www.majortom.myvnc.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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://majortom.myvnc.com/ 141.144.243.35	301	https://majortom.myvnc.com/ Html is minified: 100.00 %	0.030	A
Date: Wed, 15 May 2024 15:59:36 GMT
Server: Apache/2.4.52, (Ubuntu)
Location: https://majortom.myvnc.com/
Connection: close
Content-Length: 319
Content-Type: text/html; charset=iso-8859-1

• https://majortom.myvnc.com/ 141.144.243.35	-14		10.013	T
Timeout - The operation has timed out.

• http://majortom.myvnc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 141.144.243.35 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	301	https://majortom.myvnc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Html is minified: 100.00 % Other inline scripts (∑/total): 0/0	0.033	A
Visible Content:
Date: Wed, 15 May 2024 15:59:46 GMT
Server: Apache/2.4.52, (Ubuntu)
Location: https://majortom.myvnc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Connection: close
Content-Length: 388
Content-Type: text/html; charset=iso-8859-1

• https://majortom.myvnc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-14		10.007	T
Timeout - The operation has timed out.
Visible Content:

• https://141.144.243.35/ 141.144.243.35	-14		10.007	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "majortom.myvnc.com" is domain, public suffix is ".myvnc.com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 94244 (complete: 244198)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: majortom.myvnc.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: majortom.myvnc.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: 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.
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
	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 majortom.myvnc.com, 1 ip addresses.
B	No _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.majortom.myvnc.com
	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
A	Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers.
A	Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.2 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 5 different Name Servers found: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 4 Name Servers included in Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, 5 Name Servers included in 1 Zone definitions: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com, 1 Name Servers listed in SOA.Primary: nf1.no-ip.com.
A	Good: Only one SOA.Primary Name Server found.: nf1.no-ip.com.
A	Good: SOA.Primary Name Server included in the delegation set.: nf1.no-ip.com.
X	Fatal: 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.: nf1.no-ip.com (194.62.182.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf1.no-ip.com (2a07:dc00:1820::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf2.no-ip.com (45.54.64.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf2.no-ip.com (2607:f740:e626::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf3.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf3.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf4.no-ip.com (194.62.183.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf4.no-ip.com (2a07:dc00:1830::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf5.no-ip.com (204.16.253.53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
X	Fatal: 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.: nf5.no-ip.com (2620:0:2e61::53): Delegation: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, Zone: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com. Name Servers defined in Zone, missing in Delegation: nf5.no-ip.com.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 5 different Name Servers found
A	Good: 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: no-ip.com
	Warning: All Name Servers from the same Country / IP location.: 5 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 5 Name Servers, 3 different subnets (first Byte): 194., 204., 45., 3 different subnets (first two Bytes): 194.62., 204.16., 45.54., 4 different subnets (first three Bytes): 194.62.182., 194.62.183., 204.16.253., 45.54.64.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 5 Name Servers with IPv6, 3 different subnets (first block): 2607:, 2620:, 2a07:, 3 different subnets (first two blocks): 2607:f740:, 2620:0000:, 2a07:dc00:, 4 different subnets (first three blocks): 2607:f740:e626:, 2620:0000:2e61:, 2a07:dc00:1820:, 2a07:dc00:1830:, 4 different subnets (first four blocks): 2607:f740:e626:0000:, 2620:0000:2e61:0000:, 2a07:dc00:1820:0000:, 2a07:dc00:1830:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: nf1.no-ip.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: 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
	https://majortom.myvnc.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de	-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.
A	Good: All checked attribute values are enclosed in quotation marks (" or ').
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 98586 milliseconds, 98.586 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. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: nf1.no-ip.com, nf2.no-ip.com, nf3.no-ip.com, nf4.no-ip.com, nf5.no-ip.com

QNr.	Domain	Type	NS 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	nf1.no-ip.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
3	nf2.no-ip.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
4	nf3.no-ip.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
5	nf4.no-ip.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
6	nf5.no-ip.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com, ns4.no-ip.com
	Answer: ns1.no-ip.com 194.62.181.53, 2a07:dc00:1810::53
	Answer: ns2.no-ip.com 194.62.180.53, 2a07:dc00:180::53
	Answer: ns3.no-ip.com 204.16.255.53, 2a07:dc00:2550::53
	Answer: ns4.no-ip.com 204.16.254.53, 2620:0:2e64::53
7	nf1.no-ip.com: 194.62.182.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
8	nf1.no-ip.com: 2a07:dc00:1820::53	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
9	nf2.no-ip.com: 45.54.64.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
10	nf2.no-ip.com: 2607:f740:e626::53	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
11	nf3.no-ip.com: 204.16.253.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
12	nf3.no-ip.com: 2620:0:2e61::53	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
13	nf4.no-ip.com: 194.62.183.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
14	nf4.no-ip.com: 2a07:dc00:1830::53	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)
15	nf5.no-ip.com: 204.16.253.53	A	ns1.no-ip.com (2a07:dc00:1810::53)
16	nf5.no-ip.com: 2620:0:2e61::53	AAAA	ns1.no-ip.com (2a07:dc00:1810::53)

14. CAA - Entries

Domainname	Value	∑ Queries
majortom.myvnc.com	no CAA entry found	1
myvnc.com	no CAA entry found	1
com	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
majortom.myvnc.com	ok	1
_acme-challenge.majortom.myvnc.com	Name Error - The domain name does not exist	1
_acme-challenge.majortom.myvnc.com.majortom.myvnc.com	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

Domain	IP	Port	Description	Result	Answer
majortom.myvnc.com	141.144.243.35	21	FTP

majortom.myvnc.com	141.144.243.35	21	FTP
majortom.myvnc.com	141.144.243.35	22	SSH	open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.7
majortom.myvnc.com	141.144.243.35	22	SSH	open	SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.7	Bad: SSH without DNS SSHFP Record found
					Possible DNS SSHFP Entries: majortom.myvnc.com IN SSHFP 3 2 a7c2d3803f6f8abdf625ecbded0df3104d4139de3139ddf2edad52135317afed majortom.myvnc.com IN SSHFP 4 2 2d207e988375ad4b5858d7d8f8de4c468663a957681133ffae085147ff25e0b8
majortom.myvnc.com	141.144.243.35	25	SMTP

majortom.myvnc.com	141.144.243.35	25	SMTP
majortom.myvnc.com	141.144.243.35	53	DNS

majortom.myvnc.com	141.144.243.35	53	DNS
majortom.myvnc.com	141.144.243.35	110	POP3

majortom.myvnc.com	141.144.243.35	110	POP3
majortom.myvnc.com	141.144.243.35	143	IMAP

majortom.myvnc.com	141.144.243.35	143	IMAP
majortom.myvnc.com	141.144.243.35	465	SMTP (encrypted)

majortom.myvnc.com	141.144.243.35	465	SMTP (encrypted)
majortom.myvnc.com	141.144.243.35	587	SMTP (encrypted, submission)

majortom.myvnc.com	141.144.243.35	587	SMTP (encrypted, submission)
majortom.myvnc.com	141.144.243.35	993	IMAP (encrypted)

majortom.myvnc.com	141.144.243.35	993	IMAP (encrypted)
majortom.myvnc.com	141.144.243.35	995	POP3 (encrypted)

majortom.myvnc.com	141.144.243.35	995	POP3 (encrypted)
majortom.myvnc.com	141.144.243.35	1433	MS SQL

majortom.myvnc.com	141.144.243.35	1433	MS SQL
majortom.myvnc.com	141.144.243.35	2082	cPanel (http)

majortom.myvnc.com	141.144.243.35	2082	cPanel (http)
majortom.myvnc.com	141.144.243.35	2083	cPanel (https)

majortom.myvnc.com	141.144.243.35	2083	cPanel (https)
majortom.myvnc.com	141.144.243.35	2086	WHM (http)

majortom.myvnc.com	141.144.243.35	2086	WHM (http)
majortom.myvnc.com	141.144.243.35	2087	WHM (https)

majortom.myvnc.com	141.144.243.35	2087	WHM (https)
majortom.myvnc.com	141.144.243.35	2089	cPanel Licensing

majortom.myvnc.com	141.144.243.35	2089	cPanel Licensing
majortom.myvnc.com	141.144.243.35	2095	cPanel Webmail (http)

majortom.myvnc.com	141.144.243.35	2095	cPanel Webmail (http)
majortom.myvnc.com	141.144.243.35	2096	cPanel Webmail (https)

majortom.myvnc.com	141.144.243.35	2096	cPanel Webmail (https)
majortom.myvnc.com	141.144.243.35	2222	DirectAdmin (http)

majortom.myvnc.com	141.144.243.35	2222	DirectAdmin (http)
majortom.myvnc.com	141.144.243.35	2222	DirectAdmin (https)

majortom.myvnc.com	141.144.243.35	2222	DirectAdmin (https)
majortom.myvnc.com	141.144.243.35	3306	mySql

majortom.myvnc.com	141.144.243.35	3306	mySql
majortom.myvnc.com	141.144.243.35	5224	Plesk Licensing

majortom.myvnc.com	141.144.243.35	5224	Plesk Licensing
majortom.myvnc.com	141.144.243.35	5432	PostgreSQL

majortom.myvnc.com	141.144.243.35	5432	PostgreSQL
majortom.myvnc.com	141.144.243.35	8080	Ookla Speedtest (http)

majortom.myvnc.com	141.144.243.35	8080	Ookla Speedtest (http)
majortom.myvnc.com	141.144.243.35	8080	Ookla Speedtest (https)

majortom.myvnc.com	141.144.243.35	8080	Ookla Speedtest (https)
majortom.myvnc.com	141.144.243.35	8083	VestaCP http

majortom.myvnc.com	141.144.243.35	8083	VestaCP http
majortom.myvnc.com	141.144.243.35	8083	VestaCP https

majortom.myvnc.com	141.144.243.35	8083	VestaCP https
majortom.myvnc.com	141.144.243.35	8443	Plesk Administration (https)

majortom.myvnc.com	141.144.243.35	8443	Plesk Administration (https)
majortom.myvnc.com	141.144.243.35	8447	Plesk Installer + Updates

majortom.myvnc.com	141.144.243.35	8447	Plesk Installer + Updates
majortom.myvnc.com	141.144.243.35	8880	Plesk Administration (http)

majortom.myvnc.com	141.144.243.35	8880	Plesk Administration (http)
majortom.myvnc.com	141.144.243.35	10000	Webmin (http)

majortom.myvnc.com	141.144.243.35	10000	Webmin (http)
majortom.myvnc.com	141.144.243.35	10000	Webmin (https)

majortom.myvnc.com	141.144.243.35	10000	Webmin (https)

Permalink: https://check-your-website.server-daten.de/?i=f8854256-555f-4735-8b7e-2acac80ec888

Last Result: https://check-your-website.server-daten.de/?q=majortom.myvnc.com - 2024-05-15 17:58:45

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

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