Hostname
recordinglaw.com
Last fetched
recordinglaw.com resolves to 7 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:1154 as the registrar.
Nutrition Label
Resolution chain
recordinglaw.com resolves to 7 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.47.227 | 104.21.32.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.173.209 | 172.67.160.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 216.150.1.129 | 216.150.1.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 216.150.1.193 | 216.150.1.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 216.150.1.65 | 216.150.1.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 216.150.16.193 | 216.150.16.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 216.150.16.65 | 216.150.16.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:1154
- Organization
- —
- Contact emails
Subdomains
4 observed subdomains of recordinglaw.com.
Showing 3 of 4. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from recordinglaw.com in the public web crawl.
170 sites link to this hostname.
618 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
4 SPF mechanisms authorising senders for recordinglaw.com.
| Mechanism | Target |
|---|---|
| SPF_A | recordinglaw.com |
| SPF_IP | 162.144.153.54 |
| SPF_IP | 162.214.150.207 |
| SPF_MX | recordinglaw.com |
Related pages
Pivot deeper into the graph from recordinglaw.com.
- IP · 104.21.47.227
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:1154
- Country · CA
- Email · asteier4@gmail.com
- TLD · .com
- Browse hostnames · re…
- 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: "recordinglaw.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.