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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
16.05.2024 01:05:59

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
foeir.dns.army	A	125.228.132.199 Zhubei/Hsinchu County/Taiwan (TW) - Chunghwa Telecom Co., Ltd. Hostname: 125-228-132-199.hinet-ip.hinet.net	yes	1	0
	AAAA	2001:b011:7008:8a87:4de2:6179:fb19:18ff Hsinchu/Hsinchu City/Taiwan (TW) - Hinet Twnic	yes
www.foeir.dns.army	A		yes	1	0
	AAAA		yes
*.dns.army	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.foeir.dns.army	A		yes
	AAAA		yes
	CNAME		yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 5613, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2024, 00:00:00 +, Signature-Inception: 11.05.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: army
army	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 5296, DigestType 2 and Digest 43OP2vJddwcZHrN8c5JDWIlujQRrjV3fTUBmSr6HKWs=


	1 RRSIG RR to validate DS RR found


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


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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 10254, Flags 256


	Public Key with Algorithm 8, KeyTag 43305, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner army., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2024, 16:20:08 +, Signature-Inception: 09.05.2024, 15:20:08 +, KeyTag 5296, Signer-Name: army


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


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

Zone: dns.army
dns.army	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 "ek9rvc9fsnl7dlck6nagn2cfhv0kl7h0" between the hashed NSEC3-owner "eiugd784cr1h4gafkemkjj96bvp2brmt" and the hashed NextOwner "elp1dtfml3mj1ia163sjs8vpiqtbl6dg". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner eiugd784cr1h4gafkemkjj96bvp2brmt.army., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.05.2024, 16:20:08 +, Signature-Inception: 09.05.2024, 15:20:08 +, KeyTag 10254, Signer-Name: army


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "lqs33f2ss91apsduvg0j35r61furm531" as Owner. That's the Hash of "army" with the NextHashedOwnerName "m0cgg9k8jv3j61v6230joel0qpq44lpf". So that domain name is the Closest Encloser of "dns.army". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner lqs33f2ss91apsduvg0j35r61furm531.army., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.06.2024, 23:01:18 +, Signature-Inception: 15.05.2024, 22:01:18 +, KeyTag 10254, Signer-Name: army


	0 DNSKEY RR found




Zone: foeir.dns.army
foeir.dns.army	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.foeir.dns.army
www.foeir.dns.army	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.foeir.dns.army	• ns1.dynv6.net
foeir.dns.army	• ns1.dynv6.com	95.216.144.82 Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH	•
	•	2a01:4f9:c010:95b:: Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH	•
	• ns1.dynv6.net
	• ns2.dynv6.com	5.45.100.251 Nuremberg/Bavaria/Germany (DE) - netcup GmbH	•
	•	2a03:4000:6:569:: Nuremberg/Bavaria/Germany (DE) - netcup GmbH	•
	• ns3.dynv6.com	159.69.43.243 Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH	•
	•	2a01:4f8:1c1c:4c96:: Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH	•
dns.army	• ns1.dynv6.com	95.216.144.82 Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH
	•	2a01:4f9:c010:95b:: Helsinki/Uusimaa/Finland (FI) - Hetzner Online GmbH
	• ns2.dynv6.com	5.45.100.251 Nuremberg/Bavaria/Germany (DE) - netcup GmbH
	•	2a03:4000:6:569:: Nuremberg/Bavaria/Germany (DE) - netcup GmbH
	• ns3.dynv6.com	159.69.43.243 Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH
	•	2a01:4f8:1c1c:4c96:: Nuremberg/Bavaria/Germany (DE) - Hetzner Online GmbH
army	• v0n0.nic.army / app23.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• v0n1.nic.army / app4.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• v0n2.nic.army / app28.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• v0n3.nic.army / app10.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• v2n0.nic.army / FRA6		•
	• v2n1.nic.army / FRA6		•

4. SOA-Entries

Domain:	army
Zone-Name:	army
Primary:	v0n0.nic.army
Mail:	hostmaster.donuts.email
Serial:	1715813979
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	6

Domain:	dns.army
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	6

Domain:	foeir.dns.army
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	foeir.dns.army
Zone-Name:	foeir.dns.army
Primary:	ns1.dynv6.net
Mail:	hostmaster.dyvn6.net
Serial:	0
Refresh:	3600
Retry:	900
Expire:	604800
TTL:	180
num Entries:	6

Domain:	www.foeir.dns.army
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://foeir.dns.army/ 125.228.132.199	404	Html is minified: 107.41 %	0.594	M
Not Found
Access-Control-Allow-Origin: *
Cache-Control: public, max-age=31536000
Date: Wed, 15 May 2024 23:06:50 GMT
Age: 0
Transfer-Encoding: chunked
Connection: close
Via: http/1.1 traffic_server (ApacheTrafficServer/9.2.4 [c s f ])
Server: ATS/9.2.4

• http://foeir.dns.army/ 2001:b011:7008:8a87:4de2:6179:fb19:18ff	-16		4.077	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [2001:b011:7008:8a87:4de2:6179:fb19:18ff]:80 ([2001:b011:7008:8a87:4de2:6179:fb19:18ff]:80)

• https://foeir.dns.army/ 125.228.132.199	-16		0.593	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://foeir.dns.army/ 2001:b011:7008:8a87:4de2:6179:fb19:18ff	-16		2.034	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [2001:b011:7008:8a87:4de2:6179:fb19:18ff]:443 ([2001:b011:7008:8a87:4de2:6179:fb19:18ff]:443)

• http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.132.199	404		0.590
Not Found
Visible Content:
Date: Wed, 15 May 2024 23:06:57 GMT
Server: ATS/9.2.4
Access-Control-Allow-Origin: *
Set-Cookie: sessid=1; Path=/; Domain=dns.army
Age: 0
Connection: close
Via: http/1.1 traffic_server (ApacheTrafficServer/9.2.4 [cMsSf ])
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:b011:7008:8a87:4de2:6179:fb19:18ff	-16		1.870	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [2001:b011:7008:8a87:4de2:6179:fb19:18ff]:80 ([2001:b011:7008:8a87:4de2:6179:fb19:18ff]:80)
Visible Content:

• https://125.228.132.199/ 125.228.132.199	-16		0.584	P
UnknownError - The SSL connection could not be established, see inner exception. - Authentication failed because the remote party sent a TLS alert: 'HandshakeFailure' (FF: SSL_ERROR_NO_CYPHER_OVERLAP).

• https://[2001:b011:7008:8a87:4de2:6179:fb19:18ff]/ 2001:b011:7008:8a87:4de2:6179:fb19:18ff	-16		1.873	V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [2001:b011:7008:8a87:4de2:6179:fb19:18ff]:443 ([2001:b011:7008:8a87:4de2:6179:fb19:18ff]:443)

7. Comments

	1. General Results, most used to calculate the result
A	name "foeir.dns.army" is subdomain, public suffix is ".army", top-level-domain is ".army", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd.", num .army-domains preloaded: 14 (complete: 244198)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: foeir.dns.army has 2 different ip addresses (authoritative).
A	Good: Ipv4 and Ipv6 addresses per domain name found: foeir.dns.army has 1 ipv4, 1 ipv6 addresses
A	Good: No asked Authoritative Name Server had a timeout
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
	http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.132.199	404	sessid=1; Path=/; Domain=dns.army	Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
B	http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.132.199	404	sessid=1; Path=/; Domain=dns.army	Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
K	http://foeir.dns.army/ 125.228.132.199, Status 404		http://foeir.dns.army/ 2001:b011:7008:8a87:4de2:6179:fb19:18ff, Status -16	Configuration problem - different ip addresses with different status
K	http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.132.199, Status 404		http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:b011:7008:8a87:4de2:6179:fb19:18ff, Status -16	Configuration problem - different ip addresses with different status
M	http://foeir.dns.army/ 125.228.132.199	404		Misconfiguration - main pages should never send http status 400 - 499
X	Fatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 95.216.144.82: NXDOMAIN
X	Fatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 2a01:4f9:c010:95b::: NXDOMAIN
X	Fatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 5.45.100.251: NXDOMAIN
X	Fatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 2a03:4000:6:569::: NXDOMAIN
X	Fatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 159.69.43.243: NXDOMAIN
X	Fatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: NXDOMAIN
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain foeir.dns.army, 2 ip addresses.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain foeir.dns.army, 2 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.foeir.dns.army
	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:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
A	Info:: 12 Queries complete, 12 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns1.dynv6.com, ns1.dynv6.net, ns2.dynv6.com, ns3.dynv6.com, 3 Name Servers included in Delegation: ns1.dynv6.com, ns2.dynv6.com, ns3.dynv6.com, 3 Name Servers included in 2 Zone definitions: ns1.dynv6.com, ns2.dynv6.com, ns3.dynv6.com, 1 Name Servers listed in SOA.Primary: ns1.dynv6.net.
A	Good: Only one SOA.Primary Name Server found.: ns1.dynv6.net.
	Error: SOA.Primary Name Server not included in the delegation set.: ns1.dynv6.net.
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.dynv6.com, ns2.dynv6.com, ns3.dynv6.com
A	Good: All Name Server Domain Names have a Public Suffix.
	Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

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
A	Good: Name Servers with different domain names found.: 2 different Domains found
A	Good: Name servers with different Country locations found: 3 Name Servers, 2 Countries: DE, FI
A	Info: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 159., 5., 95., 3 different subnets (first two Bytes): 159.69., 5.45., 95.216., 3 different subnets (first three Bytes): 159.69.43., 5.45.100., 95.216.144.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2a01:, 2a03:, 3 different subnets (first two blocks): 2a01:04f8:, 2a01:04f9:, 2a03:4000:, 3 different subnets (first three blocks): 2a01:04f8:1c1c:, 2a01:04f9:c010:, 2a03:4000:0006:, 3 different subnets (first four blocks): 2a01:04f8:1c1c:4c96:, 2a01:04f9:c010:095b:, 2a03:4000:0006:0569:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynv6.com
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynv6.com
X	Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.dynv6.com
	Nameserver doesn't pass all EDNS-Checks: ns1.dynv6.com / 95.216.144.82: 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.dynv6.com / 95.216.144.82: 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.dynv6.com / 2a01:4f9:c010:95b::: 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.dynv6.com / 2a01:4f9:c010:95b::: 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.dynv6.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.dynv6.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: ns2.dynv6.com / 5.45.100.251: 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: ns2.dynv6.com / 5.45.100.251: 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: ns2.dynv6.com / 2a03:4000:6:569::: 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: ns2.dynv6.com / 2a03:4000:6:569::: 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: ns3.dynv6.com / 159.69.43.243: 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: ns3.dynv6.com / 159.69.43.243: 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: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: 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: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: 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://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:b011:7008:8a87:4de2:6179:fb19:18ff	-16		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.
	http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:b011:7008:8a87:4de2:6179:fb19:18ff, Status -16		http://foeir.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 125.228.132.199, Status 404	Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. 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: 101340 milliseconds, 101.340 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/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

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

QNr.	Domain	Type	NS used
1	com	NS	c.root-servers.net (2001:500:2::c)
	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.dynv6.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
3	ns2.dynv6.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
4	ns3.dynv6.com	NS	e.gtld-servers.net (2001:502:1ca1::30)
	Answer: ns1.digineo.de, ns2.digineo.de, ns3.digineo.de
5	de	NS	a.root-servers.net (2001:503:ba3e::2:30)
	Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
6	ns1.digineo.de: 2a03:4000:6:568::1, 5.45.100.168	NS	a.nic.de (2001:678:2::53)
	Answer: ns3.digineo.de 185.117.215.53, 2a06:8781::53
	Answer: ns2.digineo.de 195.201.93.228, 2a01:4f8:1c1c:5172::1
7	ns1.dynv6.com: 95.216.144.82	A	ns1.digineo.de (2a03:4000:6:568::1)
8	ns1.dynv6.com: 2a01:4f9:c010:95b::	AAAA	ns1.digineo.de (2a03:4000:6:568::1)
9	ns2.dynv6.com: 5.45.100.251	A	ns1.digineo.de (2a03:4000:6:568::1)
10	ns2.dynv6.com: 2a03:4000:6:569::	AAAA	ns1.digineo.de (2a03:4000:6:568::1)
11	ns3.dynv6.com: 159.69.43.243	A	ns1.digineo.de (2a03:4000:6:568::1)
12	ns3.dynv6.com: 2a01:4f8:1c1c:4c96::	AAAA	ns1.digineo.de (2a03:4000:6:568::1)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
www.foeir.dns.army	0	no CAA entry found	1
foeir.dns.army	0	no CAA entry found	1
dns.army	-3	Name Error - The domain name does not exist	1
army	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
dns.army	Name Error - The domain name does not exist	1
foeir.dns.army	ok	1
www.foeir.dns.army	ok	1
_acme-challenge.foeir.dns.army	missing entry or wrong length	1
_acme-challenge.www.foeir.dns.army	missing entry or wrong length	1
_acme-challenge.foeir.dns.army.dns.army	Name Error - The domain name does not exist	1
_acme-challenge.foeir.dns.army.foeir.dns.army	perhaps wrong	1
_acme-challenge.www.foeir.dns.army.foeir.dns.army	perhaps wrong	1
_acme-challenge.www.foeir.dns.army.www.foeir.dns.army	perhaps wrong	1

16. DomainService - Entries

Type		Domain	Pref	Value	DNS-error	num Answers	Status	Description
_dmarc	TXT	_dmarc.foeir.dns.army			0	0	ok

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=7daea7e2-6c7a-4f65-9914-9a9ef9b98c3b

Last Result: https://check-your-website.server-daten.de/?q=foeir.dns.army - 2024-05-16 01:05:59

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

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