IP Tracker
Lookup, Trace, Track, Find IP Location with IP tracking technology
and IP tracer tool from IP-Tracker.org
DNS & IP Record Check for Utimaco.com
This tool gives you a detailed look at Utimaco.com DNS setup. It checks various parts of the DNS records to ensure everything is functioning smoothly and securely.
Our DNS & IP record check is organized into 6 main groups, each focusing on different aspects of your domain's DNS configuration. Each group tests key components to ensure optimal domain performance:
- DNS Parent Group - 5 tests
- NS (Nameserver) - 17 tests
- SOA (Start of Authority) - 9 tests
- MX (Mail Exchanger) - 12 tests
- MAIL (Email) - 4 tests
- WWW (World Wide Web) - 24 tests
To help you better understand the results, our team has categorized the outcomes into four statuses:
- PASS - No issues found in the DNS record.
- FAIL - We detected a DNS record error that needs your attention.
- WARN - A minor DNS record issue was found.
- INFO - Informational data about the DNS record with no errors detected.
To ensure the integrity and security of Utimaco.com DNS data, use our DNSSEC check tool. This test provides a deeper analysis, focusing on digital signatures, security, and integrity of the DNS records.
|
|
Below is an overview of the results from our comprehensive DNS lookup for the domain Utimaco.com:
| DNS Group | DNS Check | DNS Record Type | DNS Data Information |
|---|---|---|---|
| PARENT | |||
| PASS | Missing Direct Parent check | OK. Your direct parent zone exists, SOA of parent zone com is a.gtld-servers.net which is good. Some domains (usually third or fourth level domains, such as example.co.us or subdomain.example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion. | |
| FAIL | Glue at parent nameservers | The parent servers do not have glue for your nameserversanycast.regdns1.de, anycast.regdns2.net | |
| INFO | NS records at parent servers | Your NS record at parent servers are: These were obtained from m.gtld-servers.net. However these were obtained from authority section and not answer section. It is better if they were obtained from answer section. |
|
| PASS | DNS servers have A records | OK. All your DNS servers either have A records at the zone parent servers | |
| PASS | Parent nameservers have your nameservers listed | OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there. |
| DNS Group | DNS Status | DNS Record Type | DNS Data Information | |||||
|---|---|---|---|---|---|---|---|---|
| NS | ||||||||
| INFO | NS records at your nameservers | Your NS records at your nameservers are:
|
||||||
| PASS | Mismatched NS records | OK. NS records at all your nameservers are identical. | ||||||
| PASS | All nameservers respond | All your nameservers responding. | ||||||
| PASS | Recursive queries | None of your nameservers allow recursive queries | ||||||
| PASS | Zone Transfer | Zone transfer not allowed by any of your nameservers | ||||||
| PASS | No NS A records at nameservers | OK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records. | ||||||
| PASS | Nameserver name validity | OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). | ||||||
| PASS | Number of nameservers | You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7. | ||||||
| PASS | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | ||||||
| PASS | Missing (stealth) nameservers | You have no stealth servers. | ||||||
| PASS | Missing nameservers 2 | All nameservers listed at parent servers are listed as NS records at your nameservers | ||||||
| PASS | Same Glue | The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This DNS record tests only nameservers that are common at the parent and at your nameservers. | ||||||
| PASS | No CNAMEs for domain | OK. There are no CNAMEs for Utimaco.com. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. | ||||||
| PASS | TCP Allowed | All your nameservers allow TCP connection | ||||||
| PASS | Stealth NS record leakage | Your DNS servers doesn't leak NS record in non-NS request. | ||||||
| PASS | Nameservers on separate class C's | OK. You have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. RFC2182 3.1 goes into more detail about secondary nameserver location. | ||||||
| PASS | All NS IPs public | OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | ||||||
| FAIL | Glue for NS record | Your nameservers for your NS records didn't return the A records for the NS records. | ||||||
| DNS Group | DNS Status | DNS Record Type | DNS Data Information |
|---|---|---|---|
| SOA | |||
| INFO | SOA record | Your SOA record [TTL=3600] is: Primary Name server: anycast.regdns1.de Hostmaster E-mail address: gerd.frank.Utimaco.com Serial #:2025051902 Refresh: 28800 Retry: 7200 Expire: 604800 Default: 86400 |
|
| PASS | SOA MNAME entry | SOA MNAME anycast.regdns1.de is listed as a primary nameserver at your parent nameserver | |
| PASS | SOA RNAME entry | OK. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: [email protected] (techie note: we have changed the initial '.' to an '@' for display purposes). | |
| PASS | NS agreement on SOA Serial # | OK. All your nameservers agree that your SOA serial number is 2009050102. That means that all your nameservers are using the same data (unless you have different sets of data with the same serial number, which would be very bad)! Note that the DNS report only checks the NS records listed at the parent servers (not any stealth servers). | |
| PASS | SOA Serial | Your SOA serial number is: 2025051902. This appears to be in the recommended format of YYYYMMDDnn. | |
| INFO | SOA REFRESH | OK. Your SOA REFRESH interval is: 28800. RFC 1912 recommends 1200 to 43200 seconds, low (1200) if the data is volatile or 43200 (12 hours) if it's not. If you are using NOTIFY you can set for much higher values, for instance, 1 or more days (> 86400 seconds). | |
| WARN | SOA RETRY | OK. Your SOA RETRY interval is: 7200. Typical values would be 180 (3 minutes) to 900 (15 minutes) or higher. | |
| WARN | SOA EXPIRE | OK. Your SOA EXPIRE interval is: 604800 .RFC 1912 recommends 1209600 to 2419200 seconds (2-4 weeks) to allow for major outages of the zone master. | |
| PASS | SOA MINIMUM TTL | OK. Your SOA MINIMUM TTL is: 86400. That is OK |
| DNS Group | DNS Status | DNS Record Type | DNS Data Information |
|---|---|---|---|
| MX | |||
| FAIL | MX Glue | MX record look up did not send glue record for atleast 1 MX server: utimaco-com.mail.cloud.nospamproxy.com |
|
| PASS | MX records are not CNAMEs | OK. Looking up your MX record did not just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it. | |
| PASS | MX name validity | Good. We did not detect any invalid chars in hostnames for your MX records. | |
| PASS | MX is host name, not IP | OK. All of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records). | |
| PASS | Different MX records at nameservers | Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers | |
| FAIL | MX Glues match | MX Glue returned by nameserver for MX record doesn't match with A record of MX hostname utimaco-com.mail.cloud.nospamproxy.com > 193.37.132.102;///// X |
|
| PASS | Duplicate MX records | OK. You do not have any duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources. | |
| PASS | MX A lookups have no CNAMEs | OK. There appear to be no CNAMEs returned for A records lookups from your MX records (CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3). | |
| INFO | MX Record | Your 1 records: 10 utimaco-com.mail.cloud.nospamproxy.com [IP Address=193.37.132.102] [TTL=300] |
|
| FAIL | Multiple MX records | You need to have multiple MX records so that if one is down or unreachable, the other(s) will be able to accept mail for you. | |
| PASS | Reverse MX A records (PTR) | The reverse (PTR) record for your MX records: 193.37.132.102 -> de-s112-gw1.mail.cloud.nospamproxy.com |
|
| PASS | All MX IPs public | OK. All of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail. |
| DNS Group | DNS Status | DNS Record Type | DNS Data Information |
|---|---|---|---|
| PASS | SPF record | 3cde3806bb0f1b73fed49394392ce242b222b8a573e22649ad9ef75035edbef MS=5FD7D94B63E9B2EB532776A8AF14C854879B5E37 MS=ms97330570 apple-domain-verification=lW32GVKehByQKucd atlassian-domain-verification=ZcKqtHFPuymMume80fVIVt4clS265nzrWs3Xtpk3MsDukHPweGpKFbD9b53x5NY6 atlassian-sending-domain-verification=3c7dd587-7c0f-45c0-9e19-e636cb702aca atlassian-sending-domain-verification=42a95a01-65eb-495e-aaac-73dce524b78d be8ab47f329a9418f94dcd035d80ec7e23c9d0a024b90eb97e57ceb62c7831e globalsign-domain-verification=37CBE117C579D10CD159B7DA4CC7D25F google-site-verification=If5KpGxU0OZiE_o2t1lLh716vTjMOdBq7enwcvxxEFg google-site-verification=XZtyfvDSCwALjjZ9_NqZmM7HXTKh8cDm8Jaxy9ns6oY pardot848133=4efc03c91576323583ebce0aa6758d205b44f404ce5854592992fd7597c984c3 s354z51gg5q75s7t7mgpyxc6msd8x5bt sQgxcewIsZ1lUmwp2t0ebpZxIvjoxQUC3w1NgnReTLg= v=spf1 a mx ip4:93.159.251.115 ip4:116.202.252.194 include:spf.utimaco-com.cloud.nospamproxy.com include:_spf.salesforce.com ~all this domain sends email from following domains/subdomains:spf.utimaco-com.cloud.nospamproxy.com, _spf.salesforce.com domain sends mail through its MX servers this domain is used to send mail this domain sends email from following IP/Range: 93.159.251.115, 116.202.252.194 |
|
| WARN | Sender ID record(spfv2.0) | SenderID framework not implemented | |
| WARN | Domain Key Test | Domain keys not implemenetd for _domainkey.Utimaco.com. Separate domainkey records may exist for subdomains and selectors under this domain. this cannot be tested. | |
| PASS | DMARC | v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; rf=afrf; pct=100; ri=86400; adkim=s; aspf=s |
| DNS Group | DNS Status | DNS Record Type | DNS Data Information |
|---|---|---|---|
| WWW | |||
| INFO | WWW A record | Your WWW A record is: www.Utimaco.com. Resolved IP: 23.185.0.3 You have separate A record for www. WA & DA Score for www.Utimaco.com |
|
| PASS | IPs are public | OK. All of your WWW IP addresses appear to be public IP addresses. | |
| PASS | HTTP Service | OK: We can connect to http service on port 80. | |
| INFO | Server | http service on port 80 returns server information as Pantheon |
|
| PASS | Server Header | http response header returns information about server as: Nginx |
|
| PASS | Connection | http connection header return connection as: Keep-alive | |
| PASS | Secure Header HSTS | The server implemented the HSTS (HTTP Strict Transport Security) policy by adding a header over the HTTPS connection as: Max-age=300 | |
| PASS | Secure Header X-Frame-Options | XFO response header that protects against clickjacking is found as: SAMEORIGIN XFO enables content to be found or not within iframes via the browser. |
|
| PASS | Secure Header X-Content-Type-Options | The secure X-Content-Type-Options header is set as: Nosniff The browser must interpret the file exactly as it is specified in the Content-Type HTTP header |
|
| WARN | Secure Header Content-Security-Policy | CSP is not defined in the policy. The return secure header does not send any feedback that the CSP has been set | |
| WARN | Secure Header X-Permitted-Cross-Domain-Policies | X-Permitted-Cross-Domain-Policies was not found in the response header | |
| WARN | Secure Header Referrer-Policy | The Referrer-Policy HTTP header is not set, as it is not in the Referrer header. | |
| INFO | Secure Header Clear-Site-Data | Clear-Site-Data was not found in the response header | |
| INFO | Secure Header Cross-Origin-Embedder-Policy | COEP response header was not found in the HTTP request | |
| INFO | Secure Header Cross-Origin-Opener-Policy | COOP response header was not found in the HTTP request | |
| WARN | Secure Header Cross-Origin-Resource-Policy | CORP policy not found in response header | |
| PASS | Secure Header Cache-Control | Cache-Control policy header is found in HTTP responses as: Max-age=86400, public Cache-Control belongs to the security header group that contains instructions for cashing |
|
| WARN | Secure Header Permissions-Policy | Permissions-Policy header was not found in the HTTP responses. | |
| INFO | Secure Header Feature-Policy | Feature-Policy header was not found in the HTTP responses. | |
| INFO | Secure Header X-XSS-Protection (Deprecated) | X-XSS-Protection header was not found in the HTTP responses. | |
| INFO | Secure Header HTTP Public Key Pinning (Deprecated) | HPKP header was not found in the HTTP responses. | |
| INFO | Secure Header Expect-CT (Deprecated) | Expect-CT header was not found in the HTTP responses. | |
| PASS | SSL / HTTPS Protocol | Domain use encrypted SSL / HTTPS connection on port 443. View SSL Certificate: Utimaco.com. |
|
| INFO | IPv6 | Your domain has IPv6 support. IPv6 address is: 2620:12a:8000::3 |
Click below to copy URL to clipboard for easy sharing of results:
» DNS Domain Lookup Record Utimaco.com »