Hostname
controltekusa.com
Last fetched
controltekusa.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
controltekusa.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 172.66.41.40 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.42.216 | 172.66.40.0/21 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:2
- Organization
- control group companies,
- Contact emails
Subdomains
33 observed subdomains of controltekusa.com.
Showing 25 of 33. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from controltekusa.com in the public web crawl.
46 sites link to this hostname.
25 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
15 SPF mechanisms authorising senders for controltekusa.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 8699671.spf07.hubspotemail.net |
| SPF_INCLUDE | mailgun.org |
| SPF_INCLUDE | spf.emailsignatures365.com |
| SPF_INCLUDE | spf.mtasv.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 147.160.167.14/32 |
| SPF_IP | 147.160.167.15/32 |
| SPF_IP | 223.165.113.0/24 |
| SPF_IP | 223.165.115.0/24 |
| SPF_IP | 223.165.118.0/23 |
| SPF_IP | 223.165.120.0/23 |
| SPF_IP | 23.21.109.197/32 |
| SPF_IP | 23.21.109.212/32 |
| SPF_IP | 52.49.201.246/32 |
| SPF_IP | 52.49.235.189/32 |
Related pages
Pivot deeper into the graph from controltekusa.com.
- IP · 172.66.41.40
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:2
- Country · CA
- Email · john.diplock@control-inc.com
- TLD · .com
- Browse hostnames · co…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "controltekusa.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.