Skip to content

Hostname

jdfactors.com

Last fetched

jdfactors.com resolves to 207.236.199.67, announced in 207.241.191.0/24 by BACOM - Bell Canada in CA. jdfactors.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · jdfactors.comRouting diversity1.5/10Peering density9.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/jdfactors.com

Resolution chain

IPv6 resolution

No AAAA record for jdfactors.com is recorded in WhisperGraph.

Attribution

bacom bell canada

ORIGIN_AS

WHOIS identity

Registrar
iana:86
Registrant organisation
j d factors,
Contact emails
mmcginty@tampabiz.com, whois@emailaddressprotection.com

Subdomains

Subdomain
caweb.jdfactors.com
fr.jdfactors.com
link.jdfactors.com
toronto.jdfactors.com
us.jdfactors.com
ussql.jdfactors.com
usweb.jdfactors.com
www.jdfactors.com

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.domaindiscover.com
  • ns2.domaindiscover.com

MX records

  • jdfactors-com.mail.protection.outlook.com

SPF policy

  • include: _spf.getresponse.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: spf.smtp2go.com
  • include: 9232944.spf07.hubspotemail.net
  • include: sendgrid.net
  • ip: 12.49.47.130
  • ip: 12.49.47.131
  • ip: 168.245.30.59
  • ip: 168.93.73.90
  • ip: 168.93.73.91
  • ip: 173.165.127.17
  • ip: 173.165.127.18
  • ip: 207.236.199.66
  • ip: 207.236.199.67
  • ip: 38.120.94.25
  • ip: 47.180.201.160
  • ip: 66.11.95.161

Threat-feed evidence

History

Related pages

Pivot from jdfactors.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "jdfactors.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.