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



Y

Private IP-Address found

Checked:
17.10.2020 22:43:59


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
microserver.bhamber.com
A
192.168.1.9
No Hostname found
yes
1
0

AAAA

yes


www.microserver.bhamber.com

Name Error
yes
1
0
*.bhamber.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.microserver.bhamber.com
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 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.11.2020, 00:00:00 +, Signature-Inception: 11.10.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: 30.10.2020, 17:00:00 +, Signature-Inception: 17.10.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24966, Flags 256



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



Public Key with Algorithm 8, KeyTag 31510, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.10.2020, 18:24:21 +, Signature-Inception: 12.10.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: bhamber.com
bhamber.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 "a2o0vsrjh4g4l3kr3kqvtennej57e76a" between the hashed NSEC3-owner "a2o0ubd0q1qhj50n95ok731qe59b3lkp" and the hashed NextOwner "a2o1ovg0qtj3vjl115qeb7klp6sjcpfu". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner a2o0ubd0q1qhj50n95ok731qe59b3lkp.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 21.10.2020, 05:07:33 +, Signature-Inception: 14.10.2020, 03:57:33 +, KeyTag 24966, 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 "bhamber.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: 24.10.2020, 04:40:34 +, Signature-Inception: 17.10.2020, 03:30:34 +, KeyTag 31510, Signer-Name: com



0 DNSKEY RR found




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



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.microserver.bhamber.com
  ns-1727.awsdns-23.co.uk

microserver.bhamber.com
  ns-1727.awsdns-23.co.uk / fb57a6fe339387cfd565b64c08bfd3dc -
205.251.198.191
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5306:bf00::1
Seattle/Washington/United States (US) - Amazon.com

bhamber.com
  ns-1473.awsdns-56.org / 1b0dd431bbab75f1ba38c5bd87648827 -
205.251.197.193
London/England/United Kingdom (GB) - Amazon.com


 
2600:9000:5305:c100::1
Seattle/Washington/United States (US) - Amazon.com


  ns-1727.awsdns-23.co.uk / fb57a6fe339387cfd565b64c08bfd3dc -
205.251.198.191
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5306:bf00::1
Seattle/Washington/United States (US) - Amazon.com


  ns-313.awsdns-39.com / e840d1d24c21e46bd443779147818174 -
205.251.193.57
Paris/Île-de-France/France (FR) - Amazon.com


 
2600:9000:5301:3900::1
Seattle/Washington/United States (US) - Amazon.com


  ns-528.awsdns-02.net / 6df7fc212dedb98a3f7d9c6be85bafd6 -
205.251.194.16
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5302:1000::1
Seattle/Washington/United States (US) - Amazon.com

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:1602967419
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:10


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


Domain:bhamber.com
Zone-Name:bhamber.com
Primary:ns-1727.awsdns-23.co.uk
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:microserver.bhamber.com
Zone-Name:bhamber.com
Primary:ns-1727.awsdns-23.co.uk
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


Domain:www.microserver.bhamber.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







7. Comments


1. General Results, most used to calculate the result

Aname "microserver.bhamber.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 52208 (complete: 131120)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Ymicroserver.bhamber.com

192.168.1.9
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: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: 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.
AInfo:: 4 different Name Servers found: ns-1473.awsdns-56.org, ns-1727.awsdns-23.co.uk, ns-313.awsdns-39.com, ns-528.awsdns-02.net, 4 Name Servers included in Delegation: ns-1473.awsdns-56.org, ns-1727.awsdns-23.co.uk, ns-313.awsdns-39.com, ns-528.awsdns-02.net, 4 Name Servers included in 1 Zone definitions: ns-1473.awsdns-56.org, ns-1727.awsdns-23.co.uk, ns-313.awsdns-39.com, ns-528.awsdns-02.net, 1 Name Servers listed in SOA.Primary: ns-1727.awsdns-23.co.uk.
AGood: Only one SOA.Primary Name Server found.: ns-1727.awsdns-23.co.uk.
AGood: SOA.Primary Name Server included in the delegation set.: ns-1727.awsdns-23.co.uk.
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-1473.awsdns-56.org, ns-1727.awsdns-23.co.uk, ns-313.awsdns-39.com, ns-528.awsdns-02.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
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
AGood: Name Servers with different domain names found.: 4 different Domains found
AGood: Name servers with different Country locations found: 4 Name Servers, 3 Countries: FR, GB, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.193., 205.251.194., 205.251.197., 205.251.198.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5302:, 2600:9000:5305:, 2600:9000:5306:, 4 different subnets (first four blocks): 2600:9000:5301:3900:, 2600:9000:5302:1000:, 2600:9000:5305:c100:, 2600:9000:5306:bf00:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-1727.awsdns-23.co.uk: 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

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: 46250 milliseconds, 46.250 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: ns-1473.awsdns-56.org, ns-1727.awsdns-23.co.uk, ns-313.awsdns-39.com, ns-528.awsdns-02.net

QNr.DomainTypeNS used
1
org
NS
a.root-servers.net (2001:503:ba3e::2:30)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
2
ns-1473.awsdns-56.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1083.awsdns-56.org, g-ns-1656.awsdns-56.org, g-ns-184.awsdns-56.org, g-ns-762.awsdns-56.org

Answer: g-ns-1083.awsdns-56.org
205.251.196.59, 2600:9000:5304:3b00::1

Answer: g-ns-1656.awsdns-56.org
205.251.198.120, 2600:9000:5306:7800::1

Answer: g-ns-184.awsdns-56.org
205.251.192.184, 2600:9000:5300:b800::1

Answer: g-ns-762.awsdns-56.org
205.251.194.250, 2600:9000:5302:fa00::1
3
uk
NS
l.root-servers.net (2001:500:9f::42)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
4
ns-1727.awsdns-23.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1498.awsdns-23.co.uk, g-ns-1819.awsdns-23.co.uk, g-ns-343.awsdns-23.co.uk, g-ns-919.awsdns-23.co.uk

Answer: g-ns-1498.awsdns-23.co.uk
205.251.197.218, 2600:9000:5305:da00::1

Answer: g-ns-1819.awsdns-23.co.uk
205.251.199.27, 2600:9000:5307:1b00::1

Answer: g-ns-343.awsdns-23.co.uk
205.251.193.87, 2600:9000:5301:5700::1

Answer: g-ns-919.awsdns-23.co.uk
205.251.195.151, 2600:9000:5303:9700::1
5
com
NS
l.root-servers.net (2001:500:9f::42)

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
6
ns-313.awsdns-39.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1191.awsdns-39.com, g-ns-1767.awsdns-39.com, g-ns-40.awsdns-39.com, g-ns-615.awsdns-39.com

Answer: g-ns-1191.awsdns-39.com
205.251.196.167, 2600:9000:5304:a700::1

Answer: g-ns-1767.awsdns-39.com
205.251.198.231, 2600:9000:5306:e700::1

Answer: g-ns-40.awsdns-39.com
205.251.192.40, 2600:9000:5300:2800::1

Answer: g-ns-615.awsdns-39.com
205.251.194.103, 2600:9000:5302:6700::1
7
net
NS
b.root-servers.net (2001:500:200::b)

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
8
ns-528.awsdns-02.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1346.awsdns-02.net, g-ns-1922.awsdns-02.net, g-ns-451.awsdns-02.net, g-ns-772.awsdns-02.net

Answer: g-ns-1346.awsdns-02.net
205.251.197.66, 2600:9000:5305:4200::1

Answer: g-ns-1922.awsdns-02.net
205.251.199.130, 2600:9000:5307:8200::1

Answer: g-ns-451.awsdns-02.net
205.251.193.195, 2600:9000:5301:c300::1

Answer: g-ns-772.awsdns-02.net
205.251.195.4, 2600:9000:5303:400::1
9
ns-1473.awsdns-56.org: 205.251.197.193
A
g-ns-1083.awsdns-56.org (2600:9000:5304:3b00::1)
10
ns-1473.awsdns-56.org: 2600:9000:5305:c100::1
AAAA
g-ns-1083.awsdns-56.org (2600:9000:5304:3b00::1)
11
ns-1727.awsdns-23.co.uk: 205.251.198.191
A
g-ns-1498.awsdns-23.co.uk (2600:9000:5305:da00::1)
12
ns-1727.awsdns-23.co.uk: 2600:9000:5306:bf00::1
AAAA
g-ns-1498.awsdns-23.co.uk (2600:9000:5305:da00::1)
13
ns-313.awsdns-39.com: 205.251.193.57
A
g-ns-1191.awsdns-39.com (2600:9000:5304:a700::1)
14
ns-313.awsdns-39.com: 2600:9000:5301:3900::1
AAAA
g-ns-1191.awsdns-39.com (2600:9000:5304:a700::1)
15
ns-528.awsdns-02.net: 205.251.194.16
A
g-ns-1346.awsdns-02.net (2600:9000:5305:4200::1)
16
ns-528.awsdns-02.net: 2600:9000:5302:1000::1
AAAA
g-ns-1346.awsdns-02.net (2600:9000:5305:4200::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
microserver.bhamber.com
0

no CAA entry found
1
0
bhamber.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
bhamber.com

ok
1
0
microserver.bhamber.com

ok
1
0
_acme-challenge.microserver.bhamber.com

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

Name Error - The domain name does not exist
1
0
_acme-challenge.microserver.bhamber.com.microserver.bhamber.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=2ae1aac0-0d07-424c-ab39-bfaa6d30cb47


Last Result: https://check-your-website.server-daten.de/?q=microserver.bhamber.com - 2020-10-17 22:43: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=microserver.bhamber.com" target="_blank">Check this Site: microserver.bhamber.com</a>