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:
26.05.2023 06:09:54

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
zoomus.net	A		yes	1	0
	AAAA		yes
www.zoomus.net		Name Error	yes	1	0
*.zoomus.net	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: net
net	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 07.06.2023, 21:00:00 +, Signature-Inception: 25.05.2023, 20: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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 27554, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2023, 16:28:30 +, Signature-Inception: 19.05.2023, 16:23:30 +, KeyTag 35886, Signer-Name: net


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


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

Zone: zoomus.net
zoomus.net	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 "s5efvs3q1cahsbi19f35uk9ssrtv3fe9" between the hashed NSEC3-owner "s5efl04v2u0lldlmpq7e3davph51enjo" and the hashed NextOwner "s5egbe4a56rk9d1gmfhl7bi5o3nhkdct". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner s5efl04v2u0lldlmpq7e3davph51enjo.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.06.2023, 07:03:02 +, Signature-Inception: 25.05.2023, 05:53:02 +, KeyTag 27554, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "zoomus.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.05.2023, 07:00:27 +, Signature-Inception: 23.05.2023, 05:50:27 +, KeyTag 27554, Signer-Name: net


	0 DNSKEY RR found




Zone: www.zoomus.net
www.zoomus.net	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.zoomus.net	• ns1.myhostadmin.net
zoomus.net	• ns1.myhostadmin.net	118.123.249.114 Zhongba/Sichuan/China (CN) - CHINANET SiChuan Telecom Internet Data Center	•
	X	118.123.253.132 Zhongba/Sichuan/China (CN) - CHINANET SiChuan Telecom Internet Data Center
	X	60.247.150.254 Ulanqab/Inner Mongolia Autonomous Region/China (CN) - China Internet Network Information Center
	•	240e:d9:c200::2 Beijing/China (CN) - CHINANET	•
	• ns2.myhostadmin.net	211.149.230.100 Haidian/Beijing/China (CN) - China Internet Network Information Center	•
	•	61.240.129.143 Beijing/China (CN) - CHINA UNICOM China169 Backbone
	T	2408:872f:d10::2 Jinrongjie/Beijing/China (CN) - China Unicom Network
	•	240e:d9:c200:1::2 Beijing/China (CN) - CHINANET	•
	• ns3.myhostadmin.net	118.123.249.114 Zhongba/Sichuan/China (CN) - CHINANET SiChuan Telecom Internet Data Center	•
	•	61.240.129.143 Beijing/China (CN) - CHINA UNICOM China169 Backbone
	•	240e:d9:c200::2 Beijing/China (CN) - CHINANET	•
	X ns4.myhostadmin.net	118.123.253.132 Zhongba/Sichuan/China (CN) - CHINANET SiChuan Telecom Internet Data Center
	•	211.149.230.100 Haidian/Beijing/China (CN) - China Internet Network Information Center	•
	T	240e:d9:c200:1::2 Beijing/China (CN) - CHINANET	•
	• ns5.myhostadmin.net	118.123.249.114 Zhongba/Sichuan/China (CN) - CHINANET SiChuan Telecom Internet Data Center	•
	•	61.240.129.143 Beijing/China (CN) - CHINA UNICOM China169 Backbone
	•	240e:d9:c200::2 Beijing/China (CN) - CHINANET	•
	• ns6.myhostadmin.net	60.247.150.13 Ulanqab/Inner Mongolia Autonomous Region/China (CN) - China Internet Network Information Center	•
	•	240e:d9:c200:1::2 Beijing/China (CN) - CHINANET	•
net	• a.gtld-servers.net / nnn1-defra-5		•
	• b.gtld-servers.net / nnn1-elpar7		•
	• c.gtld-servers.net / nnn1-defra-5		•
	• d.gtld-servers.net / nnn1-defra-5		•
	• e.gtld-servers.net / nnn1-stk4		•
	• 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-nlams-1c		•
	• k.gtld-servers.net / nnn1-nlams-1d		•
	• l.gtld-servers.net / nnn1-nlams-1a		•
	• m.gtld-servers.net / nnn1-nlams-1e		•

4. SOA-Entries

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

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

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

Domain:	zoomus.net
Zone-Name:	zoomus.net
Primary:	ns1.myhostadmin.net
Mail:	dnsconct.myhostadmin.net
Serial:	2018053005
Refresh:	43200
Retry:	300
Expire:	1209600
TTL:	3600
num Entries:	18

Domain:	www.zoomus.net
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "zoomus.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 8549 (complete: 221801)
A	DNS: "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.
X	Fatal error: Nameserver isn't defined or has timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns1.myhostadmin.net / 118.123.253.132: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
X	Fatal error: Nameserver doesn't support TCP connection: ns1.myhostadmin.net / 60.247.150.254: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
X	Fatal error: Nameserver doesn't support TCP connection: ns2.myhostadmin.net / 61.240.129.143: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns2.myhostadmin.net / 2408:872f:d10::2: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns3.myhostadmin.net / 61.240.129.143: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns4.myhostadmin.net / 118.123.253.132: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
X	Fatal error: Nameserver doesn't support TCP connection: ns5.myhostadmin.net / 61.240.129.143: Timeout
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.zoomus.net
	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:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
A	Info:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Good: 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.myhostadmin.net (118.123.249.114, 118.123.253.132, 240e:d9:c200:123::2, 240e:d9:c200::2, 60.247.150.254), ns2.myhostadmin.net (211.149.230.100, 240e:d9:c200:1::2), ns3.myhostadmin.net (118.123.249.114, 240e:d9:c200::2, 61.240.129.143), ns4.myhostadmin.net (118.123.253.132, 211.149.230.100, 240e:d9:c200:1::2), ns5.myhostadmin.net (118.123.249.114, 240e:d9:c200::2, 61.240.129.143), ns6.myhostadmin.net (240e:d9:c200:1::2)
A	Good (1 - 3.0):: An average of 0.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 6 different Name Servers found: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net, 2 Name Servers included in Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, 6 Name Servers included in 1 Zone definitions: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net, 1 Name Servers listed in SOA.Primary: ns1.myhostadmin.net.
A	Good: Only one SOA.Primary Name Server found.: ns1.myhostadmin.net.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.myhostadmin.net.
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.: ns1.myhostadmin.net (118.123.249.114): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns1.myhostadmin.net (118.123.253.132): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns1.myhostadmin.net (60.247.150.254): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns1.myhostadmin.net (240e:d9:c200::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns2.myhostadmin.net (211.149.230.100): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns2.myhostadmin.net (61.240.129.143): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns2.myhostadmin.net (2408:872f:d10::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns2.myhostadmin.net (240e:d9:c200:1::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns3.myhostadmin.net (118.123.249.114): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns3.myhostadmin.net (61.240.129.143): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns3.myhostadmin.net (240e:d9:c200::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns4.myhostadmin.net (118.123.253.132): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns4.myhostadmin.net (211.149.230.100): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns4.myhostadmin.net (240e:d9:c200:1::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns5.myhostadmin.net (118.123.249.114): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns5.myhostadmin.net (61.240.129.143): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns5.myhostadmin.net (240e:d9:c200::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns6.myhostadmin.net (60.247.150.13): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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.: ns6.myhostadmin.net (240e:d9:c200:1::2): Delegation: ns1.myhostadmin.net, ns2.myhostadmin.net, Zone: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net. Name Servers defined in Zone, missing in Delegation: ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net.
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: 6 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.: 6 Name Servers, 1 Top Level Domain: net
	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: myhostadmin.net
	Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: CN
A	Info: Ipv4-Subnet-list: 12 Name Servers, 4 different subnets (first Byte): 118., 211., 60., 61., 4 different subnets (first two Bytes): 118.123., 211.149., 60.247., 61.240., 5 different subnets (first three Bytes): 118.123.249., 118.123.253., 211.149.230., 60.247.150., 61.240.129.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 7 Name Servers with IPv6, 2 different subnets (first block): 2408:, 240e:, 2 different subnets (first two blocks): 2408:872f:, 240e:00d9:, 2 different subnets (first three blocks): 2408:872f:0d10:, 240e:00d9:c200:, 3 different subnets (first four blocks): 2408:872f:0d10:0000:, 240e:00d9:c200:0000:, 240e:00d9:c200:0001:
A	Good: Name Server IPv6 addresses from different subnets found.
X	Nameserver Timeout checking Echo Capitalization: ns1.myhostadmin.net / 60.247.150.254
X	Nameserver Timeout checking Echo Capitalization: ns2.myhostadmin.net / 2408:872f:d10::2
X	Nameserver Timeout checking EDNS512: ns2.myhostadmin.net / 2408:872f:d10::2
X	Nameserver Timeout checking EDNS512: ns4.myhostadmin.net / 240e:d9:c200:1::2
	Nameserver doesn't pass all EDNS-Checks: ns1.myhostadmin.net: 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.myhostadmin.net / 60.247.150.254: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns1.myhostadmin.net / 118.123.253.132: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns2.myhostadmin.net / 61.240.129.143: OP100: no result. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: no result. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: no result. COOKIE: no result. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.myhostadmin.net / 2408:872f:d10::2: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns2.myhostadmin.net / 240e:d9:c200:1::2: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns3.myhostadmin.net / 61.240.129.143: OP100: no result. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: no result. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: no result. COOKIE: no result. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns4.myhostadmin.net / 118.123.253.132: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns5.myhostadmin.net / 61.240.129.143: OP100: no result. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: no result. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: no result. COOKIE: no result. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns5.myhostadmin.net / 118.123.249.114: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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
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: 260590 milliseconds, 260.590 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.

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net

QNr.	Domain	Type	NS used
1	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
2	ns1.myhostadmin.net: 118.123.249.114, 118.123.253.132, 240e:d9:c200:123::2, 240e:d9:c200::2, 60.247.150.254	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.myhostadmin.net 211.149.230.100, 240e:d9:c200:1::2
	Answer: ns3.myhostadmin.net 118.123.249.114, 240e:d9:c200::2, 61.240.129.143
	Answer: ns4.myhostadmin.net 118.123.253.132, 211.149.230.100, 240e:d9:c200:1::2
	Answer: ns5.myhostadmin.net 118.123.249.114, 240e:d9:c200::2, 61.240.129.143
	Answer: ns6.myhostadmin.net 240e:d9:c200:1::2

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
zoomus.net	0		no CAA entry found	1	0
net	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	Status	∑ Queries
zoomus.net	ok	1
_acme-challenge.zoomus.net	Name Error - The domain name does not exist	1
_acme-challenge.zoomus.net.zoomus.net	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=035384e3-a0c2-41c5-bba3-2f01e5788308

Last Result: https://check-your-website.server-daten.de/?q=zoomus.net - 2023-05-26 06:09: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=zoomus.net" target="_blank">Check this Site: zoomus.net</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=zoomus.net