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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
03.10.2025 21:54:48

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
chat.moon-palace.net	A	73.189.58.197 San Francisco/California/United States (US) - Comcast Cable Communications Hostname: c-73-189-58-197.hsd1.ca.comcast.net	yes	1	0
	AAAA		yes
www.chat.moon-palace.net		Name Error	yes	1	0
*.moon-palace.net	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.chat.moon-palace.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


	4 DNSKEY RR found


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


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


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.10.2025, 00:00:00 +, Signature-Inception: 01.10.2025, 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 13, KeyTag 37331, DigestType 2 and Digest LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.10.2025, 17:00:00 +, Signature-Inception: 03.10.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 33296, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.10.2025, 14:10:35 +, Signature-Inception: 29.09.2025, 14:05:35 +, KeyTag 37331, Signer-Name: net


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 37331, DigestType 2 and Digest "LwvsLW95370dCP0ho6+S0OOaS57x4/QRH/8oJJDaRTs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: moon-palace.net
moon-palace.net	2 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 53934, DigestType 2 and Digest VKT6goQouuxnhcRb6qaGIGAjyp/vUx8KAEN6Jr4nLQg=


	DS with Algorithm 13, KeyTag 53934, DigestType 4 and Digest P9Fvp7g8oWtffNxEfsVteByH+/FMSi+J0NaupTH+1aE7/jS2qdn4zZbCM50kf8uf


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 08.10.2025, 03:09:01 +, Signature-Inception: 01.10.2025, 01:59:01 +, KeyTag 33296, Signer-Name: net


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 33296 used to validate the DS RRSet in the parent zone


	1 DNSKEY RR found


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


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


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 53934, DigestType 4 and Digest "P9Fvp7g8oWtffNxEfsVteByH+/FMSi+J0NaupTH+1aE7/jS2qdn4zZbCM50kf8uf" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: chat.moon-palace.net
chat.moon-palace.net	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "moon-palace.net" and the NextOwner "moon-palace.net". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 73.189.58.197 Validated: RRSIG-Owner chat.moon-palace.net., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


	TLSA-Query (_443._tcp.chat.moon-palace.net) sends a valid NSEC RR as result with the NSEC-owner "moon-palace.net" equal the NextOwner "moon-palace.net". So the zone confirmes that no other domain name exists. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


	Status: Good. NXDomain-Proof required and found.


	CNAME-Query sends a valid NSEC RR as result with the NSEC-owner "moon-palace.net" equal the NextOwner "moon-palace.net". So the zone confirmes that no other domain name exists. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


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


	TXT-Query sends a valid NSEC RR as result with the NSEC-owner "moon-palace.net" equal the NextOwner "moon-palace.net". So the zone confirmes that no other domain name exists. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


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


	AAAA-Query sends a valid NSEC RR as result with the NSEC-owner "moon-palace.net" equal the NextOwner "moon-palace.net". So the zone confirmes that no other domain name exists. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


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


	CAA-Query sends a valid NSEC RR as result with the NSEC-owner "moon-palace.net" equal the NextOwner "moon-palace.net". So the zone confirmes that no other domain name exists. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner moon-palace.net., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.10.2025, 00:00:00 +, Signature-Inception: 25.09.2025, 00:00:00 +, KeyTag 53934, Signer-Name: moon-palace.net


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

Zone: www.chat.moon-palace.net
www.chat.moon-palace.net	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "moon-palace.net" and the NextOwner "moon-palace.net". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, NS, SOA, RRSIG, NSEC, DNSKEY

3. Name Servers

Domain	Nameserver	NS-IP
www.chat.moon-palace.net	• ns1.wordpress.com
chat.moon-palace.net	• ns1.wordpress.com / hhn1	198.181.116.9 San Francisco/California/United States (US) - Automattic, Inc	•
	•	2a04:fa87:ffff::c6b5:7409 Dublin/Leinster/Ireland (IE) - Automattic, Inc	•
moon-palace.net	• ns1.wordpress.com / hhn1	198.181.116.9 San Francisco/California/United States (US) - Automattic, Inc	•
	•	2a04:fa87:ffff::c6b5:7409 Dublin/Leinster/Ireland (IE) - Automattic, Inc	•
	• ns2.wordpress.com / hhn1	198.181.117.9 San Francisco/California/United States (US) - Automattic, Inc	•
	•	2a04:fa87:ffff::c6b5:7509 Dublin/Leinster/Ireland (IE) - Automattic, Inc	•
	• ns3.wordpress.com / hhn1	192.0.74.9 San Francisco/California/United States (US) -	•
	•	2620:115:c00f::c000:4a09 San Francisco/California/United States (US) - Automattic, Inc	•
net	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• 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-frmrs-2		•
	• k.gtld-servers.net / nnn1-frmrs-2		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

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

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

Domain:	moon-palace.net
Zone-Name:	moon-palace.net
Primary:	ns1.wordpress.com
Mail:	hostmaster.wordpress.com
Serial:	2025100303
Refresh:	14400
Retry:	7200
Expire:	604800
TTL:	300
num Entries:	6

Domain:	chat.moon-palace.net
Zone-Name:	moon-palace.net
Primary:	ns1.wordpress.com
Mail:	hostmaster.wordpress.com
Serial:	2025100303
Refresh:	14400
Retry:	7200
Expire:	604800
TTL:	300
num Entries:	2

Domain:	www.chat.moon-palace.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	Sec.	G
• http://chat.moon-palace.net/ 73.189.58.197	-102	1.690	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (73.189.58.197:80)

• https://chat.moon-palace.net/ 73.189.58.197	-102	1.710	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (73.189.58.197:443)

• http://chat.moon-palace.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 73.189.58.197	-102	1.606	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (73.189.58.197:80)
Visible Content:

• https://73.189.58.197/ 73.189.58.197	-102	1.734	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (73.189.58.197:443)

7. Comments

	1. General Results, most used to calculate the result
A	name "chat.moon-palace.net" is subdomain, 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: 10583 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: chat.moon-palace.net 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: chat.moon-palace.net 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
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
V	http://chat.moon-palace.net/ 73.189.58.197	-102	Connect failure - perhaps firewall
V	https://chat.moon-palace.net/ 73.189.58.197	-102	Connect failure - perhaps firewall
V	http://chat.moon-palace.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 73.189.58.197	-102	Connect failure - perhaps firewall
V	https://73.189.58.197/ 73.189.58.197	-102	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 chat.moon-palace.net, 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.chat.moon-palace.net
	2. Header-Checks
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 3 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.wordpress.com (198.181.116.9, 2a04:fa87:ffff::c6b5:7409), ns2.wordpress.com (198.181.117.9, 2a04:fa87:ffff::c6b5:7509), ns3.wordpress.com (192.0.74.9, 2620:115:c00f::c000:4a09)
A	Good (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 3 different Name Servers found: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, 3 Name Servers included in Delegation: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, 3 Name Servers included in 1 Zone definitions: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com, 1 Name Servers listed in SOA.Primary: ns1.wordpress.com.
A	Good: Only one SOA.Primary Name Server found.: ns1.wordpress.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns1.wordpress.com.
A	Good: 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.wordpress.com, ns2.wordpress.com, ns3.wordpress.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: 3 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: wordpress.com
A	Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: IE, US
A	Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 192., 198., 2 different subnets (first two Bytes): 192.0., 198.181., 3 different subnets (first three Bytes): 192.0.74., 198.181.116., 198.181.117.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2620:, 2a04:, 2 different subnets (first two blocks): 2620:0115:, 2a04:fa87:, 2 different subnets (first three blocks): 2620:0115:c00f:, 2a04:fa87:ffff:, 2 different subnets (first four blocks): 2620:0115:c00f:0000:, 2a04:fa87:ffff: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: ns1.wordpress.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
	http://chat.moon-palace.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 73.189.58.197	-102	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.
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: 94056 milliseconds, 94.056 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.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

QNr.	Domain	Type	NS used
1	com	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.wordpress.com: 198.181.116.9, 2a04:fa87:ffff::c6b5:7409	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.wordpress.com 198.181.117.9, 2a04:fa87:ffff::c6b5:7509
	Answer: ns3.wordpress.com 192.0.74.9, 2620:115:c00f::c000:4a09
	Answer: ns4.wordpress.com 192.0.75.9, 2620:115:c00f::c000:4b09

14. CAA - Entries

Domainname	Value	∑ Queries
chat.moon-palace.net	no CAA entry found	1
moon-palace.net	no CAA entry found	1
net	no CAA entry found	1

15. TXT - Entries

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

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=1dc77988-73a9-48d3-83bc-11d936762aaa

Last Result: https://check-your-website.server-daten.de/?q=chat.moon-palace.net - 2025-10-03 21:54:48

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

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