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




V

Connect failure - perhaps firewall

Checked:
20.11.2023 20:26:20


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
staging.sundex-api.com.br
A
54.232.162.173
São Paulo/Brazil (BR) - Amazon Technologies Inc.
Hostname: ec2-54-232-162-173.sa-east-1.compute.amazonaws.com
yes
1
0

AAAA

yes


www.staging.sundex-api.com.br

Name Error
yes
1
0
*.sundex-api.com.br
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.staging.sundex-api.com.br
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 46780, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 13, KeyTag 38298, DigestType 2 and Digest ny1Jk/R7DydR3gAH1wonVO5TL+NzdhFU2ep6jLnY6hg=



1 RRSIG RR to validate DS RR found



RRSIG-Owner br., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.12.2023, 17:00:00 +, Signature-Inception: 20.11.2023, 16:00:00 +, KeyTag 46780, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 16486, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner br., Algorithm: 13, 1 Labels, original TTL: 21600 sec, Signature-expiration: 03.12.2023, 12:00:00 +, Signature-Inception: 12.11.2023, 12:00:00 +, KeyTag 2471, Signer-Name: br



RRSIG-Owner br., Algorithm: 13, 1 Labels, original TTL: 21600 sec, Signature-expiration: 03.12.2023, 12:00:00 +, Signature-Inception: 12.11.2023, 12:00:00 +, KeyTag 38298, Signer-Name: br



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



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



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

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



DS with Algorithm 13, KeyTag 53082, DigestType 2 and Digest gg/TEzfyqpUcIFXlN2Urhy/aK8b34Dsf0dfdnTgBQe8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 01.12.2023, 12:00:09 +, Signature-Inception: 17.11.2023, 11:00:09 +, KeyTag 16486, Signer-Name: br



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



1 DNSKEY RR found



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.br., Algorithm: 13, 2 Labels, original TTL: 21600 sec, Signature-expiration: 04.12.2023, 19:25:13 +, Signature-Inception: 20.11.2023, 18:25:13 +, KeyTag 53082, Signer-Name: com.br



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



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

Zone: sundex-api.com.br
sundex-api.com.br
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 "23epd73q1utum2gs2jr9r2q8nl199v28" between the hashed NSEC3-owner "23enudout1ssnp70d4hhpo3flk0nq6uq" and the hashed NextOwner "23er2rup9p44aoeg9urlalj4k7l3codf". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 23enudout1ssnp70d4hhpo3flk0nq6uq.com.br., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 28.11.2023, 12:01:16 +, Signature-Inception: 14.11.2023, 11:01:16 +, KeyTag 53082, Signer-Name: com.br



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "igtpjvie9v30c160tj60kl855qjgp039" as Owner. That's the Hash of "com.br" with the NextHashedOwnerName "igtq8un06gthbl2v4ni32jv9skubqorb". So that domain name is the Closest Encloser of "sundex-api.com.br". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner igtpjvie9v30c160tj60kl855qjgp039.com.br., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 04.12.2023, 19:25:13 +, Signature-Inception: 20.11.2023, 18:25:13 +, KeyTag 53082, Signer-Name: com.br



0 DNSKEY RR found




Zone: staging.sundex-api.com.br
staging.sundex-api.com.br
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.staging.sundex-api.com.br
www.staging.sundex-api.com.br
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.staging.sundex-api.com.br
  ns-287.awsdns-35.com

staging.sundex-api.com.br
  ns-287.awsdns-35.com / 0a079d7a9c401e496173872a7143c7fb -
205.251.193.31
Dublin/Leinster/Ireland (IE) - Amazon.com


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

sundex-api.com.br
  ns-1301.awsdns-34.org / ec9c2a7bd8f0abbddd6a8af43f652951 -
205.251.197.21
Dublin/Leinster/Ireland (IE) - Amazon.com


 
2600:9000:5305:1500::1
London/England/United Kingdom (GB) - Amazon.com


  ns-1701.awsdns-20.co.uk / e3fc9b2808eabb1791c00963e5c52f3d -
205.251.198.165
Herndon/Virginia/United States (US) - Amazon.com


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


  ns-287.awsdns-35.com / b085e4b5e9f11bafe4c40a599f175633 -
205.251.193.31
Dublin/Leinster/Ireland (IE) - Amazon.com


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


  ns-668.awsdns-19.net / bec0844a130101795d62a001484e9558 -
205.251.194.156
Sterling/Virginia/United States (US) - Amazon.com


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

com.br
  a.dns.br / a7.a.dns.br
200.219.148.10
São Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:6::10
São Paulo/Brazil (BR) - Núcleo de Inf. e Coord. do Ponto BR - NIC.BR


  b.dns.br / b8.b.dns.br
200.189.41.10
Pinheiros/Sao Paulo/Brazil (BR) - N?cleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:8::10
Pinheiros/Sao Paulo/Brazil (BR) - N?cleo de Inf. e Coord. do Ponto BR - NIC.BR


  c.dns.br / c6.c.dns.br
200.192.233.10
Pinheiros/Sao Paulo/Brazil (BR) - N?cleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:a::10
Pinheiros/Sao Paulo/Brazil (BR) - N?cleo de Inf. e Coord. do Ponto BR - NIC.BR


  d.dns.br / d3.d.dns.br
200.219.154.10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:4::10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR


  e.dns.br / e4.e.dns.br
200.229.248.10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:2::10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR


  f.dns.br / f7.a.f.dns.br
200.219.159.10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR


 
2001:12f8:c::10
Pinheiros/Sao Paulo/Brazil (BR) - NÔcleo de Inf. e Coord. do Ponto BR - NIC.BR

br
  a.dns.br / a2.a.dns.br


  b.dns.br / b2.b.dns.br


  c.dns.br / c3.c.dns.br


  d.dns.br / d4.d.dns.br


  e.dns.br / e3.e.dns.br


  f.dns.br / f7.a.f.dns.br


4. SOA-Entries


Domain:br
Zone-Name:br
Primary:a.dns.br
Mail:hostmaster.registro.br
Serial:2023324466
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:6


Domain:com.br
Zone-Name:com.br
Primary:a.dns.br
Mail:hostmaster.registro.br
Serial:2023324466
Refresh:1800
Retry:900
Expire:604800
TTL:900
num Entries:12


Domain:sundex-api.com.br
Zone-Name:sundex-api.com.br
Primary:ns-287.awsdns-35.com
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:staging.sundex-api.com.br
Zone-Name:sundex-api.com.br
Primary:ns-287.awsdns-35.com
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


Domain:www.staging.sundex-api.com.br
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://staging.sundex-api.com.br/
54.232.162.173 GZip used - 384 / 612 - 37.25 %
200

Html is minified: 129.94 %
0.454
H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 20 Nov 2023 19:28:32 GMT
Content-Type: text/html
Last-Modified: Mon, 20 Nov 2023 18:43:45 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"655ba8e1-264"
Content-Encoding: gzip

• https://staging.sundex-api.com.br/
54.232.162.173
-2

1.704
V
ConnectFailure - Unable to connect to the remote server

• http://staging.sundex-api.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
54.232.162.173 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.470
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Mon, 20 Nov 2023 19:28:35 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://54.232.162.173/
54.232.162.173
-2

1.704
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "staging.sundex-api.com.br" is subdomain, public suffix is ".com.br", top-level-domain is ".br", top-level-domain-type is "country-code", Country is Brazil, tld-manager is "Comite Gestor da Internet no Brasil", num .br-domains preloaded: 2925 (complete: 231048)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: staging.sundex-api.com.br 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: staging.sundex-api.com.br has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood - only one version with Http-Status 200
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
http://staging.sundex-api.com.br/ 54.232.162.173


Url with incomplete Content-Type - header - missing charset
http://staging.sundex-api.com.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 54.232.162.173


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
Vhttps://staging.sundex-api.com.br/ 54.232.162.173
-2

Connect failure - perhaps firewall
Vhttps://54.232.162.173/ 54.232.162.173
-2

Connect failure - perhaps firewall
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 staging.sundex-api.com.br, 1 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.staging.sundex-api.com.br

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:: 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-1301.awsdns-34.org, ns-1701.awsdns-20.co.uk, ns-287.awsdns-35.com, ns-668.awsdns-19.net, 4 Name Servers included in Delegation: ns-1301.awsdns-34.org, ns-1701.awsdns-20.co.uk, ns-287.awsdns-35.com, ns-668.awsdns-19.net, 4 Name Servers included in 1 Zone definitions: ns-1301.awsdns-34.org, ns-1701.awsdns-20.co.uk, ns-287.awsdns-35.com, ns-668.awsdns-19.net, 1 Name Servers listed in SOA.Primary: ns-287.awsdns-35.com.
AGood: Only one SOA.Primary Name Server found.: ns-287.awsdns-35.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-287.awsdns-35.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: ns-1301.awsdns-34.org, ns-1701.awsdns-20.co.uk, ns-287.awsdns-35.com, ns-668.awsdns-19.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: GB, IE, 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:1f00:, 2600:9000:5302:9c00:, 2600:9000:5305:1500:, 2600:9000:5306:a500:
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-287.awsdns-35.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.
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
ADuration: 149163 milliseconds, 149.163 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: ns-1301.awsdns-34.org, ns-1701.awsdns-20.co.uk, ns-287.awsdns-35.com, ns-668.awsdns-19.net

QNr.DomainTypeNS used
1
org
NS
l.root-servers.net (2001:500:9f::42)

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-1301.awsdns-34.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1061.awsdns-34.org, g-ns-162.awsdns-34.org, g-ns-1634.awsdns-34.org, g-ns-740.awsdns-34.org

Answer: g-ns-1061.awsdns-34.org
205.251.196.37, 2600:9000:5304:2500::1

Answer: g-ns-162.awsdns-34.org
205.251.192.162, 2600:9000:5300:a200::1

Answer: g-ns-1634.awsdns-34.org
205.251.198.98, 2600:9000:5306:6200::1

Answer: g-ns-740.awsdns-34.org
205.251.194.228, 2600:9000:5302:e400::1
3
uk
NS
k.root-servers.net (2001:7fd::1)

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-1701.awsdns-20.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1495.awsdns-20.co.uk, g-ns-1816.awsdns-20.co.uk, g-ns-340.awsdns-20.co.uk, g-ns-916.awsdns-20.co.uk

Answer: g-ns-1495.awsdns-20.co.uk
205.251.197.215, 2600:9000:5305:d700::1

Answer: g-ns-1816.awsdns-20.co.uk
205.251.199.24, 2600:9000:5307:1800::1

Answer: g-ns-340.awsdns-20.co.uk
205.251.193.84, 2600:9000:5301:5400::1

Answer: g-ns-916.awsdns-20.co.uk
205.251.195.148, 2600:9000:5303:9400::1
5
com
NS
g.root-servers.net (2001:500:12::d0d)

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-287.awsdns-35.com
NS
l.gtld-servers.net (2001:500:d937::30)

Answer: g-ns-1187.awsdns-35.com, g-ns-1763.awsdns-35.com, g-ns-36.awsdns-35.com, g-ns-611.awsdns-35.com

Answer: g-ns-1187.awsdns-35.com
205.251.196.163, 2600:9000:5304:a300::1

Answer: g-ns-1763.awsdns-35.com
205.251.198.227, 2600:9000:5306:e300::1

Answer: g-ns-36.awsdns-35.com
205.251.192.36, 2600:9000:5300:2400::1

Answer: g-ns-611.awsdns-35.com
205.251.194.99, 2600:9000:5302:6300::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-668.awsdns-19.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1363.awsdns-19.net, g-ns-1939.awsdns-19.net, g-ns-468.awsdns-19.net, g-ns-789.awsdns-19.net

Answer: g-ns-1363.awsdns-19.net
205.251.197.83, 2600:9000:5305:5300::1

Answer: g-ns-1939.awsdns-19.net
205.251.199.147, 2600:9000:5307:9300::1

Answer: g-ns-468.awsdns-19.net
205.251.193.212, 2600:9000:5301:d400::1

Answer: g-ns-789.awsdns-19.net
205.251.195.21, 2600:9000:5303:1500::1
9
ns-1301.awsdns-34.org: 205.251.197.21
A
g-ns-1061.awsdns-34.org (2600:9000:5304:2500::1)
10
ns-1301.awsdns-34.org: 2600:9000:5305:1500::1
AAAA
g-ns-1061.awsdns-34.org (2600:9000:5304:2500::1)
11
ns-1701.awsdns-20.co.uk: 205.251.198.165
A
g-ns-1495.awsdns-20.co.uk (2600:9000:5305:d700::1)
12
ns-1701.awsdns-20.co.uk: 2600:9000:5306:a500::1
AAAA
g-ns-1495.awsdns-20.co.uk (2600:9000:5305:d700::1)
13
ns-287.awsdns-35.com: 205.251.193.31
A
g-ns-1187.awsdns-35.com (2600:9000:5304:a300::1)
14
ns-287.awsdns-35.com: 2600:9000:5301:1f00::1
AAAA
g-ns-1187.awsdns-35.com (2600:9000:5304:a300::1)
15
ns-668.awsdns-19.net: 205.251.194.156
A
g-ns-1363.awsdns-19.net (2600:9000:5305:5300::1)
16
ns-668.awsdns-19.net: 2600:9000:5302:9c00::1
AAAA
g-ns-1363.awsdns-19.net (2600:9000:5305:5300::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
staging.sundex-api.com.br
0

no CAA entry found
1
0
sundex-api.com.br
0

no CAA entry found
1
0
com.br
0

no CAA entry found
1
0
br
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sundex-api.com.br

ok
1
0
staging.sundex-api.com.br

ok
1
0
_acme-challenge.staging.sundex-api.com.br

Name Error - The domain name does not exist
1
0
_acme-challenge.staging.sundex-api.com.br.sundex-api.com.br

Name Error - The domain name does not exist
1
0
_acme-challenge.staging.sundex-api.com.br.staging.sundex-api.com.br

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
staging.sundex-api.com.br
54.232.162.173
21
FTP



staging.sundex-api.com.br
54.232.162.173
21
FTP



staging.sundex-api.com.br
54.232.162.173
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4

staging.sundex-api.com.br
54.232.162.173
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.4
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
staging.sundex-api.com.br IN SSHFP 3 2 f94f2f5e784b89a476f804d3fd53620bb34bb6a70bd5443d68a7aa43b1a5a8f0
staging.sundex-api.com.br IN SSHFP 4 2 34177369c3e7e04dfbfe022173d998a15a96ef6eaefb1920108665d088c5d1c1
staging.sundex-api.com.br
54.232.162.173
25
SMTP



staging.sundex-api.com.br
54.232.162.173
25
SMTP



staging.sundex-api.com.br
54.232.162.173
53
DNS



staging.sundex-api.com.br
54.232.162.173
53
DNS



staging.sundex-api.com.br
54.232.162.173
110
POP3



staging.sundex-api.com.br
54.232.162.173
110
POP3



staging.sundex-api.com.br
54.232.162.173
143
IMAP



staging.sundex-api.com.br
54.232.162.173
143
IMAP



staging.sundex-api.com.br
54.232.162.173
465
SMTP (encrypted)



staging.sundex-api.com.br
54.232.162.173
465
SMTP (encrypted)



staging.sundex-api.com.br
54.232.162.173
587
SMTP (encrypted, submission)



staging.sundex-api.com.br
54.232.162.173
587
SMTP (encrypted, submission)



staging.sundex-api.com.br
54.232.162.173
993
IMAP (encrypted)



staging.sundex-api.com.br
54.232.162.173
993
IMAP (encrypted)



staging.sundex-api.com.br
54.232.162.173
995
POP3 (encrypted)



staging.sundex-api.com.br
54.232.162.173
995
POP3 (encrypted)



staging.sundex-api.com.br
54.232.162.173
1433
MS SQL



staging.sundex-api.com.br
54.232.162.173
1433
MS SQL



staging.sundex-api.com.br
54.232.162.173
2082
cPanel (http)



staging.sundex-api.com.br
54.232.162.173
2082
cPanel (http)



staging.sundex-api.com.br
54.232.162.173
2083
cPanel (https)



staging.sundex-api.com.br
54.232.162.173
2083
cPanel (https)



staging.sundex-api.com.br
54.232.162.173
2086
WHM (http)



staging.sundex-api.com.br
54.232.162.173
2086
WHM (http)



staging.sundex-api.com.br
54.232.162.173
2087
WHM (https)



staging.sundex-api.com.br
54.232.162.173
2087
WHM (https)



staging.sundex-api.com.br
54.232.162.173
2089
cPanel Licensing



staging.sundex-api.com.br
54.232.162.173
2089
cPanel Licensing



staging.sundex-api.com.br
54.232.162.173
2095
cPanel Webmail (http)



staging.sundex-api.com.br
54.232.162.173
2095
cPanel Webmail (http)



staging.sundex-api.com.br
54.232.162.173
2096
cPanel Webmail (https)



staging.sundex-api.com.br
54.232.162.173
2096
cPanel Webmail (https)



staging.sundex-api.com.br
54.232.162.173
2222
DirectAdmin (http)



staging.sundex-api.com.br
54.232.162.173
2222
DirectAdmin (http)



staging.sundex-api.com.br
54.232.162.173
2222
DirectAdmin (https)



staging.sundex-api.com.br
54.232.162.173
2222
DirectAdmin (https)



staging.sundex-api.com.br
54.232.162.173
3306
mySql



staging.sundex-api.com.br
54.232.162.173
3306
mySql



staging.sundex-api.com.br
54.232.162.173
5224
Plesk Licensing



staging.sundex-api.com.br
54.232.162.173
5224
Plesk Licensing



staging.sundex-api.com.br
54.232.162.173
5432
PostgreSQL



staging.sundex-api.com.br
54.232.162.173
5432
PostgreSQL



staging.sundex-api.com.br
54.232.162.173
8080
Ookla Speedtest (http)



staging.sundex-api.com.br
54.232.162.173
8080
Ookla Speedtest (http)



staging.sundex-api.com.br
54.232.162.173
8080
Ookla Speedtest (https)



staging.sundex-api.com.br
54.232.162.173
8080
Ookla Speedtest (https)



staging.sundex-api.com.br
54.232.162.173
8083
VestaCP http



staging.sundex-api.com.br
54.232.162.173
8083
VestaCP http



staging.sundex-api.com.br
54.232.162.173
8083
VestaCP https



staging.sundex-api.com.br
54.232.162.173
8083
VestaCP https



staging.sundex-api.com.br
54.232.162.173
8443
Plesk Administration (https)



staging.sundex-api.com.br
54.232.162.173
8443
Plesk Administration (https)



staging.sundex-api.com.br
54.232.162.173
8447
Plesk Installer + Updates



staging.sundex-api.com.br
54.232.162.173
8447
Plesk Installer + Updates



staging.sundex-api.com.br
54.232.162.173
8880
Plesk Administration (http)



staging.sundex-api.com.br
54.232.162.173
8880
Plesk Administration (http)



staging.sundex-api.com.br
54.232.162.173
10000
Webmin (http)



staging.sundex-api.com.br
54.232.162.173
10000
Webmin (http)



staging.sundex-api.com.br
54.232.162.173
10000
Webmin (https)



staging.sundex-api.com.br
54.232.162.173
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=cf3bb11e-8ed6-479c-a015-d1be2986aa0a


Last Result: https://check-your-website.server-daten.de/?q=staging.sundex-api.com.br - 2023-11-20 20:26:20


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

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

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