Hostname
nfloans.com
Last fetched
nfloans.com resolves to 8 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
nfloans.com resolves to 8 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 100.21.11.142 | 100.20.0.0/14 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 16.145.141.139 | 16.145.0.0/16 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 35.161.24.88 | 35.160.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 35.161.61.231 | 35.160.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 44.238.14.202 | 44.224.0.0/11 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 44.245.80.50 | 44.224.0.0/11 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.200.158.90 | 54.200.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
| 54.68.110.37 | 54.68.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of nfloans.com owner
- Contact emails
- 2d99744d-80fb-4596-b147-d8b346a56243@identity-protect.org
- 8260225f-36e4-4716-a4c0-e5cf151cb9a1@identity-protect.org
- 8622f476-6b72-4c6c-83da-6687fcf09aa5@identity-protect.org
- 8823ede4-b796-464f-ab4b-cc5bb9cc456e@identity-protect.org
- b384730b-5216-46f1-b8c9-455da4871921@identity-protect.org
- fbb56899-875b-498a-a8ed-2356c67739db@identity-protect.org
Subdomains
3 observed subdomains of nfloans.com.
Threat posture
History
Mail and authentication
MX records
Related pages
Pivot deeper into the graph from nfloans.com.
- IP · 100.21.11.142
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · 2d99744d-80fb-4596-b147-d8b346a56243@identity-protect.org
- TLD · .com
- Browse hostnames · nf…
- 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: "nfloans.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.