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




Y

Private IP-Address found

Checked:
10.06.2019 12:28:18


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
7257939.dns.army
A
178.172.147.98
Brest/Brestskaya Voblasts'/BY
Hostname: ns2.elsat.by
yes
1
0

AAAA
2001:0:53aa:64c:3023:69ff:4d53:6c9d

yes


www.7257939.dns.army
A

yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (beta)

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



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 25266, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2019, 00:00:00, Signature-Inception: 10.06.2019, 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
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2019, 05:00:00, Signature-Inception: 10.06.2019, 04:00:00, KeyTag 25266, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 61320, Flags 256



2 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.07.2019, 02:14:54, Signature-Inception: 04.06.2019, 01:53:13, KeyTag 57592, Signer-Name: army



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.07.2019, 02:14:54, Signature-Inception: 04.06.2019, 01:53:13, KeyTag 61320, Signer-Name: army



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 57592, DigestType 1 and Digest "gQmjajBe1jf1IZeTVtM1OVF7zNY=" 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 8, KeyTag 57592, DigestType 2 and Digest "hq/aR52TfvzBDRPu6qSjNuqBOMh42H1AhUbKRHvHyz8=" 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 domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.



0 DNSKEY RR found





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



0 DNSKEY RR found





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


3. Name Servers

DomainNameserverNS-IP
www.7257939.dns.army
 

7257939.dns.army
U  ns1.dynv6.com
95.216.144.82
/FI


U 
2a01:4f9:c010:95b::
Gunzenhausen/Bayern/DE


U  ns2.dynv6.com
185.55.116.153
Bremen/DE


U 
2a00:c380:c0de::5353
Bremen/DE


U  ns3.dynv6.com
159.69.43.243
/DE


U 
2a01:4f8:1c1c:4c96::
Gunzenhausen/Bayern/DE

dns.army
U  ns1.dynv6.com


U  ns2.dynv6.com


U  ns3.dynv6.com

army
X  demand.alpha.aridns.net.au / dns4.sjc


  demand.beta.aridns.net.au / dns3.ams


  demand.delta.aridns.net.au / dns5.ams


  demand.gamma.aridns.net.au / dns2.ams


4. SOA-Entries


Domain:army
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1560162193
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:7257939.dns.army
Primary:ns1.dynv6.net
Mail:hostmaster.dyvn6.net
Serial:0
Refresh:1800
Retry:3600
Expire:86400
TTL:60
num Entries:6


5. Url-Checks

Domainname Http-StatusredirectSec.G
• http://7257939.dns.army/
178.172.147.98
-14

10.030
T
Timeout - The operation has timed out

• https://7257939.dns.army/
178.172.147.98
-14

10.036
T
Timeout - The operation has timed out

• http://7257939.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.172.147.98
-14

10.026
T
Timeout - The operation has timed out
Visible Content:

6. Comments

Aname "7257939.dns.army" is subdomain, public suffix is "army", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd."
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: demand.alpha.aridns.net.au: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 95.216.144.82:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 95.216.144.82: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 95.216.144.82:53
XFatal error: Nameserver doesn't support TCP connection: ns1.dynv6.com / 2a01:4f9:c010:95b::: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a01:4f9:c010:95b::]:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 185.55.116.153:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 185.55.116.153: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 185.55.116.153:53
XFatal error: Nameserver doesn't support TCP connection: ns2.dynv6.com / 2a00:c380:c0de::5353: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a00:c380:c0de::5353]:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 159.69.43.243:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 159.69.43.243: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 159.69.43.243:53
XFatal error: Nameserver doesn't support TCP connection: ns3.dynv6.com / 2a01:4f8:1c1c:4c96::: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it [2a01:4f8:1c1c:4c96::]:53
Y7257939.dns.army

2001:0:53aa:64c:3023:69ff:4d53:6c9d
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 2001:0000:0000:0000:0000:0000:0000:0000 to 2001:0000:ffff:ffff:ffff:ffff:ffff:ffff: Teredo tunneling
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.dynv6.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.dynv6.com
XFatal 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: demand.beta.aridns.net.au: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns3.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: demand.delta.aridns.net.au: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns5.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: demand.gamma.aridns.net.au: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns2.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.dynv6.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.
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: ns2.dynv6.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.
Nameserver doesn't pass all EDNS-Checks: ns2.dynv6.com / 185.55.116.153: 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 / 2a00:c380:c0de::5353: 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: 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.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
http://7257939.dns.army/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.172.147.98
-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.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 132903 milliseconds, 132.903 seconds


7. Connections

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow.

No CRT - CT-Log entries found


10. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


11. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.7257939.dns.army
0

no CAA entry found
1
0
7257939.dns.army
0

no CAA entry found
1
0
dns.army
-3

Name Error - The domain name does not exist
1
0
army
0

no CAA entry found
1
0


12. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dns.army

Name Error - The domain name does not exist
1
0
7257939.dns.army

ok
1
0
www.7257939.dns.army

ok
1
0
_acme-challenge.7257939.dns.army

missing entry or wrong length
1
0
_acme-challenge.www.7257939.dns.army

missing entry or wrong length
1
0
_acme-challenge.7257939.dns.army.dns.army

Name Error - The domain name does not exist
1
0
_acme-challenge.7257939.dns.army.7257939.dns.army

perhaps wrong
1
0
_acme-challenge.www.7257939.dns.army.7257939.dns.army

perhaps wrong
1
0
_acme-challenge.www.7257939.dns.army.www.7257939.dns.army

perhaps wrong
1
0


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=18ed5c88-4c85-4406-b3cb-e5308f5211a7


Last Result: https://check-your-website.server-daten.de/?q=7257939.dns.army - 2019-06-10 12:28:18


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

<a href="https://check-your-website.server-daten.de/?q=7257939.dns.army" target="_blank">Check this Site: 7257939.dns.army</a>