Hostname
petals.com
Last fetched
petals.com resolves to 1 IPv4 address operated by BIGCOMMERCE - Bigcommerce Inc. in US. WHOIS lists iana:9 as the registrar.
Nutrition Label
Resolution chain
petals.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 63.141.128.14 | 63.141.128.0/24 | AS399566 | BIGCOMMERCE - Bigcommerce Inc. | US |
WHOIS identity
- Registrar
- iana:9
- Organization
- chris corelli
- Contact emails
- 1a1bf4040a28fd0a428eaa8b2379d5d7@domaindiscreet.com
- 3e285ff40a28fd0a167027af95134391@domaindiscreet.com
- 45abe9e90a28fd0a17559875a19862a2@domaindiscreet.com
- 57827351@myprivatename.com
- 8dca7d670a28fd0a6110611401b873b6@domaindiscreet.com
- b1d63f950a28fd0a0d056abbc80433e5@domaindiscreet.com
- chrisc@officescapesdirect.com
- d5e191bd0a28fd0a7f80a2dc85ed055e@domaindiscreet.com
- e3r6mgs9i2hpdaebrvss4hqcdt@domaindiscreet.com
Subdomains
2 observed subdomains of petals.com.
| Subdomain |
|---|
| blog.petals.com |
| www.petals.com |
Web-graph footprint
Distinct hostnames that link to or from petals.com in the public web crawl.
66 sites link to this hostname.
28 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for petals.com.
| Mechanism | Target |
|---|---|
| SPF_A | petals.com |
| SPF_INCLUDE | _spf.bigcommerce.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_MX | petals.com |
Related pages
Pivot deeper into the graph from petals.com.
- IP · 63.141.128.14
- ASN · AS399566BIGCOMMERCE - Bigcommerce Inc.
- Registrar · iana:9
- Country · US
- Email · 1a1bf4040a28fd0a428eaa8b2379d5d7@domaindiscreet.com
- TLD · .com
- Browse hostnames · pe…
- 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: "petals.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.