immtel.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
90
immtel.com was registered on 6 Feb 2021 via NameCheap, Inc. and the registry expiry is 6 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/immtel.com.
immtel.com publishes 2 nameservers. DNSSEC is not signed.
immtel.com has 2 IPv4 addresses (104.21.33.31, 172.67.140.190) and 2 IPv6 addresses (2606:4700:3031::ac43:8cbe, 2606:4700:3036::6815:211f). The geolocation database places 104.21.33.31 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for immtel.com in the checks that ran.
immtel.com was registered on 6 Feb 2021 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/immtel.com.
| Registered | since 6 Feb 2021 |
|---|---|
| Created | 6 February 2021 |
| Updated | 7 January 2026 |
| Expires | 6 February 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | arch.ns.cloudflare.com, olivia.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/immtel.com |
immtel.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver arch.ns.cloudflare.com is published for immtel.com in the registration record from https://rdap.verisign.com/com/v1/domain/immtel.com.
Nameserver olivia.ns.cloudflare.com is published for immtel.com in the registration record from https://rdap.verisign.com/com/v1/domain/immtel.com.
immtel.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.33.31, 172.67.140.190 |
|---|---|
| AAAA | 2606:4700:3031::ac43:8cbe, 2606:4700:3036::6815:211f |
| NS | arch.ns.cloudflare.com, olivia.ns.cloudflare.com |
| MX | mxa.mailgun.org (10), mxb.mailgun.org (10) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at immtel.com is "v=spf1 include:mailgun.org ~all".
The DMARC text record at _dmarc.immtel.com is "v=DMARC1; p=none; pct=100; fo=1; ri=3600; rua=mailto:[email protected],mailto:[email protected],mailto:[email protected]…".
IPv4 address 104.21.33.31 answers for immtel.com at resolver 1.1.1.1:53.
IPv4 address 172.67.140.190 answers for immtel.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:8cbe answers for immtel.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:211f answers for immtel.com at resolver 1.1.1.1:53.
Mail exchanger mxa.mailgun.org has preference 10.
Mail exchanger mxb.mailgun.org has preference 10.
immtel.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.33.31 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for immtel.com is valid, with 62 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | immtel.com |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 62 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.immtel.com, immtel.com.
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 200 in 36 ms. The target title is 17 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 36 ms |
| Title length | 17 yes |
| Quoted title | "门户首页 - ImmTelecom" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 52 |
| Images | 2 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for immtel.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
immtel.com is placed in Toronto, Canada.
immtel.com expires on 6 February 2027 according to https://rdap.verisign.com/com/v1/domain/immtel.com.
The registry did not return a person or a company for immtel.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.