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




T

Timeout

Checked:
12.02.2024 14:46:46


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
gunbridge.ca
A
3.33.152.147
Seattle/Washington/United States (US) - Amazon.com, Inc.
Hostname: a4ec4c6ea1c92e2e6.awsglobalaccelerator.com
yes
2
0

A
15.197.142.173
Seattle/Washington/United States (US) - Amazon.com, Inc.
Hostname: a4ec4c6ea1c92e2e6.awsglobalaccelerator.com
yes
2
0

AAAA

yes


www.gunbridge.ca
CNAME
gunbridge.ca
yes
1
0

A
3.33.152.147
Seattle/Washington/United States (US) - Amazon.com, Inc.
Hostname: a4ec4c6ea1c92e2e6.awsglobalaccelerator.com
yes



A
15.197.142.173
Seattle/Washington/United States (US) - Amazon.com, Inc.
Hostname: a4ec4c6ea1c92e2e6.awsglobalaccelerator.com
yes


*.gunbridge.ca
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 30903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.03.2024, 00:00:00 +, Signature-Inception: 10.02.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: ca
ca
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 18560, DigestType 2 and Digest huwo7Vv/B2GGMG3IzjtOPsBDPZ1dNMfKjax7GTTosyQ=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ca., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.02.2024, 05:00:00 +, Signature-Inception: 12.02.2024, 04:00:00 +, KeyTag 30903, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 56816, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ca., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 16.02.2024, 05:18:24 +, Signature-Inception: 09.02.2024, 01:07:25 +, KeyTag 18560, Signer-Name: ca



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



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

Zone: gunbridge.ca
gunbridge.ca
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 "28nld0bvuu4vp73qe8ovuijbo4m1vgu0" between the hashed NSEC3-owner "28nhipp06e7njccc4q38h78u8k3ju67u" and the hashed NextOwner "28o767la0l07jvrdvhnp9dk6d39ab5u1". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 28nhipp06e7njccc4q38h78u8k3ju67u.ca., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.02.2024, 11:36:17 +, Signature-Inception: 11.02.2024, 04:37:12 +, KeyTag 56816, Signer-Name: ca



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "r66k981mhm0vmpsgv1djat7janroai95" as Owner. That's the Hash of "ca" with the NextHashedOwnerName "r66pg9pttik20okt0j69v3is2m57vek9". So that domain name is the Closest Encloser of "gunbridge.ca". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner r66k981mhm0vmpsgv1djat7janroai95.ca., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 15.02.2024, 21:29:35 +, Signature-Inception: 08.02.2024, 12:07:42 +, KeyTag 56816, Signer-Name: ca



0 DNSKEY RR found




Zone: www.gunbridge.ca
www.gunbridge.ca
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
gunbridge.ca
  ns53.domaincontrol.com / hex:0D 70 31 33
97.74.106.27
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:21a2::1b
Tempe/Arizona/United States (US) - Host Europe GmbH


  ns54.domaincontrol.com / hex:0D 70 31 36
173.201.74.27
Tempe/Arizona/United States (US) - Host Europe GmbH


 
2603:5:22a2::1b
Tempe/Arizona/United States (US) - Host Europe GmbH

ca
  any.ca-servers.ca / LHR4


  c.ca-servers.ca / FRA1


  d.ca-servers.ca / ns-2.cira.de8.bind


  j.ca-servers.ca


  prd-czp-05.corp.cira.ca


4. SOA-Entries


Domain:ca
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:ca
Zone-Name:ca
Primary:prd-czp-05.corp.cira.ca
Mail:admin-dns.cira.ca
Serial:2402121330
Refresh:2100
Retry:900
Expire:3456000
TTL:3600
num Entries:4


Domain:gunbridge.ca
Zone-Name:gunbridge.ca
Primary:ns53.domaincontrol.com
Mail:dns.jomax.net
Serial:2024021000
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


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://gunbridge.ca/
3.33.152.147
301
https://gunbridge.dyndns-office.com/
Html is minified: 102.94 %
0.053
E
Date: Mon, 12 Feb 2024 13:47:10 GMT
Connection: close
Location: https://gunbridge.dyndns-office.com/
Server: ip-100-74-3-240.eu-west-2.compute.internal
X-Request-ID: ab64509e-893c-44c8-89b3-5071a9725c1d
Content-Type: text/html; charset=utf-8
Content-Length: 70

• http://gunbridge.ca/
15.197.142.173
301
https://gunbridge.dyndns-office.com/
Html is minified: 102.94 %
0.063
E
Date: Mon, 12 Feb 2024 13:47:10 GMT
Connection: close
Location: https://gunbridge.dyndns-office.com/
Server: ip-100-74-3-176.eu-west-2.compute.internal
X-Request-ID: 1711f9d4-0231-4711-94a7-eefcc31a0172
Content-Type: text/html; charset=utf-8
Content-Length: 70

• http://www.gunbridge.ca/
3.33.152.147
301
https://gunbridge.dyndns-office.com/
Html is minified: 102.94 %
0.064
E
Date: Mon, 12 Feb 2024 13:47:10 GMT
Connection: close
Location: https://gunbridge.dyndns-office.com/
Server: ip-100-74-2-113.eu-west-2.compute.internal
X-Request-ID: 95316c91-98a9-458f-b273-f69947a05576
Content-Type: text/html; charset=utf-8
Content-Length: 70

• http://www.gunbridge.ca/
15.197.142.173
301
https://gunbridge.dyndns-office.com/
Html is minified: 102.94 %
0.086
E
Date: Mon, 12 Feb 2024 13:47:10 GMT
Connection: close
Location: https://gunbridge.dyndns-office.com/
Server: ip-100-74-3-138.eu-west-2.compute.internal
X-Request-ID: 12fdc8c8-d19c-414e-a203-fed89c80d59f
Content-Type: text/html; charset=utf-8
Content-Length: 70

• https://gunbridge.ca/
3.33.152.147
-14

10.003
T
Timeout - The operation has timed out.

• https://gunbridge.ca/
15.197.142.173
-14

10.020
T
Timeout - The operation has timed out.

• https://www.gunbridge.ca/
3.33.152.147
-14

10.020
T
Timeout - The operation has timed out.

• https://www.gunbridge.ca/
15.197.142.173
-14

10.017
T
Timeout - The operation has timed out.

• https://gunbridge.dyndns-office.com/

-14

10.014
T
Timeout - The operation has timed out.

• http://gunbridge.ca/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.152.147
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.054
A
Not Found
Visible Content:
Date: Mon, 12 Feb 2024 13:47:50 GMT
Connection: close
Server: ip-100-74-3-138.eu-west-2.compute.internal
X-Request-ID: 05556370-af33-4eac-994b-d840ecc490ff
Content-Type: text/html; charset=utf-8
Content-Length: 125

• http://gunbridge.ca/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.142.173
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.060
A
Not Found
Visible Content:
Date: Mon, 12 Feb 2024 13:47:50 GMT
Connection: close
Server: ip-100-74-3-204.eu-west-2.compute.internal
X-Request-ID: 9b9c2621-ea8f-4e5d-9479-ef833ef079c1
Content-Type: text/html; charset=utf-8
Content-Length: 125

• http://www.gunbridge.ca/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.33.152.147
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.053
A
Not Found
Visible Content:
Date: Mon, 12 Feb 2024 13:47:50 GMT
Connection: close
Server: ip-100-74-2-64.eu-west-2.compute.internal
X-Request-ID: cc20cfbc-45a6-4007-8b8b-e73f2c7d7af0
Content-Type: text/html; charset=utf-8
Content-Length: 125

• http://www.gunbridge.ca/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
15.197.142.173
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.047
A
Not Found
Visible Content:
Date: Mon, 12 Feb 2024 13:47:50 GMT
Connection: close
Server: ip-100-74-2-104.eu-west-2.compute.internal
X-Request-ID: 1830395f-cf7a-4cd7-ba69-3fcf23a23b30
Content-Type: text/html; charset=utf-8
Content-Length: 125

• https://3.33.152.147/
3.33.152.147
-14

10.007
T
Timeout - The operation has timed out.

• https://15.197.142.173/
15.197.142.173
-14

10.010
T
Timeout - The operation has timed out.

7. Comments


1. General Results, most used to calculate the result

Aname "gunbridge.ca" is domain, public suffix is ".ca", top-level-domain is ".ca", top-level-domain-type is "country-code", Country is Canada, tld-manager is "Canadian Internet Registration Authority (CIRA) Autorité Canadienne pour les enregistrements Internet (ACEI)", num .ca-domains preloaded: 1478 (complete: 239099)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: gunbridge.ca has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.gunbridge.ca has 2 different ip addresses (authoritative).
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: gunbridge.ca has no ipv6 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.gunbridge.ca has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - no version with Http-Status 200
Ehttp://gunbridge.ca/ 3.33.152.147
301
https://gunbridge.dyndns-office.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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.
Ehttp://gunbridge.ca/ 15.197.142.173
301
https://gunbridge.dyndns-office.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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.
Ehttp://www.gunbridge.ca/ 3.33.152.147
301
https://gunbridge.dyndns-office.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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.
Ehttp://www.gunbridge.ca/ 15.197.142.173
301
https://gunbridge.dyndns-office.com/
Wrong redirect one domain http to other domain https. First redirect to https without new dns query, 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
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain gunbridge.ca, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.gunbridge.ca, 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 gunbridge.ca, 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 www.gunbridge.ca, 2 ip addresses.
BNo _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.gunbridge.ca

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 29 Queries complete, 29 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 14.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns53.domaincontrol.com, ns54.domaincontrol.com, 2 Name Servers included in Delegation: ns53.domaincontrol.com, ns54.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns53.domaincontrol.com, ns54.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns53.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns53.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns53.domaincontrol.com.
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: ns53.domaincontrol.com, ns54.domaincontrol.com
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: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 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.: 2 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: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.74., 97.74.106.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21a2:, 2603:0005:22a2:, 2 different subnets (first four blocks): 2603:0005:21a2:0000:, 2603:0005:22a2:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: prd-czp-05.corp.cira.ca: 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.

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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
AInfo: Different Server-Headers found
ADuration: 164067 milliseconds, 164.067 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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns53.domaincontrol.com, ns54.domaincontrol.com

QNr.DomainTypeNS used
1
com
NS
k.root-servers.net (2001:7fd::1)

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

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns54.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
4
net
NS
h.root-servers.net (2001:500:1::53)

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

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
6
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
7
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
8
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
9
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
10
a9-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
11
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
2600:1480:1::43, 84.53.139.67

Answer: a12-67.akam.net
184.26.160.67, 2600:1480:f000::43

Answer: a18-67.akam.net
2600:1480:4800::43, 95.101.36.67

Answer: a22-67.akam.net
23.211.61.67, 2600:1480:7800::43

Answer: a28-67.akam.net
2600:1480:d800::43, 95.100.173.67

Answer: a4-67.akam.net
2600:1480:9000::43, 72.246.46.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a9-67.akam.net: 184.85.248.67
A
a1-67.akam.net (2600:1401:2::43)
23
a9-67.akam.net: 2a02:26f0:117::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
25
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
26
ns53.domaincontrol.com: 97.74.106.27
A
a1-245.akam.net (2600:1401:2::f5)
27
ns53.domaincontrol.com: 2603:5:21a2::1b
AAAA
a1-245.akam.net (2600:1401:2::f5)
28
ns54.domaincontrol.com: 173.201.74.27
A
a1-245.akam.net (2600:1401:2::f5)
29
ns54.domaincontrol.com: 2603:5:22a2::1b
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.gunbridge.ca



1
0
gunbridge.ca
0

no CAA entry found
1
0
ca
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
gunbridge.ca
NETORGFT3964007.onmicrosoft.com
ok
1
0
gunbridge.ca
v=spf1 include:secureserver.net -all
ok
1
0
www.gunbridge.ca
NETORGFT3964007.onmicrosoft.com
ok
1
0
www.gunbridge.ca
v=spf1 include:secureserver.net -all
ok
1
0
_acme-challenge.gunbridge.ca

Name Error - The domain name does not exist
1
0
_acme-challenge.www.gunbridge.ca

Name Error - The domain name does not exist
1
0
_acme-challenge.gunbridge.ca.gunbridge.ca

Name Error - The domain name does not exist
1
0
_acme-challenge.www.gunbridge.ca.gunbridge.ca

Name Error - The domain name does not exist
1
0
_acme-challenge.www.gunbridge.ca.www.gunbridge.ca

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

gunbridge.ca
0
gunbridge-ca.mail.protection.outlook.com
01ok

A


104.47.75.164
02ok

A


104.47.75.228
02ok

CNAME


-40ok



16. Cipher Suites

No results


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=d2a1443d-e3f4-47bb-af6c-f74f99d5c90e


Last Result: https://check-your-website.server-daten.de/?q=gunbridge.ca - 2024-02-12 14:46:46


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro