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




R

Redirect to not existing domain

Checked:
29.06.2020 22:24:19


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mybannerlord.com
A

yes
1
0

AAAA

yes


www.mybannerlord.com
A
82.67.32.198
Sainte-Foy-les-Lyon/Auvergne-Rhone-Alpes/France (FR) - Proxad / Free SAS
Hostname: ril69-1_migr-82-67-32-198.fbx.proxad.net
yes
1
0

AAAA

yes


*.mybannerlord.com
A
82.67.32.198
yes



AAAA

yes



CNAME

yes



2. DNSSEC

Zone (*)DNSSEC - Informations (some minor bugs wildcard + nsec/nsec3)

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



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



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 46594, Flags 256



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



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



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

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



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.07.2020, 17:00:00 +, Signature-Inception: 29.06.2020, 16:00:00 +, KeyTag 48903, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 39844, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.07.2020, 18:24:21 +, Signature-Inception: 24.06.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

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



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "78bfl9nlkfge31utkvodjrsnpbrs3qv9" between the hashed NSEC3-owner "78bejsk5eaov9li4c5ll77mlkebgmtca" and the hashed NextOwner "78bfnpc5ge2i0rr0ue3n1hhkj3vuigcr". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 78bejsk5eaov9li4c5ll77mlkebgmtca.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.07.2020, 06:17:34 +, Signature-Inception: 29.06.2020, 05:07:34 +, KeyTag 39844, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "mybannerlord.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 04.07.2020, 04:41:05 +, Signature-Inception: 27.06.2020, 03:31:05 +, KeyTag 39844, Signer-Name: com



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.mybannerlord.com
  ns1.gandi.net

mybannerlord.com
  ns1.gandi.net / livedns-nshost10
173.246.98.2
Paris/Île-de-France/France (FR) - Gandi US Inc


 
2604:3400:abca::2
Paris/Île-de-France/France (FR) - Gandi US Inc


  ns-192-c.gandi.net / node-berlin1
217.70.187.193
Newark/New Jersey/United States (US) - GANDI is an ICANN accredited registrar


 
2604:3400:aaac::c1
Clichy-sous-Bois/Île-de-France/France (FR) - Gandi US Inc


  ns-41-a.gandi.net / node-berlin1
173.246.100.42
Paris/Île-de-France/France (FR) - Gandi US Inc


 
2001:4b98:aaaa::2a
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar


  ns-50-b.gandi.net / node-berlin1
213.167.230.51
Paris/Île-de-France/France (FR) - Gandi SAS


 
2001:4b98:aaab::33
Paris/Île-de-France/France (FR) - GANDI is an ICANN accredited registrar

com
  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


4. SOA-Entries


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


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


Domain:mybannerlord.com
Zone-Name:mybannerlord.com
Primary:ns1.gandi.net
Mail:hostmaster.gandi.net
Serial:1593455988
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:8


Domain:www.mybannerlord.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://www.mybannerlord.com/
82.67.32.198
301
http://mybannerlord.com
Html is minified: 108.19 %
0.093
D
Server: nginx/1.14.2
Date: Mon, 29 Jun 2020 20:24:54 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: http://mybannerlord.com

• http://mybannerlord.com

-1

0.043
R
NameResolutionFailure - The remote name could not be resolved: 'mybannerlord.com'

• https://www.mybannerlord.com/
82.67.32.198
-14

10.023
T
Timeout - The operation has timed out

• http://www.mybannerlord.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
82.67.32.198
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
http://mybannerlord.com
Html is minified: 108.19 %
0.090
D
Visible Content: 301 Moved Permanently nginx/1.14.2
Server: nginx/1.14.2
Date: Mon, 29 Jun 2020 20:25:04 GMT
Content-Type: text/html
Content-Length: 185
Connection: close
Location: http://mybannerlord.com

• https://82.67.32.198/
82.67.32.198
-14

10.036
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "mybannerlord.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Warning: Only one ip address found: www.mybannerlord.com has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: www.mybannerlord.com has no ipv6 address.
Agood: 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.
CError - no version with Http-Status 200
Dhttp://www.mybannerlord.com/ 82.67.32.198
301
http://mybannerlord.com
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.mybannerlord.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.67.32.198
301
http://mybannerlord.com
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
Rhttp://www.mybannerlord.com/ 82.67.32.198
301
http://mybannerlord.com
redirect to not existing domain
Rhttp://www.mybannerlord.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.67.32.198
301
http://mybannerlord.com
redirect to not existing domain
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 www.mybannerlord.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.gandi.net, ns-192-c.gandi.net, ns-41-a.gandi.net, ns-50-b.gandi.net, 3 Name Servers included in Delegation: ns-192-c.gandi.net, ns-41-a.gandi.net, ns-50-b.gandi.net, 3 Name Servers included in 1 Zone definitions: ns-192-c.gandi.net, ns-41-a.gandi.net, ns-50-b.gandi.net, 1 Name Servers listed in SOA.Primary: ns1.gandi.net.
AGood: Only one SOA.Primary Name Server found.: ns1.gandi.net.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.gandi.net.
AGood: 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: ns-192-c.gandi.net, ns-41-a.gandi.net, ns-50-b.gandi.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: gandi.net
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: FR, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 173., 213., 217., 3 different subnets (first two Bytes): 173.246., 213.167., 217.70., 4 different subnets (first three Bytes): 173.246.100., 173.246.98., 213.167.230., 217.70.187.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2604:, 2 different subnets (first two blocks): 2001:4b98:, 2604:3400:, 4 different subnets (first three blocks): 2001:4b98:aaaa:, 2001:4b98:aaab:, 2604:3400:aaac:, 2604:3400:abca:, 4 different subnets (first four blocks): 2001:4b98:aaaa:0000:, 2001:4b98:aaab:0000:, 2604:3400:aaac:0000:, 2604:3400:abca:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.gandi.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.
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.

3. Content- and Performance-critical Checks

Fatal: All checks of /.well-known/acme-challenge/random-filename have a redirect, destination doesn't have the random filename. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 71143 milliseconds, 71.143 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" > 2019 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.gandi.net, ns-192-c.gandi.net, ns-41-a.gandi.net, ns-50-b.gandi.net

QNr.DomainTypeNS used
1
net
NS
e.root-servers.net (2001:500:a8::e)

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.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5
3
ns-192-c.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5
4
ns-41-a.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5
5
ns-50-b.gandi.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns0.gandi.net, dns1.gandi.net, dns2.gandi.net, dns3.gandi.net, dns4.gandi.net, dns6.gandi.net

Answer: dns0.gandi.net
2001:4b98:d:1::39, 217.70.177.39

Answer: dns1.gandi.net
2001:4b98:d:1::45, 217.70.177.45

Answer: dns2.gandi.net
2001:4b98:d:589::211, 217.70.183.211

Answer: dns3.gandi.net
2001:4b98:c:13::14, 217.70.184.14

Answer: dns4.gandi.net
2001:4b98:dc2:90:217:70:186:184, 217.70.186.184

Answer: dns6.gandi.net
162.159.24.111, 162.159.25.213, 2400:cb00:2049:1::a29f:186f, 2400:cb00:2049:1::a29f:19d5
6
ns1.gandi.net: 173.246.98.2
A
dns0.gandi.net (2001:4b98:d:1::39)
7
ns1.gandi.net: 2604:3400:abca::2
AAAA
dns0.gandi.net (2001:4b98:d:1::39)
8
ns-192-c.gandi.net: 217.70.187.193
A
dns0.gandi.net (2001:4b98:d:1::39)
9
ns-192-c.gandi.net: 2604:3400:aaac::c1
AAAA
dns0.gandi.net (2001:4b98:d:1::39)
10
ns-41-a.gandi.net: 173.246.100.42
A
dns0.gandi.net (2001:4b98:d:1::39)
11
ns-41-a.gandi.net: 2001:4b98:aaaa::2a
AAAA
dns0.gandi.net (2001:4b98:d:1::39)
12
ns-50-b.gandi.net: 213.167.230.51
A
dns0.gandi.net (2001:4b98:d:1::39)
13
ns-50-b.gandi.net: 2001:4b98:aaab::33
AAAA
dns0.gandi.net (2001:4b98:d:1::39)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.mybannerlord.com
0

no CAA entry found
1
0
mybannerlord.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mybannerlord.com
v=spf1 include:_mailcust.gandi.net ?all
ok
1
0
www.mybannerlord.com

ok
1
0
_acme-challenge.mybannerlord.com

missing entry or wrong length
1
0
_acme-challenge.www.mybannerlord.com

Name Error - The domain name does not exist
1
0
_acme-challenge.mybannerlord.com.mybannerlord.com

perhaps wrong
1
0
_acme-challenge.www.mybannerlord.com.mybannerlord.com

perhaps wrong
1
0
_acme-challenge.www.mybannerlord.com.www.mybannerlord.com

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=0736d8af-4210-483b-84ea-781b3087fbba


Last Result: https://check-your-website.server-daten.de/?q=mybannerlord.com - 2020-06-29 22:24:19


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

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